The information that a company distributes is never in a vacuum. Instead, it affects the content of many internal and external processes and, therefore, the content of user documentation in particular. If, for example, developers adjust the functionality of a software package, the interface also changes. Both of these aspects must also be replicated in the product documentation. So why not “simply” connect the two together, for example by coupling the CMS to the development process and using it as an analysis tool for content quality as well? Continue reading
Technical documentation without up-to-date product data is no good whatsoever. Incorrect technical data, dimensions, serial numbers and terminology: not only are all these confusing for the reader, they can also have legal consequences. Naturally, conscientious technical writers can be employed to keep information in ST4 constantly up to date, which may be feasible for a certain amount of data. But what else can be done with large quantities of product data that are constantly changing?