Native content
DITA XML and binary assets remain authoritative repository objects with clean export.
Architecture
Documentation infrastructure with explicit seams.
How ForgeDITA connects native XML, contextual DITA semantics, immutable toolchains, open authoring APIs, and attributable publishing.
ForgeDITA separates content, semantics, relationships, validation, workflow, and publishing into inspectable contracts. The goal is not to distribute complexity for its own sake. The goal is to prevent one mutable platform layer from becoming the undocumented source of truth for everything else.
Semantic registry
Cross-service meaning is declared and versioned instead of hardcoded independently.
Graph and resolution
Keys, conrefs, maps, subject schemes, and impact are evaluated in named contexts.
Toolchain registry
Tenant publishing environments are versioned, promoted, retained, and attributable.
Open authoring contract
Oxygen and other clients use server-authoritative APIs for content operations.
Release evidence
Baselines, profiles, toolchains, manifests, and artifacts remain connected.
Inspect the architecture
The public repository contains the reference architecture, editor authoring contract, graph and semantic-registry models, security architecture, and illustrative manifests.
Open the public repositoryBeta evaluation
Bring us a difficult DITA problem.
ForgeDITA is in active beta with teams and practitioners who care about native XML, reproducible publishing, explicit semantics, and maintainable operations.
Request beta access