Use the practical toolkit
Templates, checklists, and examples you can copy directly into your own project. Each item is clearly labeled as either a template (a starting point you adapt) or a worked example (a finished illustration you study).
Foundation
Section titled “Foundation”Information typesThe architectural foundation: Concepts, Tasks, and References, their relationship to DITA, and how they shape our authoring templates.
Templates
Section titled “Templates”Concept article templateDefinition, why it matters, key principles, examples, trade-offs.
Task article templateObjective, prerequisites, steps, expected result, troubleshooting.
Reference article templateOverview, syntax, parameters, examples, limitations.
API documentation templateOne endpoint per page: method, parameters, request/response, error codes.
Documentation project planGoal, audience, scope, format, success criteria, timeline.
Documentation review requestScope a review so it actually gets done.
Checklists
Section titled “Checklists”Documentation qualityRun before merging any documentation change.
Technical reviewWhat a subject-matter-expert reviewer should and shouldn't check.
Release readinessA gate for shipping docs alongside a product release.
Documentation migrationMoving between formats or platforms without losing content or URLs.
Docs-as-code adoptionFormat, version control, CI/CD, and team readiness.
Documentation auditFind orphaned pages, duplicates, and stale content.
Examples
Section titled “Examples”A well-structured Markdown pageAn annotated concept article, explaining each structural choice.
A documentation repository structureLocale-first content, separated from tooling and assets.
A basic docs-as-code workflowOne change, branch to production, annotated step by step.
A documentation review workflowSplitting technical review from editorial review, and why.
A practical CI/CD pipelineBuild, test, link-check, preview, deploy — annotated stage by stage.