# 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

  - [**Integrating documentation into development**](https://docs.redaction-technique.org/en/tech-writing-process/integrating-documentation-into-development/): Aligning release cadence, version control, automated testing, and CI/CD pipelines.
  - [**Version control systems**](https://docs.redaction-technique.org/en/tech-writing-process/version-control-systems/): Why version control matters for documentation, not just code.
  - [**Git: from file to content**](https://docs.redaction-technique.org/en/tech-writing-process/git-from-file-to-content/): Thinking of Git as a content history, not just a file history.
  - [**Using branches**](https://docs.redaction-technique.org/en/tech-writing-process/using-branches/): Branching strategies for parallel documentation work.
  - [**The repository**](https://docs.redaction-technique.org/en/tech-writing-process/repository/): What belongs in a documentation repository, and how to structure it.
  - [**A single repository**](https://docs.redaction-technique.org/en/tech-writing-process/single-repository/): The case for keeping documentation and code in one place.
  - [**Which repository for group work**](https://docs.redaction-technique.org/en/tech-writing-process/which-repository-for-group-work/): Choosing a repository model when multiple writers collaborate.
  - [**Shared network directories**](https://docs.redaction-technique.org/en/tech-writing-process/shared-network-directories/): Why shared drives fall short for collaborative documentation work.
  - [**SQL databases**](https://docs.redaction-technique.org/en/tech-writing-process/sql-database/): When a database-backed repository makes sense — and when it doesn
  - [**CMS workflow and reliability**](https://docs.redaction-technique.org/en/tech-writing-process/cms-workflow-and-reliability/): The workflow benefits of a CMS, weighed against its reliability trade-offs.

## Hands-on tutorials

  - [**sed: modify your text without opening your files**](https://docs.redaction-technique.org/en/tutorials/sed-text-editing/): Batch find-and-replace across hundreds of files in one command.
  - [**Regular expressions in Python**](https://docs.redaction-technique.org/en/tutorials/python-regular-expressions/): Text manipulation for documentation automation scripts.
  - [**The Raspberry Pi 3 as a documentation platform**](https://docs.redaction-technique.org/en/tutorials/raspberry-pi-documentation-platform/): A minimal, low-cost publishing pipeline.
  - [**Managing a project from start to finish**](https://docs.redaction-technique.org/en/tutorials/project-end-to-end/): One project traced from intake through delivery.

Working with DITA XML or single-sourcing instead? See [structured authoring](https://docs.redaction-technique.org/en/structured-authoring/).

---

Source: https://docs.redaction-technique.org/en/docs-as-code/