Authoring docs checklist
Not a deploy operation — use when creating or restructuring CodeCanyon documentation during inbox intake.
Pick a pattern
Section titled “Pick a pattern”| Type | Route | Template / gate |
|---|---|---|
| Playbook step | build/playbooks/laravel/codecanyon/… | Playbook step template + stepNumber contract |
| Runbook / micro-WF | build/runbooks/codecanyon-laravel/… | Terse commands + link back to playbook |
| Concept / theory | learn/handbooks/laravel/codecanyon/… | Warrant-test diagram required |
| Learn guide | learn/guides/laravel/codecanyon/… | Read-once; :::start / :::next on long pages |
Pre-publish (all types)
Section titled “Pre-publish (all types)”- Placeholders (
<PROJECT>,<YOUR_DOMAIN>) — no real secrets or instance paths - Local and production instructions where both apply
- Verification after each risky step (
# Expected:on commands) - Troubleshooting table or abort conditions
- Writing style QC + build green
Agent intake
Section titled “Agent intake”During _INBOX/ processing, record each source in the topic COVERAGE ledger (content-intake skill) — never link inbox paths from published pages.