# 65 Branch Network

**Philosophy and fit.** Find the branch that does the work you need. Built for small chain, multi-location services, bike repair. The visitor’s next step is to book at a branch.

**Visual grammar.** Use a map-led mint and ink branch network with location-specific ledgers. Preserve the hierarchy of location finder, branch hours, service availability; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** LOCAL / Cycle care is a fictional demonstration. The entry page establishes a complete visual direction, with branch details and book at this branch 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 location finder, branch hours, service availability. 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

- Location finder
- Branch hours
- Service availability

## Routes

- Entry: /preview/65-branch-network/start
- Branch details: /preview/65-branch-network/location
- Book at this branch: /preview/65-branch-network/booking

## Reference and adaptation

- Page scope: Multi-location site.
- Distinct composition: map-led mint and ink branch network with location-specific ledgers.
- Typography: Space Grotesk / DM Sans.
- Tokens: page #f0f5ed, ink #273e3c, accent #35645b.
- Treat locations as distinct service choices, with their own hours, equipment and availability. The list and map are equivalent ways to choose a branch, and booking retains its address and supported service.
- 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.