They must work with software engineers and build masters to integrate online help into applications and then test for context-sensitivity. Depending on the volume of content, this can take from several days to many weeks of work. Next they must typically publish to an intranet or web site. This means segmenting and reformatting content for web-based viewing, and then working with the Webmaster and testing everything all over again. This can also take several days to several weeks.
Months can elapse.
As a result, yet more time and effort must be expended to make Errata's that cover the changes to the software and the errors in the documentation and the online help. With the introduction of two new server-side products, WebWorks ProjectLink and WebWorks AutoMap, the entire publication cycle has been redefined. The power of WebWorks Publisher has been extended with the creation of two enterprise-oriented products that can automatically convert either WebWorks Publisher projects or FrameMaker files. WebWorks ProjectLink and AutoMap streamline this traditional ePublishing process across the enterprise by providing much more flexibility and control with far less human intervention required. WebWorks AutoMap automatically applies a WebWorks template to FrameMaker files and generates online output.