# 57 Property Listing

**Philosophy and fit.** Give a place room to speak, and its facts a place to stay. Built for real estate, property management, lettings. The visitor’s next step is to request a viewing.

**Visual grammar.** Use a deep-green property folio with large photography and a persistent facts rail. Preserve the hierarchy of listing filters, property facts, floorplans, neighbourhood guide; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** NORTH / Residential is a fictional demonstration. The entry page establishes a complete visual direction, with property details and viewing request 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 listing filters, property facts, floorplans. 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

- Listing filters
- Property facts
- Floorplans
- Neighbourhood guide

## Routes

- Entry: /preview/57-property-listing/start
- Property details: /preview/57-property-listing/property
- Viewing request: /preview/57-property-listing/viewing

## Reference and adaptation

- Page scope: Searchable catalogue.
- Distinct composition: deep-green property folio with large photography and a persistent facts rail.
- Typography: DM Sans.
- Tokens: page #f7f5ef, ink #253c35, accent #31594c.
- Pair large photography with a persistent property-facts rail. Search and viewing requests carry the chosen listing forward; the floorplan explains spatial arrangement rather than acting as decoration.
- 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.