CMS UI Localization
Bloomreach Content supports international teams by providing localization for both content and the CMS user interface (UI). The CMS allows users to maintain multiple translations of content and offers a fully translatable UI. This page describes how UI localization works in Bloomreach Content. For information about translating content, see Adding a new language to an already existing site.
When users sign in to Bloomreach Content, they can select their preferred language for the CMS UI. UI text strings are sourced and translated through multiple mechanisms. Some strings are provided by the core product, while others come from project-specific plugins or configuration.
This page covers:
- Sources of UI strings
- Translation mechanisms used in Bloomreach Content
Sources of UI Strings
UI strings in Bloomreach Content come from several sources. By default, the CMS UI is available in multiple languages. Bloomreach maintains translations for all new features and for all default and standard plugins in these languages. Adding support for additional languages is possible but requires significant effort. For details, see Configure the CMS login page.
Most UI strings are provided by the core product. These strings are typically managed through compile-time resource bundles and, in some cases, through repository resource bundles. Because Bloomreach Content is highly configurable and extensible, many visible strings are not part of the core product. These additional strings are supplied by project configuration and plugins.
Strings from Project Configuration
Many UI strings originate from a project's content model and configuration. Examples include:
- Document type names
- Field names and hints in the content editor
- Messages for custom validation errors
You can translate these strings as part of your project configuration. For more information, see:
- Translations of document types and image sets
- Configure and translate custom validators
- Set up and translate custom Advanced Search filters
- Control allowed document types in folders
These translations use repository resource bundles.
Strings from Plugins
You can extend Bloomreach Content with custom plugins. Each plugin mechanism uses a specific translation approach.
For details on providing translations for common plugins, see:
- For channel and component configuration dialogs, refer to Annotate Channel or Component Configuration Parameters with UI Directives, section "Localization".
- For custom targeting collectors, see Targeting collectors documentation, section "Example: GroupsCollectorPlugin".
- Targeting providers use compile-time resource bundles.
These plugin translations are managed with compile-time resource bundles.