Glossary · 3 · Publishing SDKs and structured content
DITA Open Toolkit (DITA-OT)
Also known as: DITA-OT, DITA Open Toolkit
In technical communication, the DITA Open Toolkit (DITA-OT) is the open-source, vendor-independent publishing engine for content authored in the Darwin Information Typing Architecture (DITA); it processes DITA maps and topics through a pipeline of pre-processing and transformation steps into output formats such as HTML and PDF and can be extended with plug-ins.
- Publishing SDK
- DITA
- Technical documentation
In one sentence
The DITA Open Toolkit (DITA-OT) is the open-source publishing engine that turns DITA maps and topics into HTML, PDF and other outputs.
Example
A documentation team runs the dita command in its build pipeline to turn a DITA map into HTML5 and PDF, with a custom plug-in that applies the company's PDF layout.
How it applies
- Publishing SDKs: DITA-OT is the reference publishing SDK for DITA (Darwin Information Typing Architecture). The project describes it as a vendor-independent, open-source implementation of the DITA standard, released under the Apache License 2.0 and governed separately from OASIS, which owns the standard. It supports DITA 1.0 to 1.3 and, since release 3.0, Markdown input.
- Pipeline: A transformation starts with pre-processing: generating file lists, filtering, resolving DITA map references, DITA keys and content references (conref), and filtering conditional content with DITAVAL files (DITA conditional processing). Each step corresponds to an Ant target; the transformation step then produces the output format. The steps are implemented in Java or XSLT.
- Outputs: Built-in formats include HTML5 and other HTML-based outputs, PDF generated from XSL Formatting Objects through a formatter such as Apache FOP or a commercial one, and Markdown.
- Plug-ins: Output formats, styling and processing changes are added as plug-ins, installed with the dita install subcommand; a plug-in registry lists published plug-ins. Customizing through plug-ins rather than editing the toolkit keeps updates possible.
- Platform and developer SDKs: Component content management systems and authoring tools embed DITA-OT or call it as their publishing back end; continuous integration (CI) runs it in docs-as-code setups.
- Documentation: Record the DITA-OT version, the plug-ins and their versions and the DITAVAL files used for each deliverable, so a published output can be rebuilt from its source.
DITA-OT vs. the DITA standard
The DITA specification (OASIS) defines the markup, its grammar files and the processing rules. DITA-OT is one implementation of that processing. Output produced by DITA-OT reflects the toolkit's version and plug-ins; another processor may produce different output from the same valid source.
Keep in mind
DITA-OT is a software product with regular releases; supported DITA versions, output formats, build tools and command options change. Check the documentation of the release in use. Facts here are as of October 11, 2026.
External references
- DITA Open Toolkit: Project site
- DITA Open Toolkit documentation: Pre-processing modules
- DITA Open Toolkit documentation: Installing plug-ins