DITA
Structure your content. Scale your documentation. Deliver everywhere.
Darwin Information Typing Architecture (DITA) is an open standard for structured content and topic-based authoring, helping teams create, reuse, and publish technical documentation.
Write Once, Publish Everywhere
The DITA language lets you structure content in topic-based modules. DITA-compatible publishing tools can then generate HTML, PDF, mobile, print, and other formats from that same set of source files.
Built for Scale
From startups to Fortune 500 companies, the DITA language specification provides the foundation for handling complex documentation projects with thousands of topics, multiple products, and global translation requirements.
Reuse Everything
DITA’s structured markup gives you several ways to write content once and reuse it elsewhere. Use topic-based authoring to create modular content, content references to pull in shared information, and conditional text to show different content to different audiences—all from the same source files.
For Technical Writers
Professional documentation language that adapts to your workflow
Transform your content creation process with DITA’s topic-based authoring syntax. Focus on writing while DITA-compatible tools handle the structure, cross-references, and publishing automation.
- Topic-based writing language that mirrors how users actually consume information
- Built-in syntax for cross-references and linking
- Content reuse markup that eliminates copy-paste errors
- Semantic structure that enables professional publishing
For Product Teams
Documentation language that scales with your product
Keep your docs in sync with rapid product development. DITA’s modular markup approach means updates in one place propagate everywhere they’re needed when processed by DITA tools.
- Single-source content markup for multiple products and releases
- Conditional publishing syntax for different audiences
- Language designed for integration with development workflows
- Structured approach that ensures consistency across all documentation
For Enterprise
A content language for large-scale documentation programs
For organizations managing documentation across many products and teams, the DITA language specification offers a governance model, workflow foundation, and scalability suited to that scope.
- Standards-based markup language backed by OASIS
- Language designed for enterprise-grade content management workflows
- Built-in translation and localization support
- Extensible language architecture for custom requirements
Why Structure Content
As documentation grows across products, teams, and languages, keeping it consistent and current takes real, ongoing effort. DITA offers one way to manage that complexity: it treats content as structured data rather than free-form text, which supports content reuse, automated publishing workflows, and content that can adapt as your needs change.
A key part of that structure is topic-based authoring: content is organized into self-contained topics that each focus on a single subject, such as a concept, task, or reference, rather than one continuous document. Because a topic doesn’t depend on the narrative around it, it can be reused, reordered, and assembled into different documents and outputs, which is what makes DITA’s content reuse and multi-format publishing possible.
Is DITA a Good Fit?
DITA’s value comes from specific features: semantic markup, content reuse, conditional filtering, specialization, and topic-based authoring. None of that comes from the XML syntax itself, and whether those features are worth adopting depends on the shape of your content. In some situations, they get used constantly. In others, they’d mostly sit unused, and a different tool might do the job just as well or better—not just a lighter markup language like Markdown or AsciiDoc, but also non-markup tools such as Microsoft Word or Adobe FrameMaker.
| DITA’s features get used | DITA’s features go unused |
|---|---|
| The same content appears in multiple topics or products | Content is used in exactly one place |
| Several product variants share most of their content | There’s only one product or variant |
| One source publishes to multiple output formats | Only one output format is ever needed |
| Content needs audience- or platform-based filtering | All readers see the same content |
| Content is translated into many languages | Content is rarely or never translated |
| Content naturally splits into self-contained topics | Content only works as one continuous narrative |
| Multiple authors need enforced structure | Content has a single author |
| Content is long-lived and maintained for years | Content is one-off or short-lived |
| The team can invest in tooling and a publishing pipeline | The team needs to ship quickly with minimal setup |
Language Features
Content Reuse DITA’s content reference syntax lets you reference content fragments across topics and publications, so an update in one place is reflected wherever that content is used.
Conditional Publishing Built-in markup for creating different versions for different audiences from the same source. Filter by product, platform, experience level, or any criteria you define in the language.
Multiple Output Formats DITA’s semantic structure supports generating HTML, PDF, EPUB, mobile apps, and more through compatible publishing tools.
Extensibility Adapt DITA to your specific needs through specialization. Create custom topic types, add industry-specific elements, or extend the language while maintaining compatibility.
Translation Support Built-in language features for localization workflows. DITA’s structure supports translation memory, multilingual content management, and consistency across languages.
Open Standard DITA is maintained by OASIS as an open, vendor-neutral standard, so your content isn’t tied to a single vendor’s tools.
Learn More
- Take a tour of DITA’s topics, elements, and reuse mechanisms.
- See how DITA compares to HTML5, Markdown, AsciiDoc, reStructuredText, and DocBook.
- Read the history of DITA, from IBM to OASIS standard.
- Browse the specifications for the full language reference.