TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Our shop is planning (in the near future) on moving from .pdf guides, mostly user guides, to HTML user guides. In doing some research online, it appears that HTML guides are not all that different from online help systems as far as the chunking of information/topics. The only major difference I've noticed is that in help systems you have a TOC and in an HTML guide you have a list of links.
Some of our guides use information mapping (IM) procedures. In playing with the HTML output of guides with these IM tables, the information mapping tables are lengthy and look bad.
My sense is that as we move to HTML, in our documentation that uses the IM method is going to have to be changed.
Has anyone ever seen or heard pros/cons on using IM tables in HTML guides?
Does anyone know of any good resources/best practices for HTML guides?
Your feedback is appreciated.
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l