Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.

The Content Types module allows defining Magnolia content types for instance in a single YAML file of a light module. By defining a custom JCR node type, workspace and namespace in a single YAML file of a light module there's no need to deploy a WAR file or restart a Magnolia instance. Now with just a few lines of YAML code referring to the content type definition you can quickly create a content app descriptor managing the content items defined.

(warning) 5.7.2+  This module requires Magnolia 5.7.2 or higher versions.

For complex node definitions the Content Types module also supports XML file based JCR node type definitions served as resource files from a light module.

The Content Types module currently is not  part of the preconfigured Magnolia bundles and webapps of the 5.7.x series, you have to add it yourself.


Maven is the easiest way to install the module. Add the following to your bundle. The parent POM of your webapp project should set the latest version of the module automatically. Should you need to use a specific module version, you can define it using the <version/> in the dependency.



The magnolia-content-types module does not require any configuration. However, it is responsible for detection and registration of the following items: