Languages and translations
An entry has one identity across languages. Each language can have its own working and published revisions. Administrators configure available languages in Languages.
Edit a translation
- Open the entry in Content Manager.
- Select the target language.
- Fill in localized fields, such as Title and Body.
- Check any non-localized values carried into the translation before changing them.
- Save and follow review and publication for that language.
Use the same entry for translations. Creating another collection entry creates a separate item. When starting a translation with no saved revision, the editor carries over non-localized fields from the current language. Existing translations retain their own saved revision values; do not assume later edits synchronize across languages. Review each translation before publishing.
Publish deliberately
Publishing one translation does not publish all languages. Check the selected language before approval, publication, withdrawal, scheduling, or history restoration. English can remain live while French is a draft, and a new English draft can coexist with the published English revision.
Changing the default language does not translate content. If a language is missing, ask an administrator to check configuration. Removing a language does not imply erasing historical data. Existing disabled-language live content can still be withdrawn through supported unpublish behavior.
Delivery consumers must handle languages appropriately. Inspect requests in API Explorer instead of assuming automatic translation or fallback.