Docs-as-code is an approach that integrates software development tools and processes, such as source control, into documentation projects to enhance productivity and maintainability. Key to this approach is the use of branching strategies within git, which facilitates separate lines of work and collaborative efforts. The text outlines three primary branching strategies: trunk-based development, where changes are directly committed to the main branch; GitHub flow, which involves creating branches for each change and using pull requests for merging; and versioned branches, used for maintaining multiple versions of documentation concurrently. Each strategy has its advantages, such as simplicity in trunk-based development, thorough review processes in GitHub flow, and effective management of multiple versions in versioned branching. The choice of strategy depends on the project's specific needs, team size, and skill levels, with the flexibility to adapt and evolve these workflows as the project progresses. Various resources, including learning materials on git and tools like mermaid.js for visualizing workflows, support these docs-as-code practices.