Overview of the DITA Processing Pipeline in Ingeniux CMS | Describes how DITA content moves through authoring, normalization, synchronization, and other downstream processes.
The Darwin Information Typing Architecture (DITA) is not only a powerful open standard for writing, editing, and reviewing content. It also offers a high-level of versatility in how content can transform to meet the needs of your organization and its information consumers. Ingeniux CMS provides an end-to-end DITA solution for customers who exclusively author, manage, and publish DITA content and for customers who integrate DITA content with non-DITA document types.
The figure below provides a visual demonstration of how customers work in DITA and how the DITA processing pipeline works within Ingeniux CMS.
Ingeniux CMS provides DITA solutions for customers who already author and publish DITA and for those customers who first need to migrate their current content to DITA. If your content is in a non-DITA format and your organization plans to migrate to DITA, the Ingeniux Services team can help you with the transformation process. For customers who already author in DITA, you can upload your DITA content to the CMS Assets Manager.
Once uploaded to Assets Manager, your DITA topics, ditamaps, and associated files receive unique identifiers. These IDs help Ingeniux CMS to keep track of your DITA objects and their life cycles within the CMS, no matter if you rename your files or move them to different locations in the Assets Tree. Once in Assets Manager, the CMS help you manage version histories, access level permissions for users and groups, life-cycle workflows, translation projects, and other essential source management operations.
Ingeniux CMS integrates with the following XML editors for a seamless authoring experience:
Before DITA source enters the Ingeniux CMS publishing pipeline, map references, keys, content references, code references, etc. must resolve. CMS pages are created to contain the resolved DITA content.
The DITA Open Toolkit (DITA-OT) is an open-source publishing engine for content written in DITA. Ingeniux CMS incorporates the DITA-OT to preprocess DITA content on its way through the Ingeniux CMS publishing pipeline. This preprocessing step called normalization results in normalized DITA. The DITA-OT documentation provides a summary of how the normalization build transforms the source DITA to its intermediate form:
Writers execute the normalization build on the root DITA map of documentation sets from the Assets Manager. As long as the root DITA map and all child maps and topics are valid, DITA source can be normalized. Moreover, normalization is a repeatable process, so DITA source that is continually updated can be pushed forward at any point in authoring cycle.
Note: Keep in mind that the normalization build is a DITA-to-DITA transformation, which results in fully resolved and expanded XML. It is not the final presentation rendition.
When the incoming DITA source normalizes, Ingeniux CMS automatically creates new pages as needed to contain the new normalized content and also updates normalized content within existing pages (i.e., content that already underwent normalization and page creation during a previous build). After this page creation/sync process completes, the normalized DITA content resides in a dedicated field within pages in Site > Site Tree.
Once DITA content integrates into the Site Tree, content creators and CMS administrators can conduct any further downstream processes (e.g., taxonomy categorization, publishing to website, etc.) just as they would for any pages in Ingeniux CMS.