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.
pagessince a Pages app already exists.
Referring to a content type
This approach keeps the app descriptor very short. There is no need to specify the below mentioned properties. The content types and content apps frameworks automatically generate and register an app description based on the content type definition.
Example:5.7.3+ Use the directive
!content-typeto reference a content type. (With Magnolia 5.7.2, you must use
You can tailor the app descriptor within the same file by adding additional configuration which will overwrite any configuration with the same name coming from the
!content-type directive. Alternatively create a decoration.
Here is an example descriptor for a
Node containing subapps.
Fully qualified name of the Java class that contains the app business logic. The class must implement the interface.
Name of the app.
If a value is not provided, either the file name (without the suffix .yaml) or the JCR node name is used.
optional, default is
App descriptor class that reads the configuration. The class must implement the interface.
optional , default is
Enables and disables the app.
CSS class that identifies an icon font used on the app tile. For available names see Icons.
Message bundle for localized labels.
Label displayed on the app icon in the app launcher.
Name of a custom app theme.
The permission to use an app is granted in the
permissions configuration. The subnodes are roles. This allows you to provision the app to certain users in your organization.
In this example the helloworld app is provisioned to
travel-demo-publisher roles. The role property name (
publishers) is arbitrary - use any name you like. The value must be a valid role name.