This documentation is still in progress. We are working hard to update all our screenshots to the new Magnolia 6 style. Please bear with us.
The Magnolia UI module is responsible for the user interface of the backend of Magnolia's Admincentral. It provides various UI frameworks for other parts of Magnolia such as content apps.
The Magnolia UI 6.0 project is currently available as a Developer Preview. The full version is still under development.
To provide backward compatibility, it contains all previously existing classes. It also delivers refactored frameworks and new functions. 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.
If you have a custom webapp which is completely independent from any preconfigured Magnolia webapp, below is how you should add the UI project submodules to it:
In your parent pom, import the dependency management from the UI project:
In the pom of your webapp, add the UI submodules you rely on. The following is a typical configuration (from the
Here is a list of all modules in version 6.0 of the Magnolia UI project. The list includes both the Maven modules and the Magnolia modules.
|Function||Magnolia module name(s)1|
The primary module/SDK for Magnolia app development.
It provides – among others – the content app framework, IoC support for UI components & scopes, as well as Vaadin 8 data-binding facilities and UI view/state management.
It also offers convenience builders for selected Magnolia UI components, for example alerts and dialogs.
With Magnolia 6.0, the Vaadin 8 integration & data-bindings are provided as a Developer Preview.
Defines some core components for the UI such as Action, App, SubApp, Message and others.
|JCR implementation of the new UI framework (Developer Preview).|
Magnolia 6 Admincentral, an OS-like Web application running Magnolia apps. This is where authors enter, preview, publish content and where administrators configure Magnolia.
This module is considered private API and may evolve rapidly, without any guarantee of backward/binary compatibility. Developers are encouraged to use what the UI framework offers instead.
Currently this contains mainly former Magnolia 5 widget implementations. For Magnolia 6, most of the components have been re-implemented with plain Vaadin. Consequently, this module may be split and partially deprecated in any future version.
|Magnolia stock apps|
About Magnolia app
JCR Browser app
|Task management app|
|Magnolia 5 compatibility|
Magnolia 5 Admincentral
As of Magnolia 6.0, it still provides – among other things – the app launcher configuration, login form and user preferences dialog. These may be replaced or relocated to the new
This module brings support for running Magnolia 5 content apps in Magnolia 6.
In particular it contains former Magnolia 5 content-app components, such as the workbench, forms and dialogs or image provider. It also provides JCR implementations of the deprecated Vaadin 7 Data API, for example
The following Magnolia 5 Maven modules have been relocated to this module:
Magnolia 5 Vaadin theme
1) The list of Magnolia modules which belong to the given Maven submodule.
Switching to the Magnolia 5 legacy UI
How to use the legacy Magnolia 5 UI in 6.0
If you want to access Magnolia 6.0 with the legacy 5.x look and feel, add a
-m5 suffix to your instance URL after the word admincentral. For example:
This is a useful workaround if you have display issues with custom apps for example.
Note that this legacy UI mode is not fully functional and will not be supported indefinitely. Please make sure you let us know how we can improve the 6.0 UI so that we can fix any issues properly.