Guide Design Spec (Internal)¶
Use this template when creating or refactoring guides.
Section Order¶
- Front matter (title = H1)
- Intro (1–2 sentence purpose tagline)
- At a Glance (card grid) – required
- Prerequisites (checklist) – if actionable preconditions exist
- Core Flows / Steps (may use content tabs for variants)
- Supplementary Sections (e.g. Gallery, Content Sections) – optional
- Progress / State (if downloads or async operations relevant)
- After Action / Outcomes
- Troubleshooting (collapsible groups) – anchor: #troubleshooting
- Next Steps (card grid linking related guides)
Mandatory Headings & Anchors¶
- At a Glance:
## At a Glance - Troubleshooting:
## Troubleshooting {: #troubleshooting } - Next Steps:
## Next Steps
If historic anchors existed (e.g. #progress, #after-import), preserve them with explicit IDs: ## Progress {: #progress }.
Card Grid Pattern¶
<div class="grid cards" markdown>
- :material-ICON:{ .lg .middle } __Title__
---
One-line description.
[:octicons-arrow-right-24: Anchor Text](#anchor)
</div>
Admonition Usage¶
- info: neutral context / clarifications
- tip: productivity or optimization hints
- warning: caution / potential data loss
- danger: destructive / irreversible actions
- success: outcome confirmation
- question: FAQs style
- failure: explicit failure scenario
Collapsible groups: use ??? (add + to default-open). Keep titles concise.
Content Tabs¶
Use for mutually exclusive procedural variants (e.g. Object vs Material vs Height Map). Avoid tabs for linear steps.
Checklists¶
Use simple task list markdown for prerequisite verification or multi-step confirmation sequences.
Icons¶
Prefer :material-*:. Keep consistent size modifiers (.lg .middle) only inside card grids.
Inline IDs¶
When renaming a heading that had inbound links, add explicit ID with previous slug.
Example: ## Troubleshooting & Tips {: #troubleshooting } → ## Troubleshooting {: #troubleshooting }.
Image / Media Placement¶
- Favor right-aligned responsive media with max width 50–55% when paired with text.
- Always set
aria-labelandtitlefor<video>elements.
Tone & Style¶
- Present tense, imperative for steps.
- Sentence fragments allowed in cards & table cells.
- Avoid redundant phrases ("Click the button" → "Click Purchase").
Accessibility¶
- Provide captions for figures.
- Use checklist icons or color as decoration only; ensure text conveys meaning.
Example Skeleton¶
---
...front matter...
---
# Title
Short purpose sentence.
## At a Glance
<div class="grid cards" markdown>
...cards...
</div>
## Prerequisites
:octicons-check-circle-fill-16: Checklist style or bullets.
## Steps
=== "Variant A"
1. ...
=== "Variant B"
1. ...
## Progress {: #progress }
...optional...
## After Action {: #after-action }
...outcome notes...
## Troubleshooting {: #troubleshooting }
??? question "Common issue"
Fix.
## Next Steps
<div class="grid cards" markdown>
...related links...
</div>
Change Log¶
- v1 (2025-08-15): Initial extraction and consolidation.