Skip to main content
Locales define the languages available for labels and localized content. Your application still decides how language appears in its URLs and how visitors switch languages.

​
Manage languages

In a linked site, use these commands instead of editing i18n.defaultLocale or i18n.locales directly. They update the selected Branch’s .fimo/config.json and keep the matching local branch synchronized when it is safe to fast-forward.
Removing a locale permanently deletes its localized entries and labels in the current Branch. Set another language as the default before removing the current default.
You can make the same changes in Settings → Languages in Studio. A new language starts empty. Changing the default does not translate or copy existing content.

​
Add translated values

Write labels and content for each language:
Each document can have one entry per locale. Creating the same variant again returns a 409 conflict and preserves the existing translation. Read or update it instead:
Fields that should remain identical in every language, such as a SKU or price, can be marked as shared in the schema. Ask your coding agent to load the fimo-code content reference before changing that setting on existing content.

​
Connect locale URLs

Fimo does not create application routes. Your application resolves the locale from its route or another application-owned setting, then passes it to the Fimo adapter. New React Router, Astro, and SvelteKit projects include a locale-ready boundary. New Next.js projects start with an ordinary root route, so you add a locale route only when the site needs one. A single-language site does not need a language prefix or switcher. Run fimo validate after changing locale configuration or routing. For synchronization recovery and every locale option, see the CLI reference.

​
What’s next

Labels

Translate interface copy.

Content

Create localized entries.

Frameworks

Connect locale resolution to Fimo.