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've never paid for the course, but from what I've heard about it, doesn't this roughly equate to Information Mapping?
Bemused,
Rebecca Stevenson
Technical Writer
-----Original Message-----
>From: Dan Goldstein <DGoldstein -at- riverainmedical -dot- com>
>Sent: Jun 8, 2006 8:43 AM
>To: TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
>Subject: RE: Modularization of Documentation
>
>Hi Tony,
>
>Thanks for your response. So you're saying that in_the_whole_world,
>there's not a single book about documentation that requires the
>following:
>
>* Each section ("module," whatever) of documentation should describe a
>specific task and be clearly labeled as such.
>* Each section of printed documentation should be no more than one page
>long. (What about onscreen Help? Varying page sizes?)
>* Each section of documentation should have no more than five other
>sections that either reference it or are referenced by it.
>
>While I don't personally agree with all three requirements, I'll bet
>*someone* has written a book that requires them.
>
>If not, write it!
>
>Thanks,
>
>Dan
Rebecca
I'll rain horrible fiery death on you later. - Pearl "the Lawgiver" Forester
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
