I am working on a new project where the product documentation is in a Confluence wiki. There is now a requirement to export that documentation to HTML so that it can be bundled and installed with the product and accessed directly (and locally) from the GUI application. I’ve read through the forums and seen where people have done similar things, but I’m wondering if I could get a consolidated set of advice / best practices here.
I think we have the following requirements. The solution must:
- Provide both graphical and programmatic access so that either a user can manually do the export or an automated process can programmatically start the HTML export.
- Provide the ability to select a subset of content for export from entire space.
- Enable visual customization of the HTML output with company / product branding.
- Ideally, provide a collapsible TOC (e.g., left-pane tree nav).
- Ideally, include a Search capability over the HTML content.
Note, I’ve experimented with the Confluence HTML export, which I think could work for our needs with some custom CSS / development. However, I also see some add-ons and plug-ins (e.g., Custom Exporter and/or Auto-exporter for Confluence) that look promising. Any inputs on use of these or other tools would be appreciated. We are a small team, so we’ll need to weigh the costs/benefits of internal development and support vs. an off-the-shelf solution.
Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.