We use
- Serna XML Editor
- Eclipse (plain xml editing, mostly used by the technical people)
- own specific Eclipse plug-in (just for our release-notes)
- Maven docbkx plug-in
- Maven jar with specific corporate style sheet, based on the standard docbook style-sheets
- Maven plug-in for converting csv to DocBook table
- Maven plug-in for extracting BugZilla data and creating a DocBook section from it
- Hudson (to generate the PDF document(s))
- Nexus to deploy the created PDF documents
Some ideas we have:
Deploy with each product version not only the PDF, but also the original complete DocBook document (as we partly write the document and partly generate them). Saving the full DocBook document makes them independent for changes in the system setup in the future. Meaning, if the system changes, from which the content was extracted (or replaced by diff. systems) we would not be able to generate the exact content any more. Which could cause an issue, if we needed to re-release (with different style-sheet) the whole product ranche of manuals. Same as with the jars; these compiled Java classes are also placed in Nexus (you do not want to store them in your SCM); this we would also do with the generated DocBook document.
Update:
Fresh created a Maven HTML Cleaner Plug-in, which makes it possible to add DocBook content to a Maven Project Site (Beta version available). Feedback is welcome through the Open Discussion Forum.
