Designed for · For technical writers
Documentation Teams
Writers don't need another editor. They need a repository that actually works, an SME review flow that doesn't live in email, and a delivery layer they don't have to argue with. Discover CX gives documentation teams structured authoring on top of a typed component store — and lets the work compound.
What changes
From the pain you know
to the outcome you wanted.
Pain
Three writers, one install procedure.
Outcome
Single-sourcing that actually single-sources.
Conrefs, keyrefs, conditional processing, profiling, and branching — all native, all in one repository. When the part number changes, you change it once and seven topics update. Translation memory catches up automatically.
DITA 1.3 · conrefs · keyrefs · conditional · profiling
Pain
SME review lives in email.
Outcome
Review where the topic lives, with the right context.
Custom workflow states, inline comments, tracked revisions, multi-step approval, scheduled publishing. SMEs sign off on the topic itself — not on a Word doc someone exported on Tuesday.
Workflows · approvals · revisions · audit trail
Pain
Publishing is a nightly batch you don't trust.
Outcome
Topics ship in seconds, everywhere at once.
DITA-OT outputs HTML5, PDF, Markdown, EPUB. The Delivery API serves the same content as typed JSON to portals, in-product help, partners, and AI assistants. No drift between staged and published.
HTML5 · PDF · JSON · real-time
For your role
Capabilities that show up in the work.
Editor of choice
Oxygen, Fonto, Simply XML, the Discover CX editor, or your IDE with Git. Pick what fits the writer — repository stays single.
AI co-authoring (opt-in)
Draft, summarize, restructure, validate. Every suggestion stays version-controlled and SME-reviewable. Off by default.
Translation management
XLIFF 2.1 round-trip with Smartling, Lilt, XTM. Locale fan-out from a single source. TM native.
Branching for releases
Major releases get their own branch. Minor fixes merge back. The repository enforces structure — your writers don't have to.
Reuse analytics
See what's reused, where, and how often. Find candidates for further reuse. Spot stale conrefs before they bite.
Migration included
MadCap, Paligo, Heretto, IXIASOFT, Confluence — a migration engineer owns the move end-to-end.
Where it lives
One platform.
Three products.
Discover CX is one platform — but you can start with the product that fits the work in front of you. The pieces that matter for documentation teams:
Other roles
The same platform, framed for the rest of your team.
For technology leaders
CIOs & Heads of Knowledge
Make your product knowledge AI-ready before someone else does.
For service operations
Field Service
First-time-fix the hard ones — with answers technicians can find on the truck.
For service & support teams
Customer Support
Cut handle time. Cut escalation. Cut the "let me check on that".
See Discover CX for documentation teams, on your content.
A solution architect walks the platform with your real work in mind — your team, your stack, your roadmap.