All your responses have been terrific. I'm compiling a mini reference guide for myself to follow as a I restructure the install guide that all my questions relate to.
 
When I first single-sourced the guide, I set it up as follows:
vendor_guide.book
TitlePage.fm (imported vendor-specific variables from a variables file into the guide)
vendor_guideTOC.fm
folderA
folderB
.
.
.
folderG
vendor_guideIX.fm
As I've been reading your suggestions, the following question occurred to me:
Does it make more sense to use the same TOC, LOT, and same IX file in each vendor book file?
The new structure, based on this change and others resulting from your suggestions, would look something like this:
VendorFolder
vendor-specific_variables.fm
vendor_guide.book
vendor-specific_fileA.fm
.
.
.
vendor-specific_fileZ.fm
SharedFolder
TitlePage.fm
TOC.fm
LOT.fm
sharedfileA 
sharedfileB
.
.
.
sharedfileZ
IX.fm
GraphicsFolder
All graphics
If I follow this approach with the TOC, LOT, and IX, when I open a vendor-specific book file and import the vendor-specific variables file with its conditional text settings, the TOC, LOT, and Index should reflect the vendor-specific conditions, right?
 
If this makes sense, and works technically, it minimizes the number of files generated for each guide.
 
All thoughts welcome, as always.
 
Carol
 
_______________________________________________

Are you a Help Authoring Trainer or Consultant? Let clients find you at 
www.HAT.Matrix.com, the searchable HAT database based on Char James-Tanny's HAT 
Comparison Matrix. Contact [EMAIL PROTECTED] for details.


Interested in Interactive 3D Documentation? Get the scoop at 
http://www.doc-u-motion.com Your 3D Documentation Community.
_______________________________________________

Technical Communication Professionals

To post a message to the list, send an email to [email protected]

To find out more about the list, including archives and your account options, 
visit http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com

If you need assistance with the list, write to [EMAIL PROTECTED]

Reply via email to