What Is Docs As Code?
Docs As Code (also known as “Docs Like Code”) is a popular approach to delivering documentation for software projects.
There are three common themes that you can expect to see.
- Adopt an “agile” approach to content creation, namely
- The whole team is responsible for content
- Be adaptive and improve both your content, and your process, over time.
Tools and processes will need to be adapted for your project (and then adapted again for the project after that).
Docs As Code image copyright Anne Gentle. Released under and MIT license.
Why Do Docs As Code?
- Deliver valuable documentation faster with higher quality (multiple voices, collaboration)
- Stop documentation being a bottleneck in the release cycle
- Release technical writers to deliver higher value content (information architecture, customer experience, ....)
- Remove need for proprietary technical writing tools
How to do Docs As Code?
Use developer tools, and process, to create and deliver content. Specifically:
- Text based file content with embedded, lightweight, markup tags
- Developer based workflows. For example:
- Version Control using tools such as Git
- Change control driven though bugs and feature requests tickets
- Content reviews and merges
- Machine generated content
- Automated testing and verification
- Rapid online publication using web pages (using static site generators) or wikis. For example Sphinx or Hugo.
Look at Docs As Code
Links we love
Check out these great links which can help you dive a little deeper into running the Docs As Code practice with your team, customers or stakeholders.
Discuss with the Community