Skip to main content

Localization

note

For information about delivering localized content to site visitors—including locale configuration, delivery strategies, and date format customization—see Localization.

Brightspot allows you to customize the CMS interface for different locales by configuring localized static text. Static text includes field labels, display names, and other UI strings that remain constant regardless of the asset a user is viewing. By overriding these values through localization bundles, you can control how the CMS interface appears to editors—for example, renaming a notification delivery method or restricting which content types are available in a field.

Configuring localized static text​

Display names​

You can configure localized static text to change display names, like the name of an available delivery method for the purposes of notifications, in Brightspot. This is helpful for editors who want to customize the Brightspot UI. This topic contains an example of how to change the display name of a notification delivery method.

A delivery method with its name customized to "New Delivery Method Name"

To configure localized static text to change display names:

  1. Follow steps 1–5a in Configuring localized static text.

  2. In the Name field, enter the fully qualified class name of the view you are localizing. For this example, enter com/psddev/cms/notification/BrowserDeliveryOption.

    note

    To find fully-qualified class names in Brightspot, for the sake of editing other display names in a similar manner, see Viewing developer info.

  3. Under Entries, click .

  4. In the Key field, enter the key for the static text you are localizing. For this example, enter displayName.

  5. In the Value field, enter the localized text. For this example, enter the new display name of the notification delivery method. For this example, enter New Delivery Method Name. Your form should look similar to the following:

    5.0-changing-delivery-method-name-via-localized-static-text

  6. Click Save.

Brightspot then changes the display name for the value you input.

Objects in fields​

You can configure localized static text to restrict content types that can be used in reference fields. This is helpful for editors who want to make changes to the Brightspot UI. This topic contains an example of how to restrict editors to adding only Attachment List modules to the Content field in the Page content type.

Restricting object type example.png

To configure localized static text to restrict types in fields:

  1. Follow steps 1–5a in Configuring localized static text.

  2. In the Name field, enter the fully qualified class name of the view you are localizing. For this example, enter brightspot/genericpage/GenericPage.

    note

    To find fully-qualified class names in Brightspot, for the sake of making other restrictions in a similar manner, see Viewing developer info.

  3. Under Entries, click .

  4. In the Key field, enter the key for the static text you are localizing. For this example, enter field.contents.groups.

  5. In the Value field, enter the localized text. For this example, enter the object type to which you want to restrict the field. For this example, enter brightspot.module.list.attachment.inline.AttachmentListModulePlacementInline. Your form should look similar to the following:

    5.0-localized-static-text-to-restrict-object-types

  6. Click Save.

Brightspot then restricts the type of objects that can be added to the field you input.