Translatable Fields

Question:

When should I put translations in a Tastic Configuration and not in the code?

Answer:

This depends on whether you want your Frontend Manager to be able to edit these values or not.

Where you have a field type of string available in your Tastic Configuration, that's translatable by default. This means your Frontend Manager can change the translations within Backstage.

If you have content that's more static and it won't often need to be translated, for example, a button that says "OK", then this should go into the code.

We use React-Intl for this and it's where you can use the FormattedMessage component. Our DependencyInjector gives you the ability to overwrite our default App.IntlProvider, see here.


‹Back

FAQs

Still need help? Contact Us Contact Us