The Minds Behind Docs as Code – 7 People Redefining Software
Seven builders helped make documentation behave like software: stored as text, versioned with code, reviewed in changes, tested automatically, and published through repeatable pipelines.
TL;DR
Seven builders helped make documentation behave like software: stored as text, versioned with code, reviewed in changes, tested automatically, and published through repeatable pipelines. [1][2]
Why you should read it anyway
Documentation often decays because it lives outside the workflow that changes the product. Docs-as-code brings documentation into version control, review, CI, automated builds, and the same contribution model developers already use.
Imagine where Docs as Code would be without them
Without docs-as-code, documentation would remain more separated from engineering changes, making stale instructions, slow publication, ownership gaps, and inconsistent review more common.
Time Estimate of how many years we would be hindered without them for human progress
Editorial counterfactual estimate: 2–5 years. This is not a measured historical fact. It is an editorial estimate of how much slower the field might have matured without this cluster of people, systems, research, and practices.
The 7 people behind Docs as Code
1. Eric Holscher
Why they matter: co-founded Write the Docs and helped formalize docs-as-code as a community practice using version control, review, plain text, and automated publishing.[1]
2. Anne Gentle
Why they matter: wrote Docs Like Code and became a major advocate for applying software-development workflows to technical documentation.[2]
3. Riona MacNamara
Why they matter: helped advance docs-as-code practices at Google and publicly explained how large documentation teams could integrate with engineering workflows.[3]
4. Andrew Etter
Why they matter: wrote Modern Technical Writing and advocated lightweight, developer-friendly documentation systems based on plain text, static sites, and automation.[4]
5. Georg Brandl
Why they matter: created Sphinx, giving the Python ecosystem a powerful documentation generator built around text sources and automated builds.[5]
6. Tom Christie
Why they matter: created MkDocs, helping make Markdown-based static documentation sites simple to build and deploy.[1]
7. Dan Allen
Why they matter: led Asciidoctor and helped modernize AsciiDoc tooling for documentation pipelines, publishing, and docs-as-code workflows.[2]
How they each differ from one another
Holscher built the community; Gentle and Etter codified the philosophy; MacNamara demonstrated it at organizational scale; Brandl, Christie, and Allen built major text-to-documentation toolchains.
Final Take
Docs-as-code matters because it makes documentation part of the change itself rather than a separate task that everyone hopes someone remembers later.
Works Cited
- 01Write the Docs — Docs as Code writethedocs.org
- 02Docs Like Code — Anne Gentle docslikecode.com
- 03Sphinx Documentation sphinx-doc.org
- 04MkDocs mkdocs.org
- 05Asciidoctor asciidoctor.org
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead