ForgeDITA Blog

Notes for DITA teams tired of operational compromise.

Practical writing on DITA, CCMS architecture, Oxygen-first workflows, native XML, reproducible publishing, and the human cost of systems that become harder to operate every year.

ForgeDITA forge-inspired logo concept
01

What a Modern DITA CCMS Should Look Like

The architecture ForgeDITA believes structured content teams deserve.

02

What DITA Support Should Mean

Because vague compliance slogans are not a product contract.

03

Oxygen Users Deserve Better

Oxygen should be a first-class client, not collateral damage.

The theme

Structured content should not require constant surrender.

The blog explores a simple premise: DITA can still be powerful, open, and maintainable if the platform respects standards, practitioners, and operational reality.

Follow the build

Want the practical version?

ForgeDITA is being shaped around real DITA pain: process drag, publishing uncertainty, export anxiety, specialization complexity, and the need for systems that practitioners can trust.

Talk to ForgeDITA