Integrating documentation into development processes
Documentation is part of the software. Supplied with the product, it must:
- be released simultaneously,
- follow the same life cycles, and
- be subject to the same production and quality control processes.
Modular documentation sources in text format
Ideally, it should meet the following criteria:
- no vendor lock-in (independence of format and content editor),
- free and open publishing channels,
- fully automated layout.
Until a few years ago, the only tools available to deliver quality deliverables in PDF or HTML relied on binary and proprietary formats that didn’t integrate well with development teams’ version control systems.
As a result, technical documentation could not meet the same quality and time-to-market requirements as the products.
DocBook, then DITA XML, and reStructuredText have changed all that: these text formats can be edited with any type of program, from a simple text editor to a graphical IDE, integrating perfectly with Subversion, Git, or any other version control system.
Related articles
Section titled “Related articles”- Using branches in source management systems
- A single repository?
- From document to modular document base
Related reading
Section titled “Related reading”- A web journey: from HTML to Git-based Markdown workflows - bringing documentation into the development workflow.
- Why hand-maintained InDesign files rot - and what docs-as-code does instead - docs-as-code as part of the development pipeline.