Skip to content

Add additional context to the admin locales and translations page #2717

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 22, 2025
Merged

Add additional context to the admin locales and translations page #2717

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
09d915f
Add context for admin locales and translations
pwizla Sep 22, 2025
fe3de40
Formatting
pwizla Sep 22, 2025
1079370
Formatting
pwizla Sep 22, 2025
e61ecf9
Formatting
pwizla Sep 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions docusaurus/docs/cms/admin-panel-customization/locales-translations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,17 @@ tags:

# Locales & translations

Strapi's [admin panel](/cms/admin-panel-customization) always ships with English translations, but can display additional languages. You can also override any text that appears in the interface.
The present page shows how to define your own locales and extend Strapi or plugin translations from the project codebase.
<Tldr>
Configure the admin panel languages by updating the `config.locales` array and override default or plugin strings with `config.translations` or custom translation files.
</Tldr>

The Strapi [admin panel](/cms/admin-panel-customization) ships with English strings and supports adding other locales so your editorial team can work in their preferred language. Locales determine which languages appear in the interface, while translations provide the text displayed for each key in a locale.

This guide targets project maintainers customizing the admin experience from the application codebase. All examples modify the configuration exported from `/src/admin/app`file, which Strapi loads when the admin panel builds. You'll learn how to declare additional locales and how to extend Strapi or plugin translations when a locale is missing strings.

## Defining locales

To update the list of available locales in the admin panel, use the `config.locales` array:
To update the list of available locales in the admin panel, set the `config.locales` array in `src/admin/app` file:

<Tabs groupId="js-ts">
<TabItem value="js" label="JavaScript">
Expand Down Expand Up @@ -57,7 +62,7 @@ export default {

Translation key/value pairs are declared in `@strapi/admin/admin/src/translations/[language-name].json` files.

These keys can be extended through the `config.translations` key:
These keys can be extended through the `config.translations` key in `src/admin/app` file:

<Tabs groupId="js-ts">
<TabItem value="js" label="JavaScript">
Expand Down Expand Up @@ -151,4 +156,4 @@ export default {
</TabItem>
</Tabs>

If more translations files should be added, place them in the `/src/admin/extensions/translations` folder.
If you need to ship additional translation JSON files—for example to organize large overrides or to support a locale not bundled with Strapi—place them in the `/src/admin/extensions/translations` folder and ensure the locale code is listed in `config.locales`.