We electronically control revisions for this topic and deploy it directly online. Any copies you generate from the latest revision are uncontrolled. Ensure you refer to the latest revision online when possible.
Latest revision: https://docs-as-code.com/2020/08/06/version-control.html
Using Git as a tool to version control documentation gives us complete transparency and control over content updates.
When developing documentation as code, we generally store our document as a Git repository.
Git tracks every update made to content within a repository via commits. We can tag the document at a specific time manually to version it, or rely on Git flows to analyze document changes.
This approach is scalable to even when we have dozens of collaborators working on the same content across a decentralized team. We can apply permissions to what user can update what branch, and whether a gatekeeper needs to approve a change.
Workflows to update tags manually should be defined by your company’s specific documentation workflows and included or referenced in the README.md file of your document.
Below is an example using a document lifecycle tool (GitLab in this case) to show us our document tags.