# 73 Community Forum

**Philosophy and fit.** Make a conversation worth finding again. Built for community, member organisation, discussion forum. The visitor’s next step is to join a discussion.

**Visual grammar.** Use a modern blue-grey discussion architecture with nested replies and category rails. Preserve the hierarchy of categories, thread hierarchy, replies, moderation; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** The Workbench / Community is a fictional demonstration. The entry page establishes a complete visual direction, with discussion thread and member profile 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 categories, thread hierarchy, replies. 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

- Categories
- Thread hierarchy
- Replies
- Moderation

## Routes

- Entry: /preview/73-community-forum/start
- Discussion thread: /preview/73-community-forum/thread
- Member profile: /preview/73-community-forum/profile

## Reference and adaptation

- Page scope: Community site.
- Distinct composition: modern blue-grey discussion architecture with nested replies and category rails.
- Typography: DM Sans.
- Tokens: page #f0f3f8, ink #2f3b4e, accent #385da0.
- Keep the multi-person thread as the core object. Category context, reply nesting, closed states and member information distinguish this from the scripted Conversation Desk or a personal Knowledge Garden.
- 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.