Components
Approved docs primitives
These are the approved interface pieces for the documentation layer. They are intentionally small in scale and engineered for stability, not spectacle.
Inline links and actions
Inline links should feel like text first and interaction second. Use subtle underline rules for navigational text and reserve heavier button treatments for deliberate actions only.
Inline link
Best for references inside paragraphs, notes, and cross-links between docs pages.
Rounded action
Use sparingly when a page needs one explicit next step.
Notes and callouts
| Pattern | Good for | Avoid |
|---|---|---|
| Quiet note card | Implementation warnings, rollout notes, and one-off cautions | General layout decoration |
| Dense reference card | Short comparative information | Long flowing article copy |
Section heading row
Section headings pair a compact title with a divider on the same row. This keeps long documents easy to scan without making the page feel like a stack of oversized headings.
Example section heading
Content shells
Document pages should keep a narrow reading column, light metadata, and a quiet local anchor rail. The shell is part of the component system because it controls how every approved pattern is read.
- Center the article column within a larger page frame.
- Keep local anchors visible on larger screens.
- Collapse the anchor rail cleanly on small screens.
- Prefer separators and rhythm over boxes and panels.