This will be largely dependent upon how you deploy your help. Does each customer install your help on their own machines? If so, that will be much simpler to achieve than if all customers access the same set of help files from perhaps your company's web site.
How does the help get deployed?
Thanks for your quick reply.
Ours is a web application and is distributed as OVF (Open Virtualization Format) or RPM. It is deployed as virtual appliance in customer environment. WebHelp (All content) is bundled in these packages.
We deliver OVF 'X' to different customers at the same time. The features in OVF 'X' are restricted by license and same is expected for help content. Same is the case with RPM.
It will be great if we can reach to solution by 19th as this is a bit urgent requirement.
Thanks in advance for all your help.
I'm hopeful that others will chime in with their own suggestions.
To start with, I'm kind of a geeky sort of guy and I understand many computer related things on a level the average person might not. But you have totally lost me with the talk of OVF and RPM and virtual appliances.
Sooo, until others chime in with their own suggestions I'll just toss out a situation I experienced personally and see how it may be received.
Years ago I was a Technical Writer at a small company that sold software in different combinations of modules. These were locally installed for each customer. And I was considering restricting access to the help based on modules installed. And upon chatting with my boss (one of the owners of the small company) he wrinkled up his nose and said he didn't like that approach.
I want every customer to have the full help system available.
When I asked about a hypothetical situation where the customer has the help for modules that aren't installed, I was shocked and slightly pleased by his sly reply.
He said: You know, if a customer sees the help talking about what a module they don't have is capable of, they just might be enticed to contact us and purchase additional modules.
In other words, the customer can't perform the functions anyway because they don't have the proper part of the application, but the help could be used as a sales tool.
Firing up Google reveals that OVF packages install on virtual machines - so that sounds like VM's on workstations & LAN servers (maybe) - so it still sounds like creating different flavs of WebHelp to go into different builds would suit the OP.
Rick, we have followed the same approach so far as your 'boss' stated.
Now, the scenario has changed.
Thanks for your detailed explanation.