DITA (pronounced dit-uh) is an acronym for:
- Darwin—DITA can evolve to account for your particular authoring needs. (Specialization in DITA jargon.)
- Information Typing—DITA was designed for core types of technical content: concept, task, and reference.
- Architecture—DITA provides a framework for designing and delivering technical content efficiently.
Who owns DITA?
Nobody. DITA is an OASIS/XML standard for topic-based authoring of well structured content. Out of the box, DITA provides you with a structure amenable to most technical information. And it provides you with a mechanism for extending the structure if needed.
Why is DITA so widely adopted?
After all, there are other XML standards for technical documents. But, DITA is clearly the leader in standards and numbers of clients, and a whole ecosystem of support for DITA implementations.
DITA is powerful. And it’s rapidly gaining traction for product documents. Here’s why and how.
- DITA stores content as modular chunks called topics.
- A DITA Map organizes topics for publication in a logical order and hierarchy. (A DITA Map resembles a table of contents.) You can define DITA maps for outputs such as online help, user guides, system description and FAQ.
- A single topic can be included multiple times in a single DITA map or in multiple DITA maps, and will appear in as many output products.
- DITA is built for reuse and single sourcing.
- DITA is built for efficient product document authoring, update and publishing.