What this module is for
Use CMS / Languages to control which languages are active for localized content flows, which one is primary, and which SEO locale aliases should point to existing translated content.
Included units
List: active language inventory with primary-language control and remove actionSet Languages modal: chooser for adding languages into the active setSEO Locale Aliases: optional crawlable locale URL mappings such as/br-ptthat reuse content from an existing source locale
When operators usually open this module
- a new site language should be enabled for editors and translation workflows
- the primary language should be changed
- a language should be removed from the active set
- an SEO-only locale path should load content from an existing translated locale
- support needs to confirm which locales are currently enabled
Common confusion
- The page manages the active language set used by the application. It is not the same thing as the full admin language catalog or CSV import workflow.
- Removing a language from this page changes the active set. It does not delete historical language rows, translated content, or the broader language catalog.
- SEO locale aliases do not create new translations by themselves. They create public locale paths that read from an existing source locale and expose a separate search-locale value.
- If no active language set has been saved yet, the system can seed the list from the broader active catalog so operators are not starting from an empty screen.