# 69 Impact Nonprofit

**Philosophy and fit.** Connect a contribution to a specific, accountable project. Built for nonprofit, charity, environment. The visitor’s next step is to choose a contribution.

**Visual grammar.** Use a earthy campaign publication with project-led contribution allocation. Preserve the hierarchy of project outcomes, use of funds, contribution choices; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** Common Ground / River trust is a fictional demonstration. The entry page establishes a complete visual direction, with choose your contribution and project outcomes 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 project outcomes, use of funds, contribution choices. 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

- Project outcomes
- Use of funds
- Contribution choices

## Routes

- Entry: /preview/69-impact-nonprofit/start
- Choose your contribution: /preview/69-impact-nonprofit/contribute
- Project outcomes: /preview/69-impact-nonprofit/impact

## Reference and adaptation

- Page scope: Publication & action.
- Distinct composition: earthy campaign publication with project-led contribution allocation.
- Typography: Space Grotesk / DM Sans.
- Tokens: page #f0f0dc, ink #2b4336, accent #3b6a40.
- Connect the mission to named projects and transparent outcomes. The contribution flow explains how support is allocated; volunteering remains an equally clear route into the organisation.
- 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.