This article covers a Bloomreach Experience Manager version 11. There's an updated version available that covers our most recent release.

Localization modules

Hippo uses a mechanism called localization modules to provide the localized strings to end projects. The Hippo product artifacts only contains English display strings, stored in either regular Java, repository or Angular resource bundle files. The translations for those resource bundles are made available to end-projects as separate localization modules. End-projects pull these localizations modules into their build using the “hippo-l10n-maven-plugin”, which scans the project’s dependencies and adds the necessary localization module dependencies at build time. During the build you will see log statements such as:

Include localization module 'org.onehippo.cms7:hippo-cms-l10n:jar:nl:4.0.0'.

Your project’s root pom.xml defines the property “hippo.cms.locales”, which contains a comma-separated list of locales that should be included in the build.


Note that English (EN) is provided by default and need not be listed.

The included localization module(s) for the main Hippo CMS module will automatically register its locale as available frontend locale for the Hippo CMS login page to show in the language selection dropdown.

For new Hippo projects created with the Hippo Maven Archetype all supported locales are by default included using the above configuration.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?

    We rely on cookies

    to optimize our communication and to enhance your customer experience. By clicking on the Accept and Close button, you agree to the collection of cookies. You can also adjust your preferences by clicking on Manage Preferences. For more information please see our Privacy policy.

    Manage cookies
    Accept & close

    Cookies preferences

    Accept & close