# 63 Venue Floorplan

**Philosophy and fit.** Start with how people will use the space. Built for wedding venue, conference venue, event space. The visitor’s next step is to enquire about an event.

**Visual grammar.** Use a plum and cream architectural plan with selectable seating configurations. Preserve the hierarchy of floorplans, room configurations, event packages; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** The Assembly Rooms is a fictional demonstration. The entry page establishes a complete visual direction, with configure the room and event enquiry 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 floorplans, room configurations, event packages. 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

- Floorplans
- Room configurations
- Event packages

## Routes

- Entry: /preview/63-venue-floorplan/start
- Configure the room: /preview/63-venue-floorplan/plan
- Event enquiry: /preview/63-venue-floorplan/enquiry

## Reference and adaptation

- Page scope: Portfolio & enquiry.
- Distinct composition: plum and cream architectural plan with selectable seating configurations.
- Typography: Libre Baskerville / DM Sans.
- Tokens: page #f4efe8, ink #463442, accent #764259.
- The event decision is spatial: switch between banquet, theatre and workshop arrangements, then compare the guest count with the selected capacity before reviewing the enquiry.
- 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.