Activating i18n

Multiple content locales, available in all paid plans, are defined in the schema settings.

Here, you define which locales your project will support.

Adding a locale

Type in a name for the locale you want to support, or use the drop-down list to choose one of the common ones. The naming convention we have chosen corresponds to the widest supported standard for language locales.

Be sure to hit update locales!

"Add Locales"

Translating content

To add translated content, you need to define a model's field as translatable. Choosing any of your models, edit one of the field definitions and click on advanced. From there, you will see the option to make the field "translatable."

"Add Locale support to fields"

Entering translated content

Now move to a piece of content. In our context, we will be using a Robot's standard greeting.

"Add translated content"

Querying Localized fields

For information in how to query the translated content, please see the developer docs related to i18n.

For more on what i18n is, visit the Internationalization concept docs.