In this article we will discuss Multiple versions of a content item, Comparing versions and Translation.
DITA: Multiple versions, comparing versions and translation
The Content Management System manages content on the basis of the data templates. A data structure was defined for Neopost that contains all the compulsory DITA components, plus extra data that could of importance to Neopost. Some of this data concerns the many different dimensions of these topics, such as brands, products, product revisions, countries, languages, versions and audiences. With the help of Sitecore software we can quickly and easily define content structures, and immediately implement them.
Reusing DITA content
The use of a generic content management system also offers huge benefits in terms of re-using the content. The content can be used in different places by linking or embedding it. All content is stored in a database. And unlike with a file oriented solution, the links can be managed. Links are objects, that are stored separately. If an item (topic, task, or part of it) is moved, the link will continue to work. The system gives insight in the relations between content items. The topic directly shows which map (s) is or are being used. Task steps, notes, etc. can simply be re-used, without requiring dummy topics to be made.
Automatically translating DITA content with Lionbridge
The CMS supports multiple languages and versions per content item. This also applies to images, as they are also content items. It is possible to determine which users can view, process or delete a content item; this is also possible per field. Content items can be processed as part of a workflow/process. This means that a single content item could find itself in different phases. The actions performed on a content item are determined depending on the status/phase. This allows for support to multiple editors, and enables process of translating the content to occur smoothly.
Via the system a set of content items is offered for translation. The content items are gathered in a so-called “translation project”. A complete map, part, chapter or individual tasks (steps) can be compiled in a single translation project. The desired language/languages into which the content items must be translated are subsequently chosen. With the click of a button the content items are compiled, converted to XLIFF and sent a translation partner. Neopost uses Lionbridge’s Freeway portal. This process occurs without requiring further manual actions because we make use of the web services of Lionbridge’s Freeway portal.
If the content items need to be translated they should not be changed in the system. For this reason content items are given a status, which means they cannot be further processed. Once a set of content items has been translated it can imported into the correct language/version. The status of the content item is also changed, allowing the item to be further altered again. While a particular of set content items is being translated, users can continue to work on other content items in a map.
In part three of this article we'll look into publication and transformation within the DITA solution.