# 75 Annual Report

**Philosophy and fit.** Tell the year’s story and show the evidence behind it. Built for public organisation, nonprofit, annual reporting. The visitor’s next step is to explore the report.

**Visual grammar.** Use a burgundy editorial report with oversized year numerals and clearly labelled financial tables. Preserve the hierarchy of achievements, financial data, project outcomes, sources; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** Northbank / Public library is a fictional demonstration. The entry page establishes a complete visual direction, with year in review and financial statements 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 achievements, financial data, project outcomes. 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

- Achievements
- Financial data
- Project outcomes
- Sources

## Routes

- Entry: /preview/75-annual-report/start
- Year in review: /preview/75-annual-report/results
- Financial statements: /preview/75-annual-report/finances

## Reference and adaptation

- Page scope: Digital publication.
- Distinct composition: burgundy editorial report with oversized year numerals and clearly labelled financial tables.
- Typography: Libre Baskerville / DM Sans.
- Tokens: page #f3ede3, ink #462d36, accent #79364e.
- An oversized year opens a paced digital publication. Narrative chapters explain achievements before financial tables and source notes; the sequence is a report to read, rather than a live dashboard to monitor.
- 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.