Back to Search Back to Search Results

Installing a Document Type

Follow these steps to create a new document type in Titania Delivery.
  1. Create the Document Type container in the appropriate organization.
    1. Click the New button on the Document Types section for your organization to create the empty Document Type object.
    2. Specify a name for the document type.
    3. Optional: If customizing an existing document type, select that document type from the list of "Based On" document types. For example, if setting up a DITA specialization, Select the DITA 1.3 document type.
    4. Click Save to create the empty doctype container.
  2. Add the DTD and/or XSD modules for your specialized shells to the document type project.
    The structure of these files doesn't matter. All that matters is that they are present.
  3. Add a catalog file.
    This file defines mappings for resolving public identifiers and/or URIs from project documents that use this document type to DTD or XSD modules in the document type container. This file must exist at the top level of the document type, and must be named catalog.xml, catalog.txt, or catalog. The contents of the file must be in either the XML Catalog format or TR 9401 "text" catalog format. Both these formats have the ability to reference other catalog files, and those features are fully supported and encouraged.
  4. For non-DITA document types, add a doctype descriptor.
    Create a file at /HARP-META/doctype.xml describing the important elements and attributes in your document type. See Doctype Descriptor Format for details.
  5. Optionally, create an XSLT module for converting documents of this doctype to HTML.
    If desired, create a HARP-META/html.xsl file that can be linked into portal HTML transforms. See Writing XSLT for DITA and Writing XSLT for Non-DITA XML for details.
  6. Create a preview stylesheet.
    If your document type is an extension of another document type, this is optional, and the stylesheet from the base doctype will be used by default. Otherwise, create /preview.xsl for building an admin HTML preview for your document type. This can frequently be a simple inclusion of HARP-META/html.xsl.
  7. Optionally, create custom pre-processing transforms for your document type.
    See Custom Processing of XML Content for details.
  8. Add the document type to existing projects.
    In order for content in a project to use the new document type configuration, the document type must be added to the XML Document Type list for that project.
    Note: From this point forward, any new projects created under the same organization as the document type will automatically have a link to the document type. You only need to do this for existing projects.
    1. Select the root node in the project you want to update and select the XML Document Type tab.
    2. Click the Add button and select the document type from the list, and click OK.
    3. Re-process any content that should use the new document type.
Parent topic: Document Type Developer's Guide