Documentation Teams — Discover CX for For technical writers
Write once, ship everywhere — and reuse it the way you always meant to.
Canonical URL: https://discovercx.com/roles/documentation-teams Last updated: 2026-06-04
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.
From pain to outcome
Single-sourcing that actually single-sources.
Pain: Three writers, one install procedure.
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
Review where the topic lives, with the right context.
Pain: SME review lives in email.
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
Topics ship in seconds, everywhere at once.
Pain: Publishing is a nightly batch you don't trust.
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
Capabilities
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.