Overview of the Custom.xml File

The Custom.dtd file defines the legal building blocks for the site-specific documents.

The structure of the XML is as follows:

  • Sections. Information is presented in two columns, using the left and right portions of the page.

    This data uses the <leftsection> and <rightsection> elements. Each section must include at least one group.

  • Groups. Collections of related categories of documents are presented in the left or right half of the page (such as General Interest or Training).

    This data uses the <group> element.

    A group is composed of:

    • Heading (using the <head> element)

      • Heading title (using the <htitle> element)

      • (Optional) Heading description (using the <hdesc> element)

    • (Optional) One or more subheadings (using the <subhead> element)

      • Subheading title (using the <stitle> element)

      • (Optional) Subheading description (using the <sdesc> element)

    • At least one document element.

  • Documents. Titles and links that specify site-specific documents (such as Guidelines for managing resource pools and Analyzing Performance) are presented within groups.

    This data relies on the <document> element.

    A document is composed of:

    • Document title (using the <dtitle> element)

    • Document file name (using the <dfn> element)

      Specify the path of the file relative to the pdf directory (see Where to Find the Files for details on the PPM Server file organization).

    • (Possibly optional) Document type (using the <dtype> element)

      If the file format is not PDF, the file format must also be included (see Supported File Types for details).

  • Title. The name of the custom page can be uniquely specified (such as "XYZ Company" as shown in Figure 4-3. Custom, site-specific documents).

    This data uses the <title> element.

For your convenience, the Custom.dtd file is included in Sample Files. The content for this XML file is optional; however, an "empty" file similar to the following must be provided.

<?xml version="1.0" ?>
<!DOCTYPE custom SYSTEM "../Custom.dtd">