Brand and web system
Grande Burrito
Grande Burrito pairs a vivid public experience with a constrained Sanity studio that lets an owner update the information customers rely on every day.
- Role
- Strategy · Design system · Engineering
- When
- 2026 · In progress
- Built with
- SvelteKit · Sanity · TypeScript · Playwright

The premise
A restaurant website has a very practical first job: help someone decide whether to visit. Grande’s existing web presence fragments the details people need most—current hours, menu choices, prices, a phone number, and directions.
The product
The mobile-first site places today’s status, menu access, and visit actions in the first page context. Behind it, a focused Sanity studio lets the owner manage menus, sold-out states, regular and exceptional hours, announcements, photography, and small copy changes without touching the layout.
Brand with operational value
The visual system draws from the storefront, signage, food, and personality of the real place rather than a generic restaurant template. Every expressive choice must still support fast scanning, resilient content, visible focus, reduced motion, and essential information when scripting is delayed.
The system
- Structured menu and hours data drive both visible content and machine-readable business information.
- Scheduled exceptions override regular hours and expire automatically.
- A content snapshot keeps core public information available during a CMS outage.
- Constrained editing protects the design while making routine updates approachable.
What I owned
I defined the product requirements, content model, design-system contract, frontend and studio architecture, validation rules, testing strategy, and ownership-transfer plan. The project is currently moving from functional foundation into the full brand expression.
The system behind the work
Grande Burrito Sign & Sheet System
A sign-led, menu-sheet-inspired system that keeps restaurant decisions clear and resilient.
-
The sign is the anchor, not wallpaper
Brand cues establish identity without competing with operational information.
-
Operational facts come first
Hours, menu, phone, and directions remain useful through degraded states.
-
Borrow the menu's rhythm, improve its scan
Printed-menu character is translated into accessible digital hierarchy.
-
Build resilience into the default
Accessibility, responsive content, and service failure are first-class states.
Visual fingerprint
Identity, components, and proof.
A curated view of the system’s real foundations and state coverage—not a second documentation site.
Foundation
Semantic color
- Sign ink
#17141cBrand field, text, and focus
- Sign tan
#a6855fObserved storefront identity
- Paper
#fff9ecPrimary sheet surface
- Warm paper
#ead9bcSubtle operational panels
- Deep paper
#d3b483Surface emphasis
- Muted ink
#594a3eSupporting copy
- Rule
#aa9578Menu dividers and boundaries
Foundation
Typography roles
- Brand Anton
A self-hosted condensed face reserved for the sign-derived mark.
- Display Georgia
Brings printed-menu character to food-led headings.
- Body and controls System sans serif
Keeps hours, prices, actions, and operational copy fast to scan.
Inventory
Representative components
BrandMark
A responsive reconstruction anchors the identity while its provisional provenance stays explicit.
- Responsive
- Accessible label
- Provisional
MenuItem
Menu rows preserve pricing and availability detail without recreating the printed menu’s density.
- Fixed price
- Market price
- Sold out
- Dietary
- Heat
HoursStatus
Current status, next transition, today’s hours, and exceptions stay answerable together.
- Open
- Closed
- Exception
- Live update
In the product
System at work

Decision propagation
Printed-menu rhythm becomes a scannable system
Food categories, descriptions, and prices use a consistent editorial hierarchy that keeps a long made-to-order menu easy to scan.
The sign pair measures about 5.33:1, actions meet the 44px target, focus remains visible in forced colors, and status never relies on color alone.