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.
I would agree that PDF is the immediate choice. I was on a
project documenting an API, and we decided to drop the
printed docs altogether. That allowed electronic
distribution, and made the product less expensive - a good
thing since we decided to offer the API for free. A few
points:
* Existing users COMPLAINED... Rightly so. It's not so
easy to use as paper.
* In spite of the complaints, I'm not aware of any
customers who printed the PDF versions. The only
people I know of who printed them were inhouse for the
company that makes the API, and they got the company to
foot the bill. We're talking about thousands of pages.
* HTML would be good, and in fact, for my personal use of
the API, I generated an HTML version of the docs, and I
access it through my development environment.
Not sure if this is particularly useful or interesting, but
there it is.
