Brightspot CMS Developer Guide

Localizing Brightspot

You can customize Brightspot’s widgets and content edit forms so that editors see the UI in their preferred language. Localizing Brightspot is similar to that for other Java-based web applications.

To localize widgets:

  1. Clone or download a new copy of the Brightspot repository.
  2. Open your existing Brightspot project in a file manager.
  3. From the cloned repository, recursively copy all files *Default_xx.propertiesin the directory db/src/main/resources to your Brightspot project directory src/main/ (so that the directory resources/appears under main/).

    • Retain the directory structure for the copied files.
    • Example: cp resources/com/psddev/cms/tool/widget/ src/main/resources/com/psddev/cms/tool/widget/
    In addition to the English-language property files *, the cloned repository may also provide property files for other languages such as Spanish (* If your target language is included, go to step 6.

  4. If Brightspot does not provide the property files for your target language, rename each * to *

    • The two letters before .propertiesmust be a language code that Java recognizes. For a list of two-letter language codes, see List of ISO 639-1 codes.
    • Example: mv
  5. For each of the resource files, provide localized strings.
    # Localization for the Upload widgettitle=Transfert Groupé
    message.noTypes=Il n'y a pas de types de contenu qui peuvent être transfert groupé.
  6. Rebuild your Brightspot project.

Users who change their Locale setting in Admin > Users & Roles see the localized text in Brightspot.

Localized text.png Localized text.png

You can localize the field and tab labels in content edit forms. The following screen shots show the content edit form after localizing an Article model into Spanish.

English content edit form.png English content edit form.png
Original English content edit form
Localized content edit form.png Localized content edit form.png
Localized Spanish content edit form

Localization of content edit forms is achieved with properties files, where keys for fields and tabs are set with language-specific strings.

To create a localized properties file for a model:

  1. Change to or create the resources/directory for your Brightspot project. This directory is in the standard position for Maven projects, src/main/resources/, although your Brightspot project may have a different resources/ directory if your project includes themes.
  2. Change to or create the subdirectory corresponding to the required model. For example, if you are localizing the content edit form for articles, change to or create the subdirectory article/.
  3. Create the file <ContentType>Default.properties_xx. For example, the file ArticleDefault_es.propertieslocalizes the article model into Spanish.
  4. In the properties file, add lines that specify the localized names of fields and tabs, using the following forms: field.<fieldname>=<localname> and tab.<tabname>=<localname>.

    The following example shows localization of an Article model into Spanish.

    # Localization for Article Content Edit Form
    field.leadImage=Imagen de Plomo
    field.body=Texto del Cuerpo
    tab.Push\ Notification=Notificación
    • Localizes names of fields defined in the Article model.
    • Localizes names of the default tabs that Brightspot provides for content edit forms. If a tab name has more than one word, such as Push Notification, the spaces between words need to be escaped.

      If you add custom tabs to a model via @ToolUi.Tab, they can also be localized by adding their names to the properties file.

  5. Reload or rebuild your Brightspot project.

Users who change their Locale setting in Admin > Users & Roles see the localized text in Brightspot.

Previous Topic
Next Topic
Localizing published websites
Was this topic helpful?
Thanks for your feedback.
Our robust, flexible Design System provides hundreds of pre-built components you can use to build the presentation layer of your dreams.

Asset types
Module types
Page types
Brightspot is packaged with content types that get you up and running in a matter of days, including assets, modules and landing pages.

Content types
Landing pages
Everything you need to know when creating, managing, and administering content within Brightspot CMS.

Admin configurations
A guide for installing, supporting, extending, modifying and administering code on the Brightspot platform.

Field types
Content modeling
Rich-text elements
A guide to configuring Brightspot's library of integrations, including pre-built options and developer-configured extensions.

Google Analytics
Apple News