Predrag Mandic talked about how the “documentation is code” principle saves money and time, empowers documentarians, simplifies processes around testing documentation and brings happiness to a diverse customer base.Jodie Putrino from F5 gave a practical account of her experience developing docs like code.Rachel Whitten from Pantheon give a talk on their implementation of these approaches.Margaret Eker and Jennifer Roundeau from Rackspace & Capital One, it was a great overview of Docs as Code.We had a panel with folks from Rackspace, Microsoft, Balsamiq, and Twitter, all talking about how they are adopting these practices.Riona MacNamara talked about how adopting Docs as Code has completely transformed how Google does documentation.Write the Docs has had a number of talks that touch on this topic over the years. In addition, there is an open source tool-chain which shows how the docs-as-code approach can be implemented Modern Technical Writing - Andrew Etter.There are a couple books we recommend that you check out: There is a lot more to building a proper Docs as Code workflow. You can block merging of new features if they don’t include documentation, which incentivizes developers to write about features while they are fresh.Developers will often write a first draft of documentation.Writers integrate better with development teams.

Generally a Docs as Code approach gives you the following benefits: It enables a culture where writers and developers both feel ownership of documentation,Īnd work together to make it as good as possible. This means following the same workflows as development teams,Īnd being integrated in the product team. Plain Text Markup (Markdown, reStructuredText, Asciidoc).Eric Holscher & the Write the Docs communityĭocumentation as Code ( Docs as Code) refers to a philosophy that you should be writing documentation with the same tools as code:

Code writing