growth plans
To use localization with Builder, you must integrate with your codebase so that your app and Builder localization coordinate with one another. This entails:
- Passing the locale to the
BuilderComponentorRenderContent. - Passing the
localevalue in theoptionsobject when fetching content from the API to get JSON with resolved, localized values.
Though the syntax varies depending on the framework, the concept is the same. Select your framework below for examples.
Tip: Passing the locale to the BuilderComponent or RenderContent emits the locale while previewing or editing so the Visual Editor displays localized values.
For whole-page localization, specify your locale as a targeting attribute when fetching your Builder content from the Content API.
For more fine-grained control, you can localize individual blocks within your content. This approach depends on populating your content's state with your locale:
For example, given a greeting object, with localized values for en-US and fr-Fr, Builder would transform it to Hello or Bonjour depending on the locale:
// orginal object with values for each locale
"greeting": {
"en-US": "Hello",
"fr-Fr": "Bonjour"
}Builder transforms the object to use the value that corresponds to the locale, as follows:
// locale=en-US
"greeting":"Hello"// locale=fr-Fr
"greeting": "Bonjour"When your codebase and Builder localization are successfully integrated, you can use any of Builder's localization techniques.
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.
