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.
As much as I am enjoying this s/he tirade... (Even though
I am not sure why it comes up in user documentation - we
don't write in the third person any more, do we?)
I am currently exploring futures for our documentation
suite. We have several thousand pages which are constantly
and selectively affected by the introduction of new
development "features" to the product. Our customers don't
shop on a per "feature" package. Instead they, procure sets
of features. Some features will always be purchased together.
We need the ability to provide any feature permutation.
The problem: how will we selectively compile their
documentation to match their feature sets? how can
we set up feature databases with user-oriented info
(not functional specification) that serves both
product information and training needs?
Is anybody out there currently working on this problem?
Do you (does he/she/them) care to discuss your (his/hers/
their) solution in this forum? Moving forward is part of
the solution but retrofitting it to existing pages is
another...
