Re: We need a specialized doc set- advice?

[Bonni Graham <bonnig -at- IX -dot- NETCOM -dot- COM>]

Jennifer Blair wrote:
>     Unfortunately, this is not as simple as writing smaller manuals
>     for each product and issuing and bundling them at the time of
>     sale. Because of the interdependence of the products, there needs
>     to be information on how the products will be used with other
>     products. For example, B could be sold with A-E, but it could
>     also be sold by itself, and the user might want to use it with
>     *any* of our other products, or with other companies' products.

Before I say this I want to say I AM NOT TRYING TO SELL ANYONE THIS
PRODUCT.  I just happen to be writing the documentation right now for a
product that can handle this situation with nifty customized documents.

What it does is create a document structure that can hold several text
pieces.  Each of these text pieces can be generic (applying, in this
situation, to just Product B, say) or specific (applying to the way
Product B interacts with Product C, and another applying to the combo
of B and A, etc.).  You can set up a database to detail the different
possible combinations of modules, then connect the text pieces using
the document structure and the database.

Each final document includes ONLY the information for the combination
specified when you assemble it.

If anyone would like further information, I'd be more than happy to
supply it or put you in touch with my client's company.  Just lemme
know.

--
Bonni Graham
Manual Labour
bonnig -at- ix -dot- netcom -dot- com