Translations

There are two types of translations in Directus: Data Studio translations and content translations.

Data Studio Translations

Data Studio translations are used to translate the user interface of the Data Studio. The application supports internationalization across the entire App. Many languages are currently supported, with more being added all the time. Anyone can add or refine any languages through our locales project.

Releasing New Translations

As soon as a translation is edited on our translation platform, a pull request is created in our repository, which contains the corresponding changes. This pull request is usually included in the subsequent release of Directus.

Translation Strings

Any strings can be translated in the Data Studio through the decicated translation strings section of the settings module. Each entry in the translation strings has a key that is used in the data studio, and any number of translations.

Throughout the Data Studio, click the icon to assign a translation string to the field's value. The correct translation will now be shown based on the user language preference. If a language is chosen for which there is no translation string, the translation key will be displayed instead.

Content Translations

Content translations are used to translate the content of the database, which can be served via API to your external applications. The built-in translations interface handles much of the complexity in managing your data model for multilingual content.

The languages collection will be automatically created when you add your first translations field. It contains each language you support, with a code and direction field (some languages are written right-to-left).

The field will also create a new collection-specific collection for translated content, for example articles_translations. Add fields you wish to translate to this collection, and they will be displayed in the translations interface.