growth plans
In the Builder Visual Editor, you can configure individual blocks to deliver content specific to language and region preferences.
For example, if you wanted to differentiate copy or images for a visitor in Germany or a visitor in Mexico, you could adjust a few settings on the block and add locale-specific content in the block's localization settings.
You can individually localize many blocks, including the following, in the Visual Editor:
- Text
- Images
- Colors
- Symbol inputs
The process is the same for each in that you hover over the label in the Edit dialogue to show the Localize icon, click the icon, and add content to each locale.
To successfully use localization in Builder, make sure you've already done the following:
The last part of setting up localization is to integrate. For instructions, continue to Integrating Builder Localization with your code.
- Double click the block to open the Edit dialogue.
- Hover over the label of the block; for example, the label Text in a Text edit dialogue, and click the Localize icon.
- In the locale dropdown, choose the locale you'd like to edit. As a best practice, always set a value for the Default locale in case none of the other locales are in the user's settings.
- Enter content per locale.
The following video demonstrates adding localized content with two examples:
- A Text block
- An Image block
This video also shows how to select the locale for the entire content entry, which you can do by selecting the local at the top of the work area.
Tip: If you don't have any locales, click the link to Add a new locale, which displays when you hover over the locales dropdown. You can also add multiple locales in a single dialogue as outlined in Adding locales in Account settings.
To customize content for specific groups of people within your different language options, you can use targeting, and within this targeted content, you can localize inputs or fields.
To use this feature:
- Pass the
localeproperty to theBuilderComponentwhen integrating Builder into your app. This ensures that the content in the Visual Editor is localized based on the specified locale. - When making an API call to retrieve the content, include the
localeparameter, and pass the currentlocalevalue. This makes sure that the content returned from the API call is specific to the desiredlocale.
This streamlined process makes the localization workflow more direct, helping you efficiently manage localized content within the Builder environment, without the need for additional data connections.
const Page = await builder.get(page, {
options: { locale }, // Pass the locale property to the options object
userAttributes: {
urlPath: `/about`,
locale, // Pass the locale property to the userAttributes object
},
}).toPromise();
To enable field localization, explicitly mark them as localized in the model settings. This ensures that the content within those fields can be customized based on different languages or regions.
Additionally, you can localize inputs by clicking on the globe icon within the Edit dialogue. This way you can provide localized values for inputs such as text or images.
By default, all inputs can be localized unless you specifically set the localized property to false when registering your custom component. This gives you flexibility in deciding which inputs can be localized and which ones should remain static across different locales.
To remove localization from a selected block:
- Open the Edit dialogue for the block. Do this by double-clicking the block or selecting the block and clicking the Edit button.
- This step removes the localized content. Hover over the dialogue label and click on the Localize icon.
By toggling off localization for a block, the localization dropdown no longer displays, and the content is removed. The following video demonstrates this process.
Looking to hire a third party to help with your project?
Submit a project request and our partnerships team will reach out to connect you with an Expert from our partner ecosystem.
