The Technical Writer trek
Plain language, docs-as-code, API documentation, tutorials, reference docs, and the tooling that modern technical writers use to ship documentation that developers love.
Writing fundamentals & plain language
Good technical writing is plain, precise, and purposeful. Learn the principles that make complex information understandable.
Docs-as-code & Git
Treat documentation like source code: version control, code review, CI/CD for docs, and the tools modern technical writing teams use.
API documentation
Reference docs, OpenAPI specs, authentication guides, code samples, and the documentation that makes developer APIs delightful to use.
Tutorials & how-to guides
The most valuable documentation type. Writing tutorials that actually teach and how-to guides that actually solve problems.
Static site generators for docs
Docusaurus, MkDocs, Sphinx, and the tools that turn Markdown into production documentation sites.
Code documentation
Writing inline comments, docstrings, READMEs, and changelogs that developers actually read.
Diagrams & visual documentation
When a picture is worth a thousand words — and when it isn't. Mermaid, draw.io, and the art of effective technical diagrams.
Docs testing & quality
Testing documentation like code: link checking, completeness testing, readability scoring, and keeping docs accurate as products change.
Information architecture for docs
Structuring large documentation sites so users can find what they need — navigation, search, and information hierarchy.
Developer experience & style guides
Developer experience for documentation: consistency, style guides, content governance, and building documentation programs that scale.
Capstone — documentation program
Build a complete documentation program for a real product: from strategy to published site to quality pipeline.
Trek complete. What's next?
You've walked the full roadmap. Now ship the capstone, write about it, and share the path with the next engineer who needs it.