Public documentation
Eliminate tool sprawl. Write once in Confluence. Publish everywhere with full branding, search, and analytics.
Because the site is generated as static HTML and served via CDN, docs typically load faster and with fewer moving parts than dynamic Confluence page views, which improves both user experience and SEO.
Help centres should not require a technology overhead. However, most teams struggle with scattered tools, outdated content, and constant manual work.
Documentation lives in Confluence, your help centre in Zendesk Guide, and customer-facing content elsewhere. Every update increasing the chance of inconsistencies.
Licenses for platforms like Zendesk, GitBook, and ReadMe add up fast, before you factor in implementation time, maintenance, and admin overhead.
When publishing requires multiple steps across disconnected tools, content inevitably goes stale. SEO suffers. Users get frustrated.
Write documentation in Confluence. Capable Sites transforms your space into a polished, public-facing documentation site automatically.
Your team spends more time writing and improving content, and less time maintaining tooling and duplication.
Write in Confluence Use your existing spaces, pages, and structure as your documentation source.
Publish with Capable Sites Apply branding, navigation, and search to create a help centre experience, without moving content.
#Settings that matter for this
Decision | Where |
|---|---|
Who can see it | Access modes |
Which spaces, in what order | Spaces and navigation |
How it looks | Theming your site |
Your own address | Setting up a custom domain |
#Related
A pattern, not a template.
