Design tokens for restaurants who hate design systems
You do not need a forty-page system to keep three sites looking like one group. A tight set of colour, type and spacing tokens will do.
Design systems have a reputation for enterprise theatre. Underneath is a simple idea: agree the basics so each new site does not invent a slightly different pink.
Tokens are that idea without the ceremony. Named colour, type, space. The lemon, the ink, the booking button that survives contact with real copy.
Start small. Palette, one pairing of fonts, spacing that matches the grid, menu and book styles that work on a phone. That prevents drift across locations.
Enforce with tools, not policy. CSS variables, theme files, Quiteful embeds that do not restyle themselves into chaos.
Grow later if you need it. Most groups need the sites, the menus and the booking path to feel related — not a senior designer on every margin.
Common questions
- What tokens does a restaurant group actually need?
- Colour, type, spacing, buttons, and a rule for photography. Not a committee and a 200-component Figma file on day one.
- Why bother if each site should feel different?
- Different rooms can still share a booking button, a menu embed and hours formatting. Guests feel the group without a clone.