Discover CCMS
A component CCMS designed around the repository, not the editor. DITA, Markdown, and HTML in one source. Author in Oxygen, Fonto, Simply XML, the browser, or your IDE. Reuse, review, translate, publish.
Canonical URL: https://discovercx.com/platform/ccms Last updated: 2026-06-04
Structured content, written where your team already works.
A component content management platform built around the repository — not the editor. Author in DITA, Markdown, or HTML, using Oxygen, Fonto, Simply XML, the browser, or your IDE. One source. Every channel.
Repository — the system of record
- Component repository — Every topic, image, snippet, and map is a versioned component. Not a file. Not a wiki page. A typed object you can govern.
- Branching & merging — Major releases get their own branch. Minor fixes merge back. The repo enforces structure — your writers don't have to.
- Audit & access — RBAC down to the project, branch, and component. SAML, OIDC, SCIM. Every change attributed and exportable.
- Taxonomy you own — Product, audience, version, locale — typed metadata, not folder names. Filters, conditions, and publishing all key off it.
Authoring surfaces — pick your team's tools
Oxygen XML (Native)
Pro writers
Web and Desktop. Full DITA fidelity, schema validation, structured editing. The XML editor of choice.
Discover CX editor (Built-in)
Built for your team
Our browser-based authoring client. Built on Fonto, extended with AI assist, native comments and revisions, Oxygen round-trip, and usage analytics. No install, no IT ticket — see the deep dive below.
Simply XML (Native)
SMEs in Word
Your SMEs already use Microsoft Word. Simply XML lets them draft structured topics there without retraining.
Fonto (Native)
External Fonto licenses
If your team already runs standalone Fonto, we integrate natively. Most teams use the built-in Discover CX editor instead — same engine, more capability.
IDE + Git (For engineers)
Doc-as-code teams
VS Code, IntelliJ, Cursor — anything that speaks Git. Lint and preview locally. Push a PR. We open a review task.
Content formats
DITA (Structured)
Native, end-to-end. DITA 1.3, DITA-OT 4.x. Concept, task, reference, glossary, and your specializations. Conrefs, keyrefs, conditional processing — all of it.
Markdown (Lighter & faster)
Lighter and faster than DITA — perfect for engineering docs, READMEs, release notes, and in-product help. Same repository, same publishing pipeline.
HTML (Bridge)
For legacy imports, marketing-adjacent content, and bespoke knowledge articles. Schema-validated, not free-text.
Mixed in one repo (DCX-only)
Cross-format conrefs. A DITA topic can reuse a Markdown snippet. Engineering and writing converge instead of forking.
Operations
Reuse & single-sourcing
Conrefs, keyrefs, conditional processing, profiling, branching. Write once, ship to every channel and product line.
Workflow & review
Custom states, multi-step approvals, scheduled publishing. Inline review and SME sign-off built in.
Translation
Locale fan-out from a single source. XLIFF 2.1 round-trip with Smartling, Lilt, XTM. Translation memory native.
AI co-authoring
Generate first-draft topics, summarize for short-form, validate structure. SME-safe, version-controlled. Optional, not enforced.
Multi-format publishing
DITA-OT pipeline outputs HTML5, PDF, Markdown, EPUB — and feeds the Delivery API simultaneously. No nightly rebuild.
Migration
Inbound from MadCap, Paligo, Heretto, IXIASOFT, Confluence. A migration engineer owns it end-to-end. No fidelity loss.
FAQ
Is Discover CCMS DITA-only?
No. DITA, Markdown, and HTML are all first-class authoring formats — in the same repository, with cross-format conrefs. Heretto and IXIASOFT are DITA-only. DCX lets engineering write in Markdown while documentation writes in DITA, with both flowing through the same publishing pipeline.
Can we keep our existing editor?
Yes. Oxygen (Web + Desktop), Fonto, and Ingeniux Simply XML for Microsoft Word are natively integrated. Doc-as-code teams use any IDE that speaks Git. The repository is the system of record — the editor is whatever your team already knows.
How does the Git option work?
Each project is exposed as a Git remote. Authors clone, branch, edit locally, lint and preview, then push a PR. The CCMS UI and the Git surface read from the same repository — there's no two-way sync, no drift, no merge surprises. Git is one authoring surface, not the whole product.
How does this compare to Paligo?
Paligo is a strong cloud-only structured editor. DCX gives you the same structured authoring plus a true component repository, mixed format support (not DITA-only), and an integrated Delivery API and customer portal. Paligo's strength is the editor; DCX's strength is what sits behind it.
How does this compare to Heretto?
Heretto is a strong cloud DITA-only CCMS with the Deploy portal as a separate add-on. DCX handles DITA + Markdown + HTML in one repo, ships with a real Git surface as an optional authoring path, and the Discover portal is included in the platform — not a separate license.
Can we migrate from MadCap Flare, Paligo, Heretto, or IXIASOFT?
Yes. Migration is included with Business and Enterprise engagements. A dedicated migration engineer handles conversion of projects, conditional tags, conrefs, taxonomy, and workflow rules with no fidelity loss. Typical migrations run 4–12 weeks depending on volume and complexity.