Content Repository

How to access the content repository (of the CMS) via the web console? The web console is an alternative user interface to the content repository (the other being the CMS itself). The web console is only for developers: it allows changes that the CMS does not, including unsafe changes. It also allows import and exports into and from a running repository.

How to edit the content repository (of the CMS) via the web console?

How are variants of documents stored in the Hippo repository.

A compact node type definition is used by JCR (Jackrabbit) to define the possibilities of a JCR node.

The CND is sufficient for using the Hippo JCR repository. Only if you want to use the CMS, which is a GUI to the Hippo JCR repository, you need additional node type definitions, which can be found in the repository under one of the CMS namespace nodes under the hippo:namespaces node.

The content repository of Hippo CMS is already filled with standard content. You can use the standard content as examples. This document tells you where to look.

Note that if you use the quickstart or your own project created by archetype then there is more standard content than if you use the package named 'package'.

What about the nodes in the Hippo CMS repository?

Upgrading your project to a CMS 7 version that uses newer basic Hippo JCR namespaces. Preventing work in future upgrades.

This section describes how you can add a field to a strict type or a type to an existing namespace that is backward compatible. Note that with the advent of version 7.6 this is no longer an issue. Version 7.6 introduced the concept of relaxed CND which makes all type changes backward compatible. However in case a project still wants to use strict types this section is relevant.

How to initialize the Hippo repository, importing CND files, XML node files and performing repository actions.

How to implement workflow within Hippo CMS using the internal workflow mechanism?