This document defines the identity standards for the manual across editorial, interface, supporting pages, and derivative surfaces.
It is source-of-truth documentation. The rules in this document should align with master artwork, design tokens, page templates, and live implementation.
the manual is the explanatory surface of the system.
Its role is to provide clear, structured, trustworthy answers to recurring cycling questions through reference pages, FAQ pages, glossary entries, tools, and selected entity profiles.
It is not a publication in the editorial sense. It is not a content feed. It is not a lifestyle brand. It is not a marketing layer.
Its authority comes from structure, clarity, and evidence.
fieldscout.cc is the root site. the manual is a distinct branded surface within that root domain, with canonical URLs under the /the-manual/ namespace.
Use the domain model consistently:
Do not treat fieldscout.cc alone as the canonical URL for manual content. Do not invent alternate namespaces for the manual.
Use naming consistently.
| Context | Form |
|---|---|
| Running brand name | the manual |
| Formal lockup | the manual by FSCC |
| Parent-domain reference | fieldscout.cc |
| Companion brand | Field Scout |
the manual remains lowercase in all uses.
The primary mark is the pennant. It is the core visual identifier of the brand and the basis for structural elements throughout the system.
Use the master pennant shape exactly as drawn. Do not redraw or reinterpret the geometry in downstream applications.
SVG Path
Do not stretch, rotate, skew, or add shadows, gloss effects, or gradients. Do not substitute alternate shapes.
Pennant markers classify content types across the system. They are not decorative badges. They are functional identifiers.
Chevron dividers are derived from the lower geometry of the pennant and act as the primary structural separator throughout the system. Use three hierarchy levels.
Chevron weight should decrease as hierarchy decreases. Do not use chevrons as decoration independent of structure.
Each core content type is assigned a fixed pennant color. These colors classify. They do not decorate.
Use them in pennant markers, type labels, section identifiers, and type-specific underline treatments where applicable. Do not introduce additional category colors.
Use a fixed three-family system.
| Family | Role |
|---|---|
| DM Serif Display | Editorial display titles only |
| Inter | Body copy, navigation, interface copy, tool titles |
| IBM Plex Mono | Labels, metadata, formulas, technical notation |
Approved uses: homepage title, article titles, selected formal openings such as the About page statement.
Do not use serif for section headings, navigation, tools, metadata, labels, or general interface copy.
Body text, section headings, tool titles, page titles that do not earn serif treatment, interface copy, navigation.
Labels, metadata, formulas, timestamps, technical support text, source labels, compact navigational utilities.
Do not use mono for body copy.
No essential operational text below 0.625rem. No informational support text below 0.6875rem where users must read or compare it. No small informational text below AA contrast.
Do not use tiny uppercase mono as pure texture where it is carrying meaning.
| Element | Size | Notes |
|---|---|---|
| Homepage title | 3.2rem | mobile / large responsive desktop |
| Article title | 2.8rem | mobile / large responsive desktop |
| FAQ answer / key answer text | 1.05rem | |
| Section heading | 1rem | |
| Body copy | 0.92rem | |
| Utility mono | 0.625rem | minimum |
| Metadata | 0.6875rem | minimum where informational |
The system is built on a restrained warm-neutral base.
Use supporting neutrals for hierarchy and surface separation.
Use color structurally. Do not use accent colors, decorative gradients, mood-setting chroma, or bright signals not tied to meaning.
All essential text must meet WCAG AA against the field background.
Do not assign low-contrast tones to captions, labels users need to interpret, table support text, operational metadata, or anything that carries meaning on its own.
If a text element is informational, style it as readable information, not as background texture.
Inline hyperlinks may use type-specific underlines to indicate destination class.
| Class | Underline | Target |
|---|---|---|
| .link--ref | #656260 | Reference article |
| .link--faq | #72633a | FAQ |
| .link--glo | #5a5650 | Glossary term |
| .link--tool | #2a2825 | Tool |
Link text stays in body color. Underline carries the classification cue. Hover increases underline thickness, not color drama.
Use a fixed template system.
Spacing is structural. Do not compress sections to fit more material.
| Body text max-width | 58ch |
| Vertical separation between sections | generous |
| Rhythm within paragraphs | tighter than between modules |
Let structure carry hierarchy before decoration does. If spacing, rules, or grouping can solve the problem, do not add graphic treatment.
This document is only useful if it remains exact. Maintain the following discipline:
If a choice makes the system feel more stylish but less exact, reject it.