Handbook
LCDL page layout taxonomy
Declare layout_type in YAML frontmatter using one of:
Updated
Layout types
Declare layout_type in YAML frontmatter using one of:
| Layout | Use for | Structure |
|---|---|---|
landing |
Homepage and audience/product entry pages | Hero, proof cards, path cards, how-it-works, next actions |
hub |
Start, Learn, Build, Reference, Enterprise, Agents, Contribute hubs | Mini-band, card grid, featured path, common tasks, next actions |
tutorial |
101/201/301 lessons | Outcome, prerequisites, steps, verify, next lesson |
howto |
Practical guide | When to use, recipe, code, pitfalls, verify |
reference |
API/spec/task details | Summary, stable identifiers, schemas, examples, failure modes |
enterprise |
Governance and operational pages | Decision context, controls, responsibilities, evidence, runbook |
concept |
“What is…” and mental models | Definition, why it matters, diagram, examples, non-goals |
Default page anatomy
Page hero / summary
Reader outcome
Main content chunks (3–5)
Verification or next action
Related pages
Context budget
Each page must make one promise and fulfill it. Split pages when they combine definition, tutorial, reference, and operations into one page.
Default word budgets (warnings only unless audit is strict)
| Kind | Words |
|---|---|
| Concept / top-level hub | 350–700 |
| Hub (section index) | 250–600 |
| Tutorial lesson | 450–900 |
| How-to | 500–900 |
| Reference | 600–1,200 (collapse or split if longer) |
| Enterprise runbook | 500–1,000 |
Tables and lists
- Prefer no more than 8 visible rows in a table before collapsing, splitting, or moving detail to another page.
- Card grids: 3–6 items per section where possible.
Longform escape hatch
Set longform_ok: true in frontmatter with a short longform_reason: when a page must exceed its budget (e.g. generated reference tables).