# 56 Renovation Proof

**Philosophy and fit.** Show the work, its constraints, and how it changed a place. Built for renovation, contractor, landscaping, roofing. The visitor’s next step is to request an estimate.

**Visual grammar.** Use a ochre and charcoal construction journal with a large matched comparison. Preserve the hierarchy of before and after, project specifications, budget bands; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** FOUND / Renovation is a fictional demonstration. The entry page establishes a complete visual direction, with estimate request and project dossier 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 before and after, project specifications, budget bands. 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

- Before and after
- Project specifications
- Budget bands

## Routes

- Entry: /preview/56-renovation-proof/start
- Estimate request: /preview/56-renovation-proof/estimate
- Project dossier: /preview/56-renovation-proof/project

## Reference and adaptation

- Page scope: Portfolio & enquiry.
- Distinct composition: ochre and charcoal construction journal with a large matched comparison.
- Typography: Space Grotesk / DM Sans.
- Tokens: page #efeee7, ink #30352f, accent #6a4d20.
- The before/after comparison is the lead evidence plate. Tie its caption and project facts to a sequence of milestones and a scoped estimate request; never present the generated example as completed client work.
- 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.