Working with Locales

As a Frontend Manager, there's two different ways that you can manage different languages for your sites but these will have been decided when your Project was set up. 

Firstly, you can have multiple Projects set up, each one with their own language. This means that you'll usually have to write each language separately for each Project. Your Developers may have put some logic into the code that could minimize this but you'll need to talk to them as it varies from Customer to Customer. The Frontastic team can also set up a sync feature which means you don't have rebuild certain things for each Locale (for example Nodes or Tastics), by default everything is synced so if you don't want this to happen, please contact our support team if your Developers haven't done this already.

The other way to do this is to use a single Project with multiple languages. This way, the structure and Pages are shared across all languages, you just need to input the different translations if you're not using an automatic translation. If you want to show different Pages for different locales though, you'll need to talk to your Development team to build the overrides into your code.

You could also combine both set ups if you'd like to. Below is an example of that set up:

  • Project One = English Website (en_GB)
  • Project Two = Swiss Website (de_CHfr_CHit_CH) with the same node tree as the English website, but different Pages in three different languages
Managing Different Languages

Some copy will be automatically translated, but it's dependent on what your Development team have enabled or not. 

In certain Tastics, the Tastic Configuration will have certain fields that are translatable and it's here that you'll need to add the different copy for each language.

If you think a certain Tastic should be translatable but it isn't, talk to your Development team about adding that field to your Tastic Schema.

Let's look at an example of how you would edit text for different locales within the same Project. Here, we'll add an ALT text to an image banner Tastic that's only in the Default language, plus we'll add a caption to our image for each Locale.

Firstly, click on the image banner Tastic to open the configuration and expand the image section:

Inputting Different Languages GIF Example

Then we input the ALT title to the Default language. In this example German is the Default language (the first field) but we can still write in whichever language we like:

Inputting Different Languages GIF Example 2

By leaving all the other languages blank, this Default one will pull through to all locales.

We then input a translation for each caption:

Using Images in Backstage GIF

You can see that as you click on each, it shows you the Default for the caption before you enter the translation.

These captions will now display to your user depending on their Locale. If you remove the translation, it will revert to the Default caption. If you remove the caption altogether, it will default to empty unless a caption has been set in the Tastic Schema as it has in the example below. It will never go to an alternative language that isn't the Default:

Using Languages in Backstage Example


‹ Back to Article List

Next Article ›

Using the Master App

Still need help? Contact Us Contact Us