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.
This pages matters only if you define your app via JCR configuration. Since Magnolia 5.4 you can define an app with a YAML file too - see App descriptor. If you define the app via YAML - the configuration can be part of a light module or in the resources folder of Magnolia Maven module - see Module structure.
Bootstrapping app configuration
To package your app for deployment:
- Add an
appsfolder under your module configuration.
apps, add a content node and name it after your app name, for example
- Under the app content node, create the app properties and set their values.
- Export the app configuration into XML and include it in your bootstrap files so that it is installed when the module is installed.
See App descriptor for an example.
Bootstrapping the App launcher layout
To make your app icon available in the App launcher:
- Add the app to an existing group in the Apps launcher layout or create a new group for it.
- Export the app launcher configuration into XML and include it in your bootstrap files.