Magnolia 6.0 reached end of life on June 26, 2019. This branch is no longer supported, see End-of-life policy.
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.
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 Magnolia Content Types module is currently available as a Developer Preview. The full version is still under development.
This developer preview brings several powerful features. Please try it out and feel free to send us your feedback and suggestions based on your experience.
We are working to finalize the module as soon as possible.
magnolia-content-types module does not require any configuration. However, it is responsible for detection and registration of the following items:
The XML node type definition resource is loaded only if the XML resource is referenced in the Content type Data source definition of a Content type definition.
Follow the Content Types tutorial to learn how to use Magnolia content types, create content type definitions and corresponding apps.