Contentry vs DITA: structured docs without the toolchain
DITA is a fine standard and a hard product. This page says what it gets right, what it costs, where Contentry differs, and when you should pick DITA anyway.
What DITA gets right
Topic-based writing, where a task, a concept and a reference are different things with different shapes. Reuse by reference, so a warning written once appears in every manual that needs it. Conditions, so one source produces the manual for each model. A standard owned by nobody in particular, with twenty years of tooling behind it.
Every serious CCMS, Contentry included, borrows those ideas. The disagreement is about where the structure should live.
What it costs a team
In a DITA toolchain the structure lives in the tooling, and every writer pays the entry fee. The usual bill:
- An XML editor that shows tags, or a form for every element, and a training course before anyone can type.
- A specialisation: the schema someone adapted years ago, which nobody now dares to change.
- PDF through DITA-OT and XSL-FO, a stylesheet that was commissioned once and is edited by nobody.
- A translation round trip that loses inline tags, and a vendor who charges to put them back.
- An implementation partner for the first six months, and a contractor for every change after.
What Contentry does instead
The structure is in the editor. You write what the reader sees: a heading is a heading, a step is a step, a warning is a warning, and the element name sits in the margin for the day you want it. Nothing is typed as a tag.
Reuse is a thing you do while writing. The where-used list sits beside the text, and a change tells you what it touches before you save. Conditions are set on the content and previewed with a view-as switch, not compiled with a filter file.
Page layout is set in the studio with a live preview, for PDF and HTML from the same source. Translation goes out as XLIFF 2.1 with the inline tags intact and comes back the same way, with the assistant pre-translating and your own past translations matched.
Versions are kept and releases are pinned, so when someone asks what shipped in which language, the answer is on screen.
When DITA is still the right answer
If a customer contract requires DITA or S1000D deliverables, you need a DITA toolchain, full stop. If you have a large corpus already in DITA with pipelines that work and a team that knows them, the cost of moving may exceed the cost of staying. If you exchange topics with partners who only take DITA, the standard is the point.
Contentry does not import DITA today, and the first cohort starts fresh or brings content by hand. Say so on the call if that is a blocker.
What to do next
Join the waitlist and bring a manual to the call. Thirty minutes with a real chapter says more than any comparison page, this one included.