Diátaxis: The Four-Quadrant Framework for Structuring Technical Docs

Diátaxis is a documentation framework built on a simple insight: readers come to docs with four fundamentally different needs, and each deserves its own form. It splits content into tutorials (learning by doing), how-to guides (solving a specific problem), reference (looking up facts), and explanation (understanding the why). Rather than dictating implementation, it gives writers a lens for deciding what to write, how to phrase it, and where it belongs — the three questions that usually sink documentation efforts.

The framework’s appeal is that it’s lightweight and diagnostic. When a team can’t decide where a new page fits, the four quadrants force clarity about the user’s actual goal, which in turn exposes content that’s trying to do two jobs at once. That makes it as useful a tool for maintainers auditing existing docs as for teams starting from scratch.

Adoption signals matter here: Cloudflare leaned on it as the ‘north star’ for its developer-docs redesign, and Gatsby and Vonage report similar restructurings around the model. For engineering organizations where poor documentation quietly taxes every onboarding and support ticket, Diátaxis has become something close to a default reference for information architecture.