§00 — Typography
Typography sets the whole interface contract: what matters, what can be scanned, what needs action, and what should stay quiet. This page is the QA baseline for headings and spacing across the showcase.
Display type belongs to the manual chrome and page titles. Product UI stays calm: compact headings, readable body copy, mono only for metadata, shortcuts, and tabular values.
§01
The app scale is intentionally short. Larger type is reserved for true page-level context.
The fixed hierarchy used by product pages and showcase routes.
§01
A page should read from the top down without fighting itself: H1, lead, note, section, card.
The exact rhythm pages should follow before adding any component demos.
Procurement desk
The heading states the job. The lead explains the context. The next section should carry the work, not another introduction.
Notes are for constraints, caveats, or operating context. They should not become a second paragraph of sales copy.
§01
Operational tools live or die by scannability: numbers, labels, timestamps, and status must line up.
Numeric and metadata treatment for dense product surfaces.
The writing style that keeps app pages consistent.
One page H1, one clear job.
Operational labels beat marketing copy.
Numbers align and stay scannable.
Mono is for structure, not paragraphs.
§01
Mono is a structural accent: section numbers, tokens, keyboard hints, versions, timestamps.
Where the manual voice may use mono without degrading readability.