Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

Magnolia stores all content in a content repository. The repository implementation we have chosen, Apache Jackrabbit, adheres to the Java Content Repository standard (JCR). A content repository is a high-level information management system that is a superset of traditional data repositories. It implements content services such as:

  • Granular content access and access control
  • Hierarchical, structured and unstructured content
  • Node types, property types (text, number, date, binary)
  • Queries (XPath, SQL)
  • Import and export.

Diagram

Concept

Repository and workspaces
Here's what the object hierarchy in a repository looks like:

  1. Repository contains workspaces
  2. Workspace contains nodes
  3. Each workspace has a single root node.
  4. Node contains properties
  5. Properties store values (data)

Magnolia workspaces
Magnolia has one repository, magnolia, which in turn contains several workspaces:

  • website. Websites, pages and paragraphs.
  • config. Configuration settings for everything.
  • data. Custom data types and data items.
  • dms. Documents and images, typically binary data.
  • templates. Page and paragraph templates in the Standard Templating Kit (STK)
  • resources. JavaScript and CSS style sheet files used by the STK and themes.
  • userroles. Roles and access control lists (ACL) for granting permissions to users.
  • usergroups. Groups of users.
  • users. System, administrative and public user accounts.

Hierarchical content store
A content repository is designed to store, search and retrieve hierarchical data. Data consists of a tree of nodes with associated properties. Data is stored in the properties. They may store simple values such as numbers and strings or binary data (images, documents) of arbitrary length.

JCR standard API for content repositories
Java Content Repository (JCR) is a standard interface for accessing content repositories. The standard decouples the responsibilities of content storage from content management and provides a common API that enables content reuse across the enterprise and between applications.

  • No labels