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.
Subject:QUESTION: Using Information Modules From:Joe Miller <joemiller -at- CANBERRA -dot- COM> Date:Thu, 23 Oct 1997 11:54:09 -0500
Mike Dannenberg wrote:
>I think modularising docs recycling stuff are simply necessary
>to cope with the ever increasing amount of information we have
>to handle. When done badly the result is bad, when done well,
>the result is good.
Amen. Or to put it less succinctly, he's absolutely right on both counts:
any tool can be used well or ill, and we've got to find new ways of
keeping the information accessible, so modularising is here to stay.
We're starting to use modules because we're responsible for about
160 spec sheets and an equal number of user manuals which often
reuse common parts. It's not yet an automatic process, so we're
doing it manually where necessary.
Do any of you have stories about how you stopped worrying and
learned to love "information modules"?
