### 16.11 Setting up a dynamic modular Help system

Suppose you are providing Help for a product with several optional modules, and you want to supply each customer with information only about the modules licensed by that customer. Or, suppose a user decides not to install a module, or adds a new module later. Or, suppose you have created reusable Help modules that can be incorporated into any of a number of main Help systems, such as “Help on Help”.

Any Help system that DITA2Go generates can be made to access more than one module, yet appear to the user as a single unit. The user accesses a single Help file, and sees integrated contents, index, and related-topic links, containing information only for the relevant modules. Additional modules are loaded dynamically, when a user clicks a Contents, Index, Related Topics, or Search entry that references a separate module.

Methods and configuration settings vary according to which type of Help system you are generating. See the following for more information:

Help system | Reference
WinHelp | §17.2.8 Providing multiple .hlp files
MS HTML Help | §18.14 Mapping and merging CHM files
OmniHelp | §19.12 Merging OmniHelp projects
JavaHelp, Oracle Help for Java | §20.11 Merging JavaHelp or Oracle Help systems
Eclipse Help | §21.6 Merging Eclipse Help projects

Previous Topic: 16.10.2 Specifying CSH mappings

Next Topic: 17. Generating WinHelp

Parent Topic: 16. Producing on-line Help

Sibling Topics:

16.1 Weighing Help-system alternatives

16.2 Completing Help system construction

16.3 Producing contents and index for Help systems

16.4 Configuring contents entries for Help systems

16.5 Configuring index entries for Help systems

16.6 Providing related-topic links for Help systems

16.7 Jumping to secondary windows in Help systems

16.8 Creating pop-up topics for Help systems

16.9 Including expandable sections in Help topics

16.10 Setting up Context Sensitive Help (CSH)

Table of Contents • Index