This article covers a Hippo CMS version 11. There's an updated version available that covers our most recent release.

Top Level Repository Nodes

Introduction

Hippo's content repository is used to store content as well as configuration in a node tree. The CMS Console can be used to browse the node tree. This pages provides an overview of the top level nodes and what they are used for.

jcr:system

Used by the underlying Jackrabbit application.

hippo:configuration

Contains Hippo CMS configuration.

hippo:log

Contains the Hippo Event Log. Hippo Repository logs all workflow invocations as JCR nodes. These nodes contain information about which user performed what workflow operation when and on what document. 

hippo:namespaces

Contains namespaces in which content type definitions are stored. Most content type definitions are created using the Document Type Editor. Image Set types are configured using Hippo's setup application.

hst:hst

Contains delivery tier configuration such as hosts, channels, URLs, pages, components, and templates.

content

Contains all content managed through the CMS UI.

  • /content/documents - Editable documents.
  • /content/gallery - Uploaded images.
  • /content/assets - Uploaded assets (e.g. non-editable files such as PDFs).
  • /content/attic - Deleted content.

formdata

Temporary storage for form data persisted during a Post/Redirect/Get sequence.

hippo:reports

Reporting Dashboard configuration (Enterprise Edition).

targeting:targeting

Relevance Module configuration (Enterprise Edition).