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.
Our department has planned to release a *light* version of our current software
application. This light version will have limited functionality, but against
payment, the customer can ask for more functionality and even request for all
the functionality the original application has. My problem now is that I do not
know beforehand which functionality will be delivered in every particular light
version. Has anyone ideas of how to deal with that in the documentation.
My first thought was to describe all functionality in a manual and supply the
individual customers with a list of the functionality in their version. Does
anyone have other ideas?
