Getting Feedback on your Technical Documentation
- Adobe RoboHelp Server has been around for years, but has recently undergone a major rewrite. RoboHelp Server requires a Java runtime environment (e.g. JRE or Apache Tomcat) and a database (e.g. Oracle or SQL Server) but the installation and setup is very easy. When I tried, it took me little more than 30 minutes See the Adobe RoboHelp Server System Requirements page for full details.
- Madcap Central is the newer kid on the block and offers similar functionality. Unlike Adobe's offering, Central doesn't rely on external software or databases. You just need a browser and an internet connection. Instead, it has partnered with Microsoft Azure to host your content. See the Madcap Central System Requirements page for full details.
- They only work with specific content. Adobe RoboHelp Server only works with Responsive HTML output. Madcap Central also has limitations with the Flare targets that can be published to Central, but also offers content not being authored in Flare to be hosted.
- The reports offered by both solutions are fairly basic. For example, they don't allow much in the way of customization or filtering.
- Statistics on their own provide only part of the story. It requires time and effort to analyze the results and action change. For example, repeated context sensitive help calls from a dialog could mean there's a need for a UI or copy change.