Preserve the source
DITA topics, maps, subject schemes, DITAVAL files, catalogs, and assets should remain clean and exportable.
Modern DITA architecture
What a modern DITA CCMS should look like.
The CCMS market has given many teams a familiar bargain: accept platform heaviness, hidden assumptions, and process drag in exchange for governance. ForgeDITA starts from the belief that governance and maintainability should reinforce each other.
A modern DITA CCMS should not make experienced practitioners feel like they are only moving changes through a machine. It should preserve content, clarify workflow, and make publishing behavior easier to explain over time.
That means native XML as the system of record, open APIs for integration, versioned toolchain bundles, explicit semantic interpretation, and release evidence that can survive audits without turning every update into a manual chase.
This is not a rejection of structure or regulation. Regulated teams need control. The problem is when control is implemented as scattered spreadsheets, unclear runtime state, and systems nobody is allowed to improve.
Practical take
What this means in real DITA operations.
Pin the runtime
A release should identify the exact baseline, toolchain bundle, publishing profile, and semantic model used to produce it.
Expose the seams
Repository, validation, graph, workflow, preview, publish, and baseline behavior should be available through open APIs.
Respect practitioners
The system should support responsible experts who need to improve templates, transforms, semantics, and workflows.
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