documentation-structure
How to architect a documentation set with the Diátaxis framework — separating tutorials, how-to guides, reference, and explanation, then wiring information architecture, navigation, audience mapping, search, and docs-as-code so each reader lands on the page they need. With examples and a runnable structure linter.
Included with Vanara Pro ($10/mo) — unlocks all 206 items. See pricing →
Overview
Most documentation fails not because the writing is bad but because the structure is bad: four different jobs are crammed onto one page, so the newcomer drowns in API options and the expert wastes time wading through a beginner's tutorial. Good documentation structure makes a docs set navigable by intent — a reader who knows *why* they came can find *where* to go in one or two clicks. This skill i
What it covers
- Mental model: documentation serves intent, not topics
- The four quadrants in practice
- Information architecture and navigation
- Audience mapping and findability
- Docs as code
- Audience mapping & findability
- Diátaxis — the four quadrants in depth
- Information architecture & navigation