Understanding Build Manifest templates

If many of your Build Manifests share certain properties, such as the output types or user properties, you can define Build Manifest templates that automatically include these properties in any Build Manifests that you create.

For example.

• You create Gadget documentation in three formats: PDF, HTML, and online help. You create Widget documentation only in PDF and HTML. In such a case, create separate Build Manifest templates that include the appropriate output types.
• You include default user parameters for each output. For example, your PDF output requires three user parameters with specific values. In this case, add those parameters and values to the Build Manifest template..

The following shows the structure of a sample Build Manifest template:

In this example, output types are defined on lines 19 and 31. The Acme-Pdf output is generated only in English (line 22). The Acme-xhtml output is generated in English, German, and French (lines 34-36). The Acme-PDF output requires three user properties with specified values (lines 25-27). Both outputs are filtered with a ditaval (lines 29 and 38).

The Build Manifest overall is set to "pick up" maps at Localization:done and Translation:done (line 7). This is a BOTH Build Manifest (line 6), meaning that it can be run on-demand or via a script.