I have a RoboHelp 9 project that documents the installation and configuration of a software package that can include add-in components. Currently, the core instructions and add-in instructions are all in one RoboHelp project, with condition tags to include or exclude steps for the add-in components. The add-in steps are in the middle of the software setup. That is, the user cannot install the core software, then the add-in components.
I have a new requirement to split the instructions into two RoboHelp projects: one for the core software and one for an add-in component. The idea is that the core project should not include any of the add-in instructions, but the add-in project can freely reuse information from the core project. (The projects have different owners.) The biggest risk in meeting this new requirement is that the user might incorrectly assume that he can complete the core installation steps, then look at the add-in instructions.
So far, my best idea is to set up a merged WebHelp project. In the core project, I'd use conditionalized snippets at the proper place in the step-by-step instructions to link to the applicable add-in information in the add-in project. (I think I can sell that idea as RoboHelp configuration, rather than combined content.) The add-in project will be pretty simple, with links to the core project.
Can anyone recommend a better approach?