documentation-writer

The Diátaxis framework structures technical documentation into four quadrants: tutorials, how-tos, references, and explanations. This approach aligns content objectives and tone to guide users from initial learning to practical mastery.

To write documentation across these four types, you provide a feature context to generate a Diátaxis-compliant draft. The output adapts content for diverse audiences, ensuring practical, actionable guidance with standardized frontmatter metadata.

Yes, the documentation workflow adapts content for novice developers, seasoned engineers, and product teams. It adjusts the tone and structure to ensure audience-focused writing across all generated technical documentation.

The best way to standardize metadata is using frontmatter-driven extraction at the top of the document. This ensures consistent discovery and indexing across software projects while maintaining Diátaxis-aligned content structure.

Yes, you can generate a complete documentation outline from a feature description. The workflow provides a repeatable process from acknowledgment to outline, culminating in final content across the four Diátaxis quadrants.

Diátaxis documentation structure is not suited for projects requiring narrative-driven content or single-page manuals. It is designed for software projects needing strict separation of tutorials, how-tos, references, and explanations across diverse audiences.