Templates (system docs)

System docs · templates

Canonical skeleton files live under the ZajLibrary authoring topic (page templates hub). This section is the agent registry — which spine to use, which live page proves it, and how types map to Learn · Build · Resources.

flowchart LR
  Agent[Agent or author] --> Registry["zajlibrary/authoring/content-system"]
  Registry --> Copy["resources/templates/page-templates"]
  Registry --> Example[Worked example page]
  Copy --> NewPage[New doc page]
  Example --> Verify[Verify spine match]

Rules

1. Copy the skeleton from Resources — never duplicate skeleton bodies here.
2. Verify against a worked example row below (or Examples shelf).
3. Enforce section order via Writing style → Doc-type spines.

Shelf registries

Learn templates Handbook, guide, concept, research, case study

Build templates Playbook set, runbook, SOP, checklist, blueprint

Resources templates Kit page, cheatsheet, reference meta, asset hub

Copy-paste entry points

Page templates hub All skeletons + asset starters

Writing style → Doc-type spines Required sections per kind

Formatting toolkit Headings, lists, Steps, FileTree

Quick reference (common types)

Template	Live example
Playbook overview	Setup-new overview
Playbook phase hub	Phase 1 · AI System
Playbook step	Machine setup
Kit page	AI System kit
Guide	Build an MCP server
Runbook	Code → test → ship
Handbook chapter	ZajModules vs customizations
Checklist	Staging first deploy
Concept	Content architecture
Handbook hub	Laravel CodeCanyon handbook
Blueprint	Blueprints hub
Cheatsheet	Laravel operations
Reference meta	Authoring capabilities
Asset starter hub	Laravel deployment starters
SOP	SOPs hub — no leaf SOP yet
Research	Research hub (stub)
Case study	Case studies hub (stub)

Per-type Sources and design rationale live on each page template file under Resources → Page authoring templates (last section).

Sources

• Diátaxis — tutorial / how-to / explanation / reference modes used as registry tags.
• Good Docs Project — Templates — installation and doc-type patterns (kit pages, procedures).
• Content architecture — shelf · type · path layout for ZajLibrary.