Languages

Global fallback languages

Administrators can configure global fallback languages in CMS, enhancing multi-language support for CMS (SaaS) and Optimizely CMS (PaaS) and Optimizely Graph implementations.

• Administrators can set global fallback languages.
• Search analysis is performed on the authored language rather than the requested language.
• Graph Queries return the best-fit language based on fallback settings.

Global fallback language configuration in admin UI

Administrators can configure global fallback languages directly within CMS Admin UI's languages section.

• Administrators can set a single fallback language for each language.
• Implemented recursive evaluation of fallback languages (for example, fr-BE falls back to nl-BE, which falls back to nl).
• Applying global fallback settings has the same effect as applying current language settings on the root node.
• Provided user notifications and an option to apply changes after updating fallback settings, which updates the root node with default language settings.
• Triggered re-indexing of affected content to Optimizely Graph when root node language settings are updated and Optimizely Graph is enabled.
• Content nodes applying global fallback settings are aware of their configuration for re-indexing and UI visualization.
• Validation prevents circular fallback loops.
• Cleared fallback references when a language is removed.

Fallback language variant indexing for Optimizely Graph

You can create fallback language variants in Optimizely Graph integration, ensuring comprehensive language management for published and deleted content.

• Ensured that when a content instance is published or moved, the instance and its fallback language variants are indexed to Optimizely Graph.
• You can delete content instances and their associated fallback language variants from Optimizely Graph upon content deletion. New fallback versions are subsequently indexed where applicable.
• Fallback version indexing sets the locale to the content instance's locale and fallbackVersionFor to the locale of the non-available language it replaces.
• When updating an existing fallback version in Graph, the new version is indexed before the old one is deleted to prevent temporary data loss.
• Applied this logic consistently when running a synchronization from the admin UI.

Global language context switching for content creators

Content creators can change the global language context in CMS (SaaS) so users can work in their preferred language. The UI dynamically adjusts to reflect content availability and creation permissions for the selected language.

• If a content creator switches to an available language, the UI displays which pages and other content exist in that language versus only in other languages.
• If a content creator switches to an available language that is not enabled for a specific content item, the UI prevents the creation of content in that language.
• The language selection dropdown includes search functionality and a scrollbar, improving usability when more than 10 languages are available.

Enhanced multi-language content translation

Added enhanced multi-language content translation capabilities for content creators in CMS (SaaS), improving the efficiency of content localization.

• When you create a content item in an enabled language, content creators can now duplicate the source content, including all structures and layouts.
• Users can select the specific language version to use as the source for translation or duplication.
• You can copy only the content structure (such as content area blocks for pages, layout for experiences) while stripping out actual content values.
• Content creators can choose to auto-translate content. This preserves the content structure while machine-translating the content itself. Optimizely provides a translation engine to translate content only upon explicit user request.
• You can export translatable content in a human-readable format, such as JSON, for use with external translation providers. This export respects Visual Builder and other content structures.

Enhanced content translation initiation and language management

Added enhanced capabilities for initiating content translation and managing language contexts, streamlining the localization workflow for content creators.

Translation initiation

You can initiate content translation from multiple points, all opening the Translate Content dialog box:

• From the context menu for items in the Page tree.
• From the toolbar's yellow ribbon, when a language branch is missing.
• By clicking an untranslated language in the Language Selector in the toolbar.
• The Translate menu option is disabled when content exists for all languages.

Translate Content dialog box

You can copy content into a new language branch. The dialog box lists source and target languages by name, sorted with the master language at the top. Source and target languages are preselected when initiated from the toolbar or Language Selector, but you can change them. You can create an empty copy by selecting None, while selecting a language as the source copies all its content.

Post-Translation Context

After performing a translation, the system automatically switches the context to the new language and loads the newly created content.

Redesigned Language Selector

The Language Selector in the toolbar was redesigned to display all available languages, split into two sections: languages with existing branches and those without. Clicking an existing language loads its content and switches the context, while clicking an untranslated language opens the Translate Content dialog box. The current language branch is indicated with a checkmark, and the section for adding new languages is hidden once you create all language branches.

Auto-translation for language variants

📘

Note

This feature is controlled by a feature flag, which is off by default.

You can automatically create language variants so content creators can machine translate content while preserving its original structure.

• When creating a language variant, content creators can auto-translate content from the source language. The auto-translation process preserves the content's structure (page hierarchies, content areas, and blocks) while machine-translating the textual content.
• Upon completion, the editing context automatically switches to the target language, displaying the newly translated content.
• Errors encountered during the external machine translation process prevent the creation of the language version, and these errors are displayed in the translation dialog.

Auto-translate content in draft state

You can translate draft content, including pages, blocks, and experiences, without requiring prior publication. Content creators can work on translations and collaborate on multiple language versions before publishing.

Draft pages, blocks, and experiences can be translated into a target language, including any associated draft content references.