Take back control of your documentation
Docs-as-code gives you control of your content.
Your content stays in your repository. No proprietary format. No vendor lock-in. I’ve seen teams trapped:
Content locked in proprietary CMS
Export breaks formatting
5 years of docs, no clean way out
Forced to accept new pricing
With docs-as-code:
Content is markdown in Git
Build process you control
Host anywhere
Switch tools without losing content
This isn’t anti-SaaS (there are docs-as-code friendly platforms out there). It’s about keeping ownership of your docs so it does not become leverage for someone else.
P.S. I’m back on Substack with a weekly note on technical writing, docs-as-code, and automation. If you’re not interested, you can unsubscribe anytime.


I’m curious how you’d go about this at an enterprise level. How do you handle variables, conditions, generating output like help sites and PDFs?