Why Topicary
The gap between easy and powerful
Why I built a CCMS for teams of 2–15 writers — and what that means for your documentation.
The gap
Easy tools vs powerful tools
Documentation tools split into two camps. On one side: Paligo, MadCap Flare, Heretto. Structured authoring — content reuse, conditions, multi-format publishing. They cost $2,999+/author/year (Flare Desktop) to $32,680/year median (Paligo), 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.
A sweep of 200+ documentation tools (May 2026) confirmed this: zero tools offer component-level content reuse, conditional content, and multi-channel publishing in a cloud-native interface below $185/mo.
Independent software
Bootstrapped. No venture capital.
Topicary is bootstrapped. No venture capital. No board to satisfy. No pivot toward enterprise sales when the growth metrics dip. I built this because I needed it and couldn't find it. That means no acqui-hire risk, no “sunsetting” announcement, no forced migration to a platform you didn't choose. I publish a dated changelog with every feature shipped.
Migration
Import details by format
Drag a file or zip onto the import dialog. Format auto-detected, preview before you commit.
| Format | Transfers | Does not transfer |
|---|---|---|
| Markdown | Headings, paragraphs, lists, code blocks, images, tables, links | Front matter (preserved as raw text) |
| HTML | Semantic structure, tables, images, links, lists | JavaScript, external stylesheets, embedded scripts |
| DITA | Concepts, tasks, references, ditamaps with hierarchy, conrefs as component references | Relationship tables, specializations, subject schemes |
| Confluence | Pages, hierarchy, macros (cleaned/converted), images, tables | Confluence-specific macros (Jira, Roadmap), user mentions |
| MadCap Flare | Topics, snippets as components, TOC as maps, variables, conditions | Micro content, target settings, custom stylesheets, skins |
| Word (.docx) | Headings, paragraphs, lists, tables, images | Track changes, comments, embedded objects, macros |
| OpenAPI 3.x | Endpoints as topics with method badges, schemas, parameters, examples | Server-side validation, webhook definitions |
Comparison
Feature by feature
| Capability | Topicary | Paligo | MadCap Flare | GitBook |
|---|---|---|---|---|
| Content reuse | Block-level components, where-used tracking, orphan detection | Block + inline (text fragments), reuse dashboard | Snippets, cross-project linking | Reusable blocks (no tracking, no conditions) |
| Conditional content | Dimensions + values, per-block include/exclude, in-editor preview | Dimensions, filter sets, profiling dashboard | Conditions, target-based filtering, expressions | Not supported |
| Variables | Variable sets, key-value pairs, publish-time replacement | Variable sets, scoped + taxonomy variables | Variable sets, target-level overrides | Not supported |
| Web publishing | Hosted, dark mode, AI search, feedback, custom CSS | Paligo Hosting (Netlify), self-host, Zendesk/Salesforce | Self-host, context-sensitive help | Hosted, custom domain, clean UX |
| PDF output | Branded cover, TOC, header/footer, custom font | Full page layout, running headers, TOC with page numbers | Full print — auto-numbering, index, page layouts | Basic export (Pro feature) |
| Import formats | 7 (MD, HTML, DITA, Confluence, Flare, Word, OpenAPI) | 4 (DITA, Word, HTML, Markdown) | DITA, Word, RoboHelp, HTML | Markdown, GitHub |
| SME review | Token-based, no login, inline comments, approve/reject | Contributor accounts required, comment-only | No built-in review | Not supported |
| Translation | Not supported | XLIFF, 6+ TMS integrations | Lingo, XLIFF | Not supported |
| Real-time collab | Not supported | Supported | Not supported (desktop) | Supported |
| Content branching | Publication versioning | Branching + three-way merge | Not supported (uses source control) | Draft/merge workflow |
Honest positioning
What Topicary doesn't do yet
Topicary is a shipping product, not a finished one.
- Real-time collaborative editing — Two writers cannot edit the same topic simultaneously. Different topics, no conflict.
- Suggest mode / track changes — Reviewers can comment but cannot propose inline edits for author accept/reject.
- Three-way merge — Publication versioning lets you maintain v1 and v2 docs side by side with independent publishing. Paligo additionally supports three-way merge (source, target, merged output) and release lifecycle management — Topicary does not.
- Translation / XLIFF — No localization pipeline. English-first teams are the current audience.
- SSO / SAML — Email + password authentication. Enterprise SSO is on the roadmap.
- Custom domains — Published sites use Topicary subdomains. The database schema exists; the code path does not.
- Word export — Export to PDF, Markdown, and DITA XML. Word (.docx) is not available.
If any of these are requirements — not nice-to-haves but blockers — Paligo supports translation and three-way merge with release lifecycle management. MadCap Flare supports Word export and print-production PDF. I link to their documentation on the comparison pages because sending you to the right tool builds more trust than claiming I do everything.
Help build the tool that's missing
Free during beta. All features, no limits. Your feedback shapes what ships next.