The documentation gap
Documentation tools split into 2 camps. On one side: Paligo, MadCap Flare, Heretto. These enterprise CCMS platforms offer component reuse, conditional content, and multi-format publishing. They cost $3,150+/author/year, require weeks of training, and target teams of 25+ writers.
On the other side: GitBook, Confluence, Notion, Document360. Modern UX, fast onboarding, lower pricing. But no component-level reuse, no conditional content, and no real multi-format output. If you want to understand what a CCMS is and why it matters, start with the plain-language guide.
What small teams actually need
After a decade in enterprise documentation, I noticed a pattern. Teams of 2 to 10 writers need roughly 10% of what an enterprise CCMS offers — but that 10% is non-negotiable:
- Component reuse: write once, reference everywhere. Update the source and every reference updates.
- Conditional content: one topic, multiple audiences. Filter by product, plan, or platform.
- Variables: product names, version numbers, URLs. Change once, propagate everywhere.
- Multi-channel publishing: web, PDF, and API docs from the same source.
Everything else (translation management, three-way merge, XML round-tripping) serves teams an order of magnitude larger. The long version of that argument, with the pricing math, is in what a decade of enterprise CCMS taught me.
The block editor approach
Enterprise CCMS platforms were built in the DITA/XML era. They assume writers think in XML. Topicary assumes writers think in blocks, like Notion or Google Docs, but with structured authoring primitives built into the editor.
No XML, no training budget
A new writer can start producing content in an afternoon. Components, conditions, and variables are visual. You insert them from a slash command menu, not by writing markup. For a deeper look at Topicary's approach to structured authoring, see how Topicary provides reuse, conditions, and variables without XML.
Real-time preview
Conditional content filtering happens in the editor. Toggle an audience condition and see exactly what that audience will see, with no build step and no preview delay.
Import what you have
Drag a MadCap Flare project, a DITA map, a Confluence export, or a folder of Markdown files onto the import dialog. Format auto-detected, content mapped to Topicary's structured model, preview before you commit.
What Topicary does not do yet
Topicary now covers real-time co-editing, track changes, topic branching with three-way merge, release management, translation (XLIFF 2.0 + Phrase TMS), SSO/SAML, custom domains, and bidirectional GitHub sync. Two gaps remain: professional PDF composition (auto-numbering, back-of-book indices, master page layouts; Topicary's PDF has branded covers, page-numbered TOCs, and running headers, but not prepress-grade output) and inline/sentence-level content reuse (components are block-level only). If those are blockers, evaluate Paligo or MadCap Flare.
I publish this list because sending you to the right tool builds more trust than claiming I do everything. To see how Topicary compares to Paligo, the most feature-complete cloud CCMS, read the detailed comparison.
Try it
Start free. No credit card required. Import your existing content and see the difference.