This zip is a sample branding plug-in for the DITA Open Toolkit.

Unzip directly into the DITA-OT install directory.

Run startcmd.bat from the root DITA-OT install directory to set up your build environment.
On Unix or Mac systems, run the shell script startcmd.sh.

From the prompt that appears after setting up your environment, run
ant -f sample_metadita.xml

NOTE: on Windows systems, the batch file run_sample_metadita.bat is equivalent to running
      startcmd.bat and running the build in a single step.

TO UPDATE FOR YOUR OWN BRAND:
1. Open the sample_metadita.xml file in a text editor.
2. Update properties to point to your own CSS information. For example,
   edit this line so that it points to the directory that contains your branding info:
<property name="brand.dir" value="${basedir}${file.separator}metadita"/>
   This directory should contain your CSS and any header or footer files.
3. Edit this line to set your desired output directory. The default is
   out/metadita (relative to the XML file you are editing).
<property name="sample.output.dir" value="out${file.separator}metadita"/>
4. Edit the args.input parameter so that it points to your input file
   rather than the DITA-OT sample file hierarchy.ditamap:
      <property name="args.input"
        value="${dita.dir}${file.separator}samples${file.separator}hierarchy.ditamap"/>
5. Update the args.css parameter to use the name of your CSS file:
      <property name="args.css"
        value="metadita_style.css"/>
6. Update the args.hdf, args.hdr, and args.ftr parameters so that they point to
   your actual header and footer files. If these are not needed, simply delete
   the appropriate lines. For example, edit (or delete) the following line to change
   what appears in each XHTML header section:
      <property name="args.hdr" value="${brand.dir}${file.separator}metadita_hdr.html"/>
7. If your CSS file uses images, you will need to copy those to the output directory.
   The sample build copies all *.jpg files from the images/ directory of your branding
   information into the images/ directory of your output CSS directory. If you do not
   have any CSS images, then delete these lines. If you do have CSS images, you have two
   options:
   7a. Store all of them in the images directory, and ensure they are all .JPG files.
   7b. Edit the <copy> command so that it uses the directory values you need. For example,
       in the content below, changing "images" to "img" in both cases will copy all JPG
       files to and from the "img" subdirectory of your branding content. Changing "*.jpg"
       to "*.jpg,*.gif" will copy all JPG files as well as all GIF files.
    <copy todir="${sample.output.dir}${file.separator}css${file.separator}images">
        <fileset dir="${css.source.dir}${file.separator}images"
            includes="*.jpg"/>
    </copy>
8. To remove the comment about this file that appears at the end of each build, remove
   the following line:
    <antcall target="readme"/>

If you have comments or questions, or suggestions for clarifications, please contact
me (Robert D. Anderson) at robander@us.ibm.com. Thanks!