Every Page is Page One
by Mark Baker · Mark Baker
Baker argues that readers arrive at documentation mid-search rather than at page one, and shows how to write self-contained topics that establish their own context and link outward. Aimed at writers moving beyond linear manuals.
This link may earn us a small commission at no extra cost to you. Affiliate disclosure
More resources on Software Documentation
writethedocs.org
Write the Docs is a community resource hub for software documentation, offering practical guidance, articles, and talks on writing, structuring, and maintaining project docs, plus information about their conferences and events.
Architecture Decision Records (ADR)
The community hub for architecture decision records: templates, tooling, and worked examples. Readers come away able to capture a design decision with its context, options considered, and consequences in a short versioned file alongside the code.
Diátaxis Framework
Daniele Procida's model splits technical documentation into four distinct modes—tutorials, how-to guides, reference, and explanation—each with its own purpose and voice. After reading, you can diagnose why a docs set feels muddled and restructure it.
Write the Docs Podcast
Write the Docs is a series of conferences, local meetups, and Slack groups focused on all things related to software documentation. We consider everyone who cares about communication, documentation, and their users to be a member of our community. This can be programmers, tech writers, customer support, marketers, and anyone else who wants people to have great experiences with software. This podcast is focused on topics discussed and debated within this community.
API The Docs Podcast
Interview podcast from the API The Docs community, where technical writers, developer advocates and portal teams discuss API reference documentation, developer portal design, docs-as-code workflows and measuring documentation quality. Listeners gain practical ideas for planning and improving developer-facing documentation.
Docs for Developers
Five practitioners from Google, Stripe, and elsewhere follow a fictional product team through planning, drafting, editing, publishing, and measuring documentation. You finish with a repeatable workflow for shipping developer docs and deciding what to write next.