30-Day English for Technical Writers
Complete Learning Path

The path covers plain language principles, the Diataxis documentation framework, API documentation writing, SME interview technique, docs-as-code pull request workflows, changelog and release note writing, UX microcopy, and technical interview preparation — all the English a technical writer needs to work effectively in an international team.

Yes. Days 1–10 build the foundational vocabulary and Diataxis framework that any writer needs, regardless of background. Developers already comfortable with Git and PRs will find Week 3 (docs-as-code) especially fast to pick up, while Week 4 (UX writing, content strategy) introduces skills less familiar to engineers.

Week 2 (Days 11–15) focuses entirely on API documentation: endpoint and parameter description vocabulary, writing endpoint documentation, OpenAPI spec vocabulary, API versioning language, and code comment/docstring conventions.

Yes. Day 16 covers SME interview technique in depth: funnel questioning, restating answers for confirmation, and the diplomatic language used to push engineers for precision without appearing adversarial.

Yes. Days 17 and 18 cover writing documentation pull request descriptions, requesting the right kind of review from engineers, responding to review comments, and GitHub platform vocabulary including PR templates and CODEOWNERS.

Yes. Day 23 focuses on UX writing and microcopy — error messages, empty states, button labels, and confirmation dialog language, which is increasingly expected of technical writers contributing to product UX.

Day 21 covers changelog and release note writing: the "Keep a Changelog" conventions, flagging breaking changes, and calibrating register for developer-facing versus customer-facing release notes.

Yes. The path is marked Beginner–Intermediate and starts with foundational plain-language and Diataxis vocabulary before progressing to more advanced topics. If you are completely new to technical writing, spend extra time on Days 1–10 before moving forward.

After the 30-day path, explore the Technical Writer guide for comprehensive reference material, or browse /exercises/technical-writing/ for additional exercises. If your role involves API-heavy documentation, the Backend Developer path is a useful complement.