>With the availabilty of the The DocBook Project and the DITA Open Toolkit, there should be no reason that end user documentation is still maintained in HTML files that have to be manually edited. Having it in HTML, just limits the possibile output formats the documentation could be presented. By moving to either DocBook or DITA formats, the documentation is immediately available in multiple potential formats.
The above wiki entries, describe ways in which the end user documentation can be put into either format and then rendered as HTML. One of the concerns that have been expressed by end users of eclipse, is the lack of documentation or current documentation. The problem with maintaining the HTML, is making sure you update the toc.xml files correctly. By moving to DocBook and DITA, these files are updated automatically when the appropriate build scripts are run.
Treate the documentation generation as one would treate code generation or plugins, and the end user documentation can be rebuilt during a normal build process, and kept more current. Maintenance becomes easier, as only the appropriate docbook or dita file needs to be updated, by the programmer responsible.