similar, yet different

[Lisa Bronson <lisa -dot- infocus -at- gmail -dot- com>]

I'm documenting a machine with two modules that are almost identical.
Some customers will order a machine with only one module; others will
get both so their production will be doubled; some will start with
one, then add the second later.

Under normal circumstances, I would prefer to document both modules,
but given time contraints, my plan at this point is to document the
base module and *only the differences* between it and the second
module. And maybe that's the better way to do it, anyway?

Has anyone ever written about something like this? How did you handle
it? Did you receive any feedback from your users as to whether it was
not enough (if you did it like I'm planning) or too much (if you fully
documented both sides)?

Thanks,
Lisa B.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl

WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l 

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.