# 67 Everyday Eatery

**Philosophy and fit.** Get from hungry to a clear collection order. Built for cafe, diner, pizzeria, takeaway. The visitor’s next step is to order for collection.

**Visual grammar.** Use a red and butter-yellow menu board with large food photography. Preserve the hierarchy of scannable menu, visible prices, collection ordering; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** SIDE STREET / Pizza & plates is a fictional demonstration. The entry page establishes a complete visual direction, with build your order and choose collection as supporting states. Inputs use local deterministic fixtures; no request, order, application or payment is sent.

**Responsive behaviour.** On a phone, keep the primary decision first, stack facts with explicit labels, preserve the order of the workflow, and provide comfortably sized controls. Wide diagrams scale; tabular facts retain their labels.

**Adaptation.** Replace the fictional brand, prices, availability, qualifications and claims with verified client information. Preserve scannable menu, visible prices, collection ordering. Use imagery to explain the place, people, work or product, with deliberate crops and honest captions. Do not turn this into a generic hero-and-card layout.

## Commercial and content patterns

- Scannable menu
- Visible prices
- Collection ordering

## Routes

- Entry: /preview/67-everyday-eatery/start
- Build your order: /preview/67-everyday-eatery/menu
- Choose collection: /preview/67-everyday-eatery/order

## Reference and adaptation

- Page scope: Small brochure.
- Distinct composition: red and butter-yellow menu board with large food photography.
- Typography: Archivo Black / DM Sans.
- Tokens: page #fff4d7, ink #4d2723, accent #9c3029.
- Use a fast, price-forward menu and a visible collection basket. The bright counter-service character and straightforward hours deliberately differ from Fine Dining’s slower seasonal narrative.
- Use the native inputs and labelled states in Demo.vue as interaction references. Replace local fixtures with real validation, availability and backend behaviour in the destination application.

## Assets

All brands and fixture data are fictional. Original SVG diagrams are source-native. Commercial photos are illustrative and are documented in [asset provenance](../../../docs/COMMERCIAL_ASSETS.md); do not present them as evidence of a real business or rename a stock subject as actual staff. See the public commercial asset manifest for URLs, checksums and cropping guidance.