Handbook hub template

When to use

• Shelf: learn/handbooks/<topic>/index.mdx
• kind: handbook (collection hub — not a chapter)
• Diátaxis mode: explanation (orients before deep chapters)
• Readers served: readers choosing which chapter to read; agents routing to the right concept page

Design rationale

• Handbooks are explanation collections — hub orients the mental model before chapters (Diátaxis explanation).
• Map or diagram first — relationship between chapters warrants a visual (warrant test).
• CardGrid for chapter entry — scannable navigation beats prose lists (NN/g scanning).
• Reading order table — optional numbered path for beginners without forcing linear read.
• No step checklists on hub — verification belongs in playbooks, not handbook hubs.

Copy-paste skeleton

---
title: "<Handbook title>"
description: One sentence — what mental model this handbook builds.
kind: handbook
status: current
tags: [handbook, topic]
---

import { CardGrid, LinkCard } from '@astrojs/starlight/components';

<p class="eyebrow">Handbook · &lt;topic&gt;</p>

&lt;Outcome paragraph — who this handbook is for.&gt;

## Map

\`\`\`mermaid
flowchart LR
  …
\`\`\`

## Chapters

<CardGrid>
  <LinkCard title="01 · …" href="/tech-stack/laravel/codecanyon/learn/handbooks/01-zajmodules-vs-customizations/" description="…" />
</CardGrid>

| Order | Chapter | You'll understand |
| --- | --- | --- |
| 1 | […](/tech-stack/laravel/codecanyon/learn/handbooks/) | … |

Anti-patterns

• Do not use playbook step spine or :::next on handbook hubs.
• Do not teach procedural deploy steps — link to Build playbooks instead.

Worked example

• Laravel CodeCanyon handbook

Sources

• Diátaxis — Explanation — handbook hub orients understanding before depth.
• NN/g — How users read on the web — scannable hubs and short intros.
• Diátaxis — Overview — handbooks vs guides vs tutorials.
• Writing style → Doc-type spines