Authoring stays professional
Use Oxygen for the work it already does well: editing, validation, specialization support, and authoring assistance.
Oxygen-first
Oxygen users deserve better CCMS workflows.
Oxygen is already a mature authoring environment for serious XML and DITA work. A CCMS should not force experienced writers to give that up just to get repository control, workflow evidence, and publishing governance.
Many teams already know how they want to author. The pain begins when the CCMS treats the editor as a problem to replace instead of a professional tool to support.
ForgeDITA treats Oxygen as a first-class client over open APIs. The CCMS owns repository state, locks, validation, graph context, workflow evidence, baselines, and publishing jobs. The editor remains an editor.
That matters because good DITA work still requires skill. Structure can reduce chaos, but it does not remove judgment. The platform should protect that expertise, not flatten it.
Practical take
What this means in real DITA operations.
The CCMS remains authoritative
Repository state, locks, workflow, releases, and publishing jobs live in the platform, not in local editor assumptions.
Semantics are shared
Editor behavior should come from toolchain assets and semantic declarations, not Oxygen-only private logic.
Other editors can follow
Oxygen can receive first-class treatment without becoming the only supported path.
Early access
Building the cleaner path.
ForgeDITA is moving toward MVP for teams that want native XML, Oxygen-first workflows, reproducible publishing, and fewer systems that punish the people who understand them best.
Talk to ForgeDITA