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:What to call an umbrella document? From:"Hart, Geoff" <Geoff-H -at- MTL -dot- FERIC -dot- CA> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 31 May 2001 09:50:50 -0400
Becca Price reports: <<We have a very elaborate product, which consists of a
number of components that can be installed in any number of configurations.
Because of this, we have a separate installation guide for each component.
Unfortunately, there really isn't any one place to put information that
relates to the product as a whole, or talk about interactions between
different components, installation order, and so forth. There actually exist
documents that (mostly) contain this high-level information - three of them,
with a whole lot of overlap. They are called "Getting Started Guides" -
which in itself causes confusion, because experienced installers don't look
at them, because the name implies something different (IMHO) from what they
are.>>
Sounds like you need a single document called "Product overview" or
"Planning your installation" to act as a sort of "guide to the guides". You
could also call it "before you begin", but the risk here is that nobody will
read it (just like nobody reads "read me first" files). Well, almost nobody.
<<I'd kinda like to get away from "getting started" because it also contains
upgrade information, but there is historical inertia behind keeping the
"Getting Started" title.>>
Inertia isn't a good reason to retain a title if (as you note) it doesn't
describe the actual contents. The solution might be to sell your manager on
a consistent approach, centered around the "product overview" (or whatever
you call it). After all, if you're going to redesign one thing, you might as
well make everything else fit!
--Geoff Hart, FERIC, Pointe-Claire, Quebec
geoff-h -at- mtl -dot- feric -dot- ca
"User's advocate" online monthly at
www.raycomm.com/techwhirl/usersadvocate.html
"The problem with defending the purity of the English language is that
English is about as pure as a cribhouse whore. We don't just borrow words;
on occasion, English has pursued other languages down alleyways to beat them
unconscious and rifle their pockets for new vocabulary."-- James D. Nicoll
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Information Mapping, Inc., a professional services firm
specializing in Knowledge Management and e-content solutions. See http://www.infomap.com or 800-463-6627 for more about our solutions.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.