Hello there,
Anyone have experience with Docs as Code for Confluence? I could see that this concept is not entirely new. It does seem like a smart move to source code your crucial operational documentation and deploy the confluence pages using standard CICD pipelines.
Good question, the short answer is: not natively, but there are ways to get close.
The classic docs-as-code approach (write in Markdown, commit to Git, publish via CI/CD)
doesn't map perfectly to Confluence's storage format. You'd be fighting the platform.
What works better in practice is flipping the flow: instead of writing docs as code,
you let AI generate Confluence pages from your code automatically.
I built CodeDoc AI for Confluence for exactly this. You connect your GitHub, GitLab,
Bitbucket or Azure DevOps repo, choose what to generate (README, API docs, architecture overview, changelog, etc.) and set a trigger — on every merge, on a schedule, or manually.
The result lands as a structured Confluence page. No manual writing, no CI/CD pipeline
to maintain for docs.
It's not docs-as-code in the traditional sense, but it solves the same underlying problem:
keeping Confluence in sync with what the code actually does.
Marketplace link if anyone wants to try it: https://marketplace.atlassian.com/apps/2654352538
Welcome to the Atlassian Community!
Treating docs as though they are code is never a bad idea.
But Confluence is a wiki, not a file store, so, the first thing to look at is converting your docs to something more accessible than files in a fixed and non-shared format. Why not just upload your docs as Confluence pages directly?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.