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

The commands update the selected environment and its .fimo/config.json. They also 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 selected environment. 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:
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 project does not need a language prefix or switcher. If you use Studio Pages, route metadata can describe a :locale segment. An optional locale leaves the default language unprefixed, while a required locale prefixes every language. See Pages. Run fimo validate after changing locale configuration or routing. For synchronization recovery, route metadata, 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.