CMS interface language versus website content language

Documentation / Languages and translations

The admin header has two language selectors because the interface and the website content are independent. Changing menu language should not be mistaken for creating or editing a page translation.

Control panel language

Control panel language changes CMS labels, menus, and messages. The current interface configuration supports English and French. The selection navigates the admin with the selected locale and persists an admin preference.

This choice does not rewrite page titles, body text, summaries, or public URLs. An editor can use an English control panel while editing French content.

Content language

Content language selects which configured website language you are managing. It is derived from the site's language configuration and is carried into relevant admin views. Secondary-language views identify the selected content language separately from the control-panel locale.

Before editing, confirm the website, page identity, and content language. This is especially important when translated versions have similar titles or different slugs. A page's language controls show whether the target translation exists and offer creation or retranslation actions where supported.

Changing the content selector does not itself translate the page. It selects a version or context; translation creation is a separate action that can require a configured provider.

Validate the distinction

Change the control-panel language and confirm that the page content remains unchanged. Then select a known secondary content language and confirm the page version and URL shown by the admin. After saving an edit, reload that version and inspect its public page.

If the intended translation is missing, create it rather than editing the source in place. See Agentic editing and connections for the same site, page, and language checks when using an assistant.