Structured docs without the DITA.
A component content management system (CCMS) for people who'd rather write than wrangle XML. Write what readers see, reuse anything, translate with AI, publish PDF and HTML. Live in a week.
The studio today: a task from a machinery manual, its safety notice reused from a fragment, one step changed since version 12.
Everything a CCMS should do. Nothing to learn first.
Write what the reader sees.
No XML view. No form per element. A step is a step, a warning is a warning, and the element name waits in the margin for the day you want it.
Live in a week.
Sign up, invite the team, write. No implementation partner. No schema project. No course to pass before you can type.
Reuse without the report.
Write a warning once, use it in every model. Where it's used sits beside the text, and a change tells you what it touches before you save.
PDF and HTML from one source.
Set layouts and themes in the studio with a live preview. What the author sees is what the reader gets.
AI that's part of the studio, not a line on the invoice.
Included for every author. Your workspace opts in, picks the provider and region or brings its own key, and nothing you write trains anyone's model.
Draft and tighten.
A first draft of a procedure. A shorter warning. A plainer sentence. The assistant writes inside your structure, so a step stays a step.
Spot what you already wrote.
Type a paragraph that lives in another manual and the studio offers the original. Reuse while you write, not in a clean-up next year.
Pre-translate, then review.
A new language starts translated. Review it in the studio, or send the XLIFF to your vendor with your own past translations already matched.
Answers for readers, from your content.
Readers ask, and get an answer with the page it came from, limited to what they may see. Plug your manuals into your own tools over MCP.
What a DITA toolchain costs you. What Contentry doesn't.
DITA is a fine standard and a hard product. Here's what changes when the structure lives in the editor, not in a specialisation.
Side by side with Paligo, Heretto and Tridion Docs.
From each vendor's public documentation, October 2026. Spot a mistake? Tell us and we'll fix it.
- Included
- Partial, extra or beta
- Not offered
In more detail: Contentry vs DITA · Contentry vs Paligo · What is a CCMS?
For teams who'd rather write manuals than run a CCMS.
Write in the finished page, not a form. Structure stays visible. The assistant drafts the dull parts.
Who holds what, what changed, what shipped. No spreadsheet. One price per author, no modules later.
A new product line, a new manual, a team that's never had a CCMS. Start structured on page one. Reuse from day one.
Safety notices to ANSI Z535 and ISO 3864. Reused across every model, translated once, kept per release.
Help us build the CCMS you'd actually choose.
A small first cohort. The studio and the assistant early, a founding price for good, and the people building it on the phone.
Questions first? Read the FAQ.