What do you like best?
Our challenge was that we needed to share the help documentation for our software product via a compiled help viewer, our website, on a mobile phone friendly view and as a single html page. Before HelpNDoc, we were using Word as the source and then modifying it for each different target. That was not efficient and led to possible errors and inconsistencies. HelpNDoc offered the additional benefit of being able to embed videos from our youtube channel with ease and sharing it among all the different views.
We ran into a couple of technical issues and their technical support was courteous, fast and helpful.
What do you dislike?
Outside of using the templates that ship with the product, we did have to remember some of our Pascal days in order to modify the one page html view to add our own table of contents. Also, there is no easy way to make the html output WordPress compatible, so we had to get creative there as well.
Recommendations to others considering the product
Start with the shipping build templates, generate the help documentation using that and then switch to tweaking the templates if you need to.
We found that we could have professional looking documentation that met most of our needs, released with that and then had more time to make the tweaks we needed and publish the updates.
What business problems are you solving with the product? What benefits have you realized?
Having a single source for different views is a time/money saver. It improves the quality of our help documentation.
Our documentation looks professional and reflects all the time that we have invested in producing a high quality product.