Operational drag
Small content changes should not trigger days of manual routing, duplicate tracking, and process archaeology.
DITA-native. Oxygen-first. Built for maintainability.
DITA infrastructure for teams tired of constant compromise.
Many DITA teams spend minutes changing content and hours routing, tracking, rebuilding, and explaining it. ForgeDITA is a standards-first CCMS for teams that want native XML, predictable publishing, and systems that remain understandable as complexity grows.
Development status
ForgeDITA has reached MVP.
ForgeDITA has now reached MVP after an extended architecture-first development phase focused on operational maintainability, reproducible publishing, explicit semantics, and standards-first structured content infrastructure.
The project remains intentionally focused on native XML preservation, Oxygen-first workflows, immutable publishing toolchains, graph-aware architecture, open APIs, and long-term operational clarity.
The goal is not simply to modernize enterprise documentation systems. The goal is to build documentation infrastructure that remains understandable, portable, reproducible, and operationally trustworthy as complexity grows over time.
There is still substantial work ahead, but reaching MVP represents an important milestone in validating these architectural and operational ideas in practice.
The pain is real
Structured content was supposed to make work safer, not more exhausting.
For many teams, the content change is the easy part. The hard part is the maze around it: approval cycles, translation handoffs, tracking spreadsheets, brittle publishing environments, and tools that no longer feel open to improvement.
Customization debt
Specializations, transforms, templates, and workflow rules should be explicit and versioned, not tribal knowledge hidden in the platform.
Publishing uncertainty
Teams should know exactly which content, baseline, toolchain, and profile produced a release.
Loss of agency
Experienced DITA practitioners should be able to shape the system responsibly instead of working around it forever.
The ForgeDITA position
A CCMS should reduce long-term friction, not institutionalize it.
ForgeDITA treats native DITA/XML, semantic understanding, validation, publishing, workflow, and APIs as infrastructure. The goal is not less governance. The goal is governance that remains clear, reproducible, and maintainable.
The promise
Standards-compliant content infrastructure built for long-term maintainability.
Native XML
Your DITA stays DITA. No proprietary document model. No hidden lock-in.
Bring Your Own Editor
Oxygen-first workflows without forcing writers into a vendor-hosted authoring experience.
Reproducible publishing
Pin content, baselines, toolchains, and publishing profiles for releases that can be explained and rebuilt.
Open APIs
Repository, validation, graph, preview, publish, baseline, workflow, and integration surfaces by design.
ForgeDITA vs legacy CCMS drift
Built for teams that are tired of trading standards for survival.
What teams need
Common CCMS pain
ForgeDITA direction
Native DITA control
Content shaped by product assumptions and export anxiety
Native XML remains the system of record
Workflow clarity
Approvals and tracking spread across disconnected tools
Workflow evidence, release gates, and audit events treated as first-class platform data
Publishing confidence
Mutable installs, fragile transforms, and unclear release provenance
Immutable, tenant-scoped toolchain bundles and pinned baselines
Specialization maturity
Custom DITA semantics implemented as hidden exceptions
Semantic registry model for explicit, versioned interpretation
01
Standards-first
Public, bounded conformance claims instead of broad compliance slogans.
02
Practitioner-aware
Designed around real DITA work: reuse, validation, publishing, baselines, review evidence, and translation handoffs.
03
Maintainable by design
Architecture that makes system behavior inspectable instead of forcing teams to memorize workarounds.
Alternatives hub
Evaluating a CCMS after years of compromise?
These pages compare ForgeDITA's direction against the operating friction teams often experience when structured content platforms become too heavy, too opaque, or too hard to evolve.
AEM Guides Alternative
For teams that want enterprise DITA power without absorbing a broader platform maze.
Vasont Inspire Alternative
For teams that need control, portability, and fewer operational unknowns.
Heretto Alternative
For teams that want structured content without surrendering native DITA control.
Paligo Alternative
For teams that need deeper DITA operations than simplified authoring models can provide.
MadCap Central Alternative
For teams moving beyond project hosting toward standards-first CCMS infrastructure.
Read the ForgeDITA Blog
Practical thinking on DITA, operational maintainability, Oxygen workflows, and honest conformance.
From the blog
Notes for people who still believe structured content can be done well.
Read the first articles on modern DITA architecture, honest conformance claims, Oxygen-first workflows, and why native XML still matters.
Early access
Help shape a DITA CCMS that stays maintainable.
ForgeDITA has reached MVP. We are looking for practical teams, consultants, regulated content groups, and Oxygen power users who know where current systems hurt.
Request beta access