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. Training takes weeks. They are built for 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. Neither camp serves the middle. For the plain-language version, start with what a CCMS is.
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. 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 argument, with the pricing math, sits 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. Writers do not. Topicary assumes writers think in blocks, like Notion or Google Docs. The structured authoring primitives live inside 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. Nobody writes markup. For the deeper version, see Topicary's approach to structured authoring.
Real-time preview
Conditional content filtering happens in the editor. Toggle an audience condition and see exactly what that audience will see. No build step. 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. The format is auto-detected. Content maps to Topicary's structured model. You 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. The first is professional PDF composition: auto-numbering, back-of-book indices, master page layouts. Topicary's PDF has branded covers, page-numbered TOCs, and running headers. It is not prepress-grade output. The second is inline/sentence-level content reuse. Components are block-level only. If those are blockers, evaluate Paligo or MadCap Flare.
I publish this list on purpose. Sending you to the right tool builds more trust than claiming I do everything. Paligo is the most feature-complete cloud CCMS. The details are in how Topicary compares to Paligo.
Try it
Start free. No credit card required. Import your existing content and see the difference.