# 74 Modern Docs Portal

**Philosophy and fit.** Make the next implementation step easy to locate and verify. Built for developer tools, software, api documentation. The visitor’s next step is to complete a quickstart.

**Visual grammar.** Use a light technical documentation with a three-column reading architecture. Preserve the hierarchy of versioning, sidebar navigation, code examples, quickstarts; these patterns solve this business’s actual decision, rather than supplying interchangeable decoration.

**Sample and interaction.** Vector / Developer docs is a fictional demonstration. The entry page establishes a complete visual direction, with quickstart guide and api reference 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 versioning, sidebar navigation, code examples. 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

- Versioning
- Sidebar navigation
- Code examples
- Quickstarts

## Routes

- Entry: /preview/74-modern-docs-portal/start
- Quickstart guide: /preview/74-modern-docs-portal/quickstart
- API reference: /preview/74-modern-docs-portal/reference

## Reference and adaptation

- Page scope: Documentation site.
- Distinct composition: light technical documentation with a three-column reading architecture.
- Typography: DM Sans.
- Tokens: page #fafbfd, ink #2c3545, accent #444f9d.
- Use the familiar documentation hierarchy: versions, page navigation, a reading column and in-page contents. Code and response examples follow the selected version; this is a conventional counterpart to Terminal Manual.
- 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.