Git
Documentation pages on Git (8 pages).
A single repository?
A single Git repository for all technical documentation content maximizes reuse, consistency, and quality while simplifying collaboration across writing and dev teams.
Git: from file to content
Think content rather than files with Git: branches, commits, and diffs for technical documentation make collaboration and version management far simpler and safer.
Integrating documentation into development processes
Learn why technical documentation should be released, versioned, and quality-controlled alongside the product, using text formats like DocBook, DITA XML, and reStructuredText.
Managing a project from start to finish
It's pretty rare, in a professional context, to be able to manage a project from (almost) A to Z, from conception to realization and communication.
Repository
Content is a company's intangible capital. Learn how to choose and manage a documentation repository to protect, version, and share technical content across teams.
The Raspberry Pi 3 as a documentation platform
Set up a complete documentation platform on a Raspberry Pi 3: install Sphinx, generate PDF, HTML, and EPUB from reStructuredText, and manage content with Git.
Using branches in source management systems
Use Git branches to manage parallel documentation projects, product variants, and translation workflows without conflicts - a practical guide for technical writers.
Version management systems - rustic but reliable
Use Git or Subversion to manage technical documentation like source code: track changes, collaborate with your team, and roll back safely at any time.