Merging Help projects
About merged Help projects
Using RoboHelp, you can create projects in an enterprise or distributed setup where different documentation projects feed into a common project. You can achieve multi-authoring without using source-control software because multiple writers can work on their individual projects and you merge them to create the common project. By using skins and templates in the common project, you can achieve a unified appearance in the merged projects.
The merging takes place at run time, after the projects are generated. Before merging the projects, you simply place references to other projects inside a master project (the master project does not actually contain the child projects). You insert each reference in the master project's table of contents, placing it where you want the TOC of the child project to appear. This step gives you control over where end users access the child project and gives the appearance of a single, unified Help system. End users see a single online system complete with a table of contents, an index, full-text search, a glossary (in WebHelp projects), and link controls.important: The child projects must not have content categories.
Merging multiple projects involves these steps:
•Create a master project with references to child projects in the TOC. See Create a master project.
•Publish the child projects. See Publish child projects.
note: For master projects having the Adobe AIR Application output type, publish the child projects as browser-based Adobe AIR Help.
Browser based Help output type selection
•(Adobe AIR Application output type only) Regenerate the output of the master project. See Configure the Adobe AIR layout.
note: Responsive HTML5, WebHelp Pro, and FlashHelp Pro projects are automatically published by RoboHelp Server.