Welcome to Titania Delivery

Primary Concepts

Projects

A Project is a container where the content owner places the content they want to distribute. You can think of a Project as a virtual file system containing your files, organized into folders.

Content can be uploaded manually through the administrative web application, automatically via Sync Services, or the Titania Delivery content upload SDK. A Portal's content can be shared through any number of Portals. Projects have access control rules defining the users who have access to various content and delivery management functions within a Portal.

Portals

A Portal is a content delivery channel. Think of a Portal like its own website targeted at an individual audience. A Portal can pull its content from one or more Projects and filter that content using Metadata rules.

Portal Themes

A Portal Theme allows you to control every aspect of the appearance of a Portal, from the HTML and CSS of the web pages themselves to the stylesheets used to convert XML content into viewable HTML.

Organizations

An Organization is a list of users that act as a unit for purposes of content delivery management. An Organization has ownership of its own Projects and Portals, and can also be added to Projects owned by other users or Organizations.

Document Types

A Document Type is a special kind of Project that contains the XML grammar definition files – DTDs and XML Schemas – that are used to parse XML content.

Metadata

Metadata provides information about the content; think of it as properties you can customize for single or multiple files. These values set on your files can be used in multiple ways to enhance the delivery of your content. See Empowering your Content Delivery with Metadata for additional details.

Titania Sync

Titania Sync ™ is an optional component that can be used to synchronize content from your content management system into Delivery Projects automatically based on life cycle or workflow triggers.

Storing Content in Projects

A Project is similar to the file system on a computer. You can load files into a Project and organize those files into folders. Any relative paths in your XML content will be resolved using the folder structure of the Project. Projects have a number of additional features to aid in content delivery:

• Projects include a set of document types to parse and validate the XML files in your Portal.

• Titania Delivery records the relationships between XML document so that it can understand the implications when files are updated.

• You can assign Metadata – custom properties – on files stored in a Project to enable dynamic content delivery features.

Delivering Content through Portals

A Portal is the website used to deliver the content stored in Projects to your users. Portals draw content from specific Projects, filtered using Metadata rules. A single Project might be published using multiple Portals, but each Portal might use a different subset of that Project's contents based on the preset Metadata-based filtering.

The look and feel of a Portal is configured using a Portal Theme, which enables you full control over a Portal's appearance. The default Portal Theme is configured with a mobile-first responsive design, so it will function well on virtually any device. The Portal Themes are also easily customized. You can either use the default Theme or you can choose to build a new Portal Theme entirely.

Gathering Metrics and Feedback

Titania Delivery automatically logs access to Portals and records information about each individual visitor. This includes the content they viewed as well as the kind of device they used to view it. These Metrics can be used to drive future decisions of how to structure your content. You can also identify high and low-value content based on how often different topics are viewed. This information can help you decide which topics are most important to your readers, and which topics require more frequent updates.

In addition, each topic in a Portal allows users to specify whether or not that content was useful via a simple up/down vote button. Users can also leave comments on your content, enabling authors to improve it in future revisions.

Portal Content Filtering

When you associate a Project with a Portal, by default, all content of that Project becomes available through that Portal. However, you can filter the content for the Portal by assigning Metadata filters.

For example, your implementation has a system managing the documentation for two brands: Acme and Uber. All of the documentation is stored in a single Project, with some content marked brand=acme and some as brand=uber. In addition, you have other topics that apply across brands as brand={acme, uber}. However, each brand can have its own Portal, each pointing to the same single Project, but restricting what's available using Metadata filtering. Refer to the diagram below:\x`:

Search Result Filtering

The Portal administrator can configure Titania Delivery with Metadata types to be used as Search Facets. Users executing searches on a Portal can filter the results using these Metadata values. Titania Delivery also displays the number of results for the current search for each value of filterable Metadata. For example:

Rendering Details

You can configure Portal Themes to use a file's Metadata when displaying it. For example, you might configure the Portal to render content marked with draft=true differently from other files. For example, you might render it with a different color heading, or inserting the word DRAFT into the title, or placing a watermark behind the text, like so:

Header Bar and Menu

Titania Delivery Portals have a header that contains various links. In addition on some pages, web portals also have a search form.

However, on smaller screens, this would take up too much horizontal space. To save that space, HARP moves the links and the header to a menu box once the screen becomes too small.

Table of Contents

When viewing a DITA topic through a Portal, the table of contents for the current publication appears on the left with the current location highlighted.

When viewing on a mobile device, the Table of Contents uses too much space on the smaller screen, so the table of contents is not visible. In this case, a Table of Contents link appears in the header menu allowing you to switch back and forth between the content of the current topic and the table of contents (seen above).

Refining Searches

The Search Results page has a form that enables users to perform another search or to refine the current search using Search Facets

When viewing on a mobile device, this also uses too much space on the smaller screen. Therfore, on the topic viewing page, there is a Refine Search link available on the heading menu that enables users to toggle back and forth between the search results and the search form.