This content has been marked as final. Show 4 replies
Welcome to our community, Pippa
You should investigate using a merged approach. In this approach, you create one project that serves as a "Master", to which you add subordinate projects that may or may not be included in the output.
I think before we go further though, we need more information. For example, what is your output type?
Thank you Rick :)
The output will be compiled HTML. I have a fair bit of experience using Robohelp for this, but have thus far never had the need for merged projects, so I know pretty much nothing about them - how might they help in this scenario?
Well, here's the way it may work for a compiled .CHM setup. If you are using compiled .CHM files, I'm guessing your software is modular. Meaning that at the time it is installed, the user has options of choosing between the following modules:
Module 2 - 9
In this setup, you would create help that is generic that all modules would need. That one would be the Master. Then you would create separate projects for the remaining modules. You would then provide it all to the person that handles the installation program for your application. That person would then handle configuring the installer application so that only help for the actually installed modules is installed. If a module has been excluded, help is not installed for that module and doesn't appear and is not available to the user.
Hopefully that makes sense to you. If not, ping back and I or someone else will take a stab at another explanation.
My that was fast! Thanks so much.
Your approach sounds very logical, but they don't call me Miss Worse Case Scenario for nothing! I am certainly thinking (and hoping) in modular terms, but I have a nasty feeling that I might turn up and find that it's one monolithic application, with access rights handled in some other way.
In this instance, I'm guessing we could only install one help file, and so that file would have to contain everything... ?
I'm confusing myself again ;)