Latest posts by techwriter (see all)
- 15 Questions to Ask After You Finish a Technical Document Project - February 12, 2018
- THY’s Perfect Information Design - February 9, 2018
- Waterfall vs. Agile Models in Technical Documentation - February 7, 2018
© Ugur Akinci
Much lip-service is paid to the savings realized through conversion of legacy documents to DITA format. But in general the evidence is either sparse or anecdotal.
Even though these are numbers provided by one specific DITA vendor and probably cannot serve as a general guide to the exact number of hours per document saved during the conversion process, it is important to pay attention to the amount of PRE-CONVERSION work (the blue bar in the above chart) that needs to be done, whether one does it in-house or through an outside DITA vendor.
Stilo has kindly provided numbers for the monetary costs of such conversion as well:
Let’s remind that 1,000 characters is more or less one-page of documentation.
The above numbers can act as a rough guideline for technical documentation managers as to what kind of a budget one needs to have those old document silos converted into clean DATA by a qualified vendor like Stilo.