You should use Git for all your internal documentation. Here’s why.
When I say Git, most people imagine something for programmers. I want you to see Git as a distributed version control system that goes beyond software.
Most corporations split their tools:
- code in GitHub/GitLab
- docs in Confluence/Google Docs
- discussions in chat
Modern tools try to merge docs with chat. Boundaries get blurry.
If you use Git for documentation, you get:
- one place for code and docs
- auditability
- accountability
- timestamped history via commits
- pull requests that carry the discussion
When I say this, I often hear: “Most people don’t know Git (or Markdown).”
I treat Git and Markdown as foundational. Learning the basics is part of onboarding. Everyone should know them.
With the right tools, writing in Markdown and committing to Git isn’t much harder than saving files to Google Drive. Most people can learn it in a day or two.
The key is to standardize the workflow — and document it in… Git.
What do you think?
Is this too radical — or just an obvious step most teams haven’t taken yet?
