Adopt docs-as-code
Version control, branching, and continuous integration applied to documentation - plus the practical tutorials for the text-processing and automation tooling this workflow depends on.
Process and tooling
Section titled “Process and tooling”Integrating documentation into developmentAligning release cadence, version control, automated testing, and CI/CD pipelines.
Version control systemsWhy version control matters for documentation, not just code.
Git: from file to contentThinking of Git as a content history, not just a file history.
Using branchesBranching strategies for parallel documentation work.
The repositoryWhat belongs in a documentation repository, and how to structure it.
A single repositoryThe case for keeping documentation and code in one place.
Which repository for group workChoosing a repository model when multiple writers collaborate.
Shared network directoriesWhy shared drives fall short for collaborative documentation work.
SQL databasesWhen a database-backed repository makes sense — and when it doesn't.
CMS workflow and reliabilityThe workflow benefits of a CMS, weighed against its reliability trade-offs.
Hands-on tutorials
Section titled “Hands-on tutorials”sed: modify your text without opening your filesBatch find-and-replace across hundreds of files in one command.
Regular expressions in PythonText manipulation for documentation automation scripts.
The Raspberry Pi 3 as a documentation platformA minimal, low-cost publishing pipeline.
Managing a project from start to finishOne project traced from intake through delivery.
Working with DITA XML or single-sourcing instead? See structured authoring.