For about ten years, I’ve been maintaining the documentation suite for a set of niche market applications. The docs consistent of a set of user guides, quick start brochures, and help sets. A few years ago we made a decision to develop the online help using JavaHelp. I’ve recently been working to move the help to PDF using links from the application modules to named destinations in the PDF versions of the user guides. I am aware that an online user guide is not a help file. In fact, online guides are woefully unhelpful when it comes to resolve point-of-problem inquiries into an application’s knowledge base.
I’m attempting to justify a business decision that I know will compromise the usability of help files. The move to PDF-based help is driven by the costs of converting a FrameMaker-based documentation suite to JavaHelp, and the need to have the help sets ship with each release of the applications. Arguments about single-sourcing aside, the quickest way to generate the help sets will be to update the PDFs named destinations with the application’s help call map IDs. I’ve not convinced myself that I feel good about this decision.
I loved watching Michigan beat Florida today. I like Tebow, but Michigan has a better fight song. It was classic college football. A plethora of SEC wide-open passing and good ‘ol Big 10 ½ punch you in the mouth running. Saturday my Scarlet Knights look to make it two bowl victories in row. When’s the last time Dome fans could say that?