Playbook: Overhaul a neglected docs site

Sorted page types, working pipelines, and freshness signals readers trust again.

Track: 🗺️ Technical Writing · Domain: Journey Playbooks · Level: journey · ~80 min

Who this is for: Technical Writers, Developer Advocates, Engineers Who Document, Content Leads

When to Use This Skill

Sorted page types, working pipelines, and freshness signals readers trust again. Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

Journey Steps

1. Step 1 — Sort docs into types readers recognize: start with "Label every existing page: learning-journey, task-recipe, information-lookup, or theory"
2. Step 2 — Run docs through the same pipeline as code: start with "Store docs beside code or in sibling repo with same review gates"
3. Step 3 — Write changelogs users read: start with "Categorize: Added / Changed / Fixed / Breaking / Security only"
4. How it fits together: Sort types before rewriting anything. Half the mess resolves itself once modes separate.