Templates
These templates describe the recommended structure for each page type. They are defined in full in the project's article_scheme.md and summarized here for quick reference.
Frontmatter
Every page starts with YAML frontmatter:
---
id: <unique-id>
title: <Page Title>
sidebar_position: <number>
description: <one-line summary shown in search and listings>
---
Page Type Templates
Product page (products/{model}/index.md)
Used for any single product.
- One-line positioning statement ("what is this and who is it for").
- Specifications table.
- Overview paragraph(s).
- Driver / firmware install (add a Mermaid flow when steps are non-trivial).
- Advanced usage.
- Compatibility table.
- Troubleshooting.
- Related resources links (absolute paths).
Setup / guide page
- Learning objective.
- Concept explanation.
- Prerequisites checklist.
- Step-by-step
Step 1..Nblocks, each with a ```bash command and its expected output. - Verification step.
- Common errors table.
- References.
Comparison page
- Conclusion first.
- Quick comparison table.
- Deep-dive analysis.
- Scenario-based recommendation.
- Test data (if any).
Troubleshooting page
- Diagnosis-first decision tree (Mermaid flowchart).
- Problem index table.
- For each issue: Symptom / Diagnostic / Root cause / Fix.
- "Still stuck?" → Review Queue.
Diagram Rules
- Inline flow/sequence diagrams: Mermaid.
- Hero / highlight diagrams: standalone SVG stored under
static/img/{article-id}/.
DoD (Definition of Done)
- Frontmatter present and
idunique. - Structure matches the matching template.
- At least one diagram on setup/guide/troubleshooting pages.
- Every ```bash command actually tested; include expected output.
- Internal links use absolute route paths (no
../). - No
TODO/TBDplaceholders. npm run build:enpasses with zero broken links.
Related
Review Queue— where new content is checked before it ships.Change Log— records what changed and when.