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.
Icons add visual value to apps and actions. They help users instantly recognize user interface elements. Icons also add familiarity when used consistently across Magnolia.
Magnolia icon font
Icons used in Magnolia come from the pictographic
MagnoliaIcons font. Each icon is a character. The character is a vector format rather than a bitmap, which means you can style the icons with CSS and display them in various sizes without repeating the asset itself.
Icons are displayed in the following sizes in the user interface.
Choosing an icon
When choosing an icon for your own app or action:
- Look through the icons provided in the
MagnoliaIconsfont. Find an icon that represents your app or action well.
- Avoid icons that are already used. Using the same icon for two different purposes confuses users and leads to errors.
- If you create your own icons, adhere to the Magnolia design language.
Using a custom icon font
To use a custom icon font:
- Create an icon font.
- Create a CSS file which references your custom font.
- In the CSS file, specify classes for your icons. Use a namespace that will prevent collision with Magnolia's native classes. For example
- Configure a custom Vaadin theme that is different from the default
admincentraltheme. Your Vaadin theme should include
admincentraltheme and it needs to compile it. See Using custom styles in your Magnolia app.