Properties

  Enter the Output Channel's name and a brief description. Enter the file name and extension for the stories files created in this output channel in the "File Name" and "File Extension" fields.

  The URI Format properties determine how the URIs of stories and media will be created in this output channel. In the "URI Format" and "Fixed URI Format" fields, enter the tokens that represent the various parts out of which the URI should be made. Tokens must be separated by `/`; like a URI. The currently available tokens are:

  `%{categories}`

    The category path.

  `%{slug}`

    The slug, applies to stories only.

  `%Y`

    The cover date year.

  `%m`

    The cover date month

  `%d`

    The cover date day.

  %{uuid}

    The document UUID.

  %{base64_uuid}

    The base64-encoded document UUID.

  %{hex_uuid}

    The hex representation of the document UUID.

  For example, a story in the category `/stories`, whose slug is `hello`, with a cover date of Feb. 27, 2002 and URI Format `/%{categories}/%Y/%m/%d/%{slug}/` would have the URI `/stories/2002/02/27/hello/`. Any other DateTime-supported `strftime` format can be used for other parts of the cover date, as well. See the DateTime documentation for the complete list.

  You can also use the URI format fields to set a prefix or postfix directory to the URI. For example with a URI Format of `/foo/%{categories}/%{slug}/bar/` and the file example above the uri would be /foo/stories/hello/bar/index.html. This feature is useful if you're keeping different kinds of content on one delivery server.

  The "URI Case" select list forces URIs in this output channel to be formatted in a particular case, either "Mixed Case" (the default), "Lowercase", or "Uppercase".

  The "Use Slug for Filename" field indicates that the names of the story files created in this output channel should use the slug when possible. This means that non-fixed stories will use the slug to name the file, if it's available. Fixed stories will instead use the name specified in the Filename field, while media will use the name of the media file itself.

Click Next for the second page of the Profile.

Template Includes
  Select existing Output Channels in order to include the templates of those Output Channels in this Output Channel. The idea here is that, when you preview or publish assets via this Output Channel, if the Burn system can't find a template, it'll look for it in the Output Channels selected here. The template includes can be ordered, and they will be searched for templates in that order.

When finished, click Save.