# Every language, edited in its own language.

> Each language of a page is listed on its own, so your client picks the German one and edits German. Details the languages share, like a phone number, update everywhere at once.

## Why translated sites stay correct.

- **One entry per language:** The client is never editing a language they do not speak by accident.
- **Shared facts update once:** A phone number, an address or a brand name is one fact, not a translation. Change it and every language gets it.
- **Both project shapes work:** A folder per language, or a locale route with shared translation catalogs such as next-intl or Nuxt i18n.
- **It names what it reached:** When a shared value updates several languages at once, the editor says which ones it touched.

## From one language to all of them.

1. **Mapping finds the languages** Connecting a translated site produces one entry per language of each page.
2. **The client picks a language** The switcher names them, so the German page is unmistakably the German one.
3. **They edit that language** Translated wording stays in its own language, one language at a time.
4. **Shared values fan out** A value the languages hold identically updates in all of them together.

## Use cases

- **A bilingual local business:** A site in two languages where only the copy differs between them.
  > Changing the phone number updates both languages at once. Changing the tagline updates only the language being edited.
- **A next-intl or Nuxt i18n project:** Shared translation catalogs under a locale route map the same way a folder per language does.
- **A client who speaks one of the languages:** They edit the one they speak with confidence, and send the other to you.
- **Keeping contact details in sync:** The detail most likely to change is also the one most likely to be forgotten in the second language.

## FAQ

### How do I stop a client editing the wrong language?

Each language is a separate entry in the page list, named by language, so the client chooses before they type. Translated wording is only ever edited one language at a time.

### Which localization setups are supported?

Both common shapes: a folder per language, and a locale route with shared translation catalogs, including next-intl and Nuxt i18n.

### What about a phone number that appears in every language?

It is treated as one fact rather than a translation. Editing it updates every language at once, and the editor names the languages it reached.

### Will it translate the copy for the client?

No. It edits the text that is on the page, in the language that text is written in. Translation stays a human decision.

---

- [All features](https://cmsbrew.com/features)
- [Chat editing](https://cmsbrew.com/features/chat-editing)
- [Connect and map](https://cmsbrew.com/features/connect-and-map)
- [Guards](https://cmsbrew.com/features/guards)