Content Types module

Content management Bundled: Community Edition

Edition CE




Maven site



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.

Installing with Maven

Bundled modules are automatically installed for you.

If the module is unbundled, add the following to your bundle including your project’s <dependencyManagement> section and your webapp’s <dependencies> section. If the module is unbundled but the parent POM manages the version, add the following to your webapp’s <dependencies> section.

  <version>1.2</version> (1)
1 Should you need to specify the module version, do it using <version>.


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

The CND node type definition resource is loaded only if the CND resource is referenced in the 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.

DX Core



This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules