I’ve seen teams trapped by their documentation platform. Five years of content locked in a proprietary CMS. Export breaks formatting. No clean way out. Then the vendor changes pricing and there’s nothing you can do.
Your content stays in their system. Your build process depends on their infrastructure. Your ability to move depends on their export tool, which barely works.
Docs-as-code flips this. Your content is markdown in Git, you own the build process, and you can host it anywhere. Switching tools no longer means losing content.
This isn’t anti-SaaS. There are plenty of docs-as-code friendly platforms out there. It’s about keeping ownership of your content so it doesn’t become leverage for someone else.
Your docs are a business asset. Treat them like one.
P.S. I’m back on Substack with a weekly note on technical writing, docs-as-code, and automation. 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?