# 70 Community Commons

**Philosophy and fit.** Put the useful things a community shares in one welcoming place. Built for club, association, neighbourhood group. The visitor’s next step is to join a community.

**Visual grammar.** Use a welcoming coloured noticeboard with dated notices and plain joining steps. Preserve the hierarchy of events, meeting notes, resources, membership; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** Maple Street / Commons is a fictional demonstration. The entry page establishes a complete visual direction, with community calendar and join the commons 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 events, meeting notes, resources. 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

- Events
- Meeting notes
- Resources
- Membership

## Routes

- Entry: /preview/70-community-commons/start
- Community calendar: /preview/70-community-commons/events
- Join the commons: /preview/70-community-commons/join

## Reference and adaptation

- Page scope: Community site.
- Distinct composition: welcoming coloured noticeboard with dated notices and plain joining steps.
- Typography: DM Sans.
- Tokens: page #f6f0df, ink #3c4135, accent #4b6348.
- Use a welcoming bulletin board with different notice sizes for joining, dates and shared resources. Keep meeting notes discoverable so the organisation feels participatory rather than promotional.
- 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.