How should I construct and deliver documentation for an IT tool on Windows? There's an additional constraint that I don't want to spend money on help authoring tools.
Here on SO, we talk about algorithms and optimizations, APIs and performance. But one of the deliverables from my dev efforts is documentation. What's the best way to build it, and in what form should I deliver it?
If I am delivering a set of .NET APIs, a .CHM is a reasonable mechanism for delivery. It's very easy to use SHFB to construct the help file as part of the build, and if it will be used mostly on Windows, a .CHM is very accessible. And converting the .CHM to .HTM makes the doc accessible even more broadly.
But I want to deliver doc for a ISAPI Filter which will be used not by developers per se, but by Windows web server administrators. I need to describe installation, operations, and configuration. I think the end users might often have developer as well as administrative skills, but in any case, for my purposes the documentation will cover administrative tasks and operational matters.
I know that SHFB allows me to include regular HTML files in the .CHM. If I already know SHFB, and if I don't want to spend money on a help-authoring tool, is this the best way to go? If not, what?