Types of Content - Fluid Topics - 3.10 - Technical Notes

Develop Connectors with the Fluid Topics API

Fluid Topics
Fluid Topics Version
Technical Notes
Target Audience

Publishing data to Fluid Topics generates different types of documents. A document can be made of several textual parts and embed some files, or it can fully rely on a file.

A file is a self-sufficient binary or text file (PDF files, text files, images, videos, archives like ZIPs, ...).

Files can be:

  • Used as a document.
  • Embedded within a Topic.
  • Attached to a Structured Document.

There are three types of documents:

  • Structured: refers to content that has been organized and classified using metadata. A Structured Document (or Map for short) is a succession of textual parts called Topics, which are organized in a Table of Contents. A Topic is a section of text that can include some files called Resources and is associated with one or several Structured Documents. It is also possible to associate Structured Documents with Attachments that rely on files. These attachments are not part of the indexed content.

    Examples of Structured Content:

    • DITA generated content
    • Author-it generated content

      Two editorial types are available for Structured Documents:

    • Article: a document whose content is indivisible although it may be composed of multiple fragments. We refer to those fragments as Article topics. Articles must be read from the beginning.
    • Book (default type): a document with sections of content that can each make sense separately. We refer to these sections as Book topics. Books can be accessed starting with any topic.

  • Unstructured: refers to content that relies on a file. The Unstructured Documents (or UD for short) are intended to be indexed (i.e made "searchable"). The Viewer page is the dedicated tool for consulting these documents.

  • External: refers to content that are hosted outside of Fluid Topics and accessed via a URL. External Documents are indexed by Fluid Topics in order to appear in the search results, but cannot be viewed in the Reader page.

The content classes are illustrated in the following diagram: