Translating navigation, shared content, and collections

Documentation / Languages and translations

Multilingual navigation uses the same structural page identities with localized labels and destinations. The root file still owns order and nesting. Translating a page does not create a second independent navigation tree.

Translate page labels

Select the target content language and review the translated navigation title and page title. The public navigation resolves labels from page metadata and translated pages. Do not copy translated labels or availability into root-file page entries.

Internal navigation can use a translated destination when one exists. If it does not, some navigation links retain their source-language destination. Review those links as a visitor instead of assuming every label and address changes automatically.

Include shared content

Translate the pages used for toplines, prefooters, and footers, as well as ordinary content pages. A translated article with a source-language footer may be technically reachable but still incomplete for its audience.

Template content and page content have separate editing boundaries. Check the rendered result for shared text rather than assuming a translated page has translated every locked area of its template. Provider widgets and text inside images also require separate attention.

Localize collections

With a secondary content language selected, collection settings allow localized names and base paths. Translate the item pages separately. Blog and tree listings filter items for the current language; they do not automatically fill the list with source-language items.

Validate the reading route

Start at the translated homepage, follow the menu into a collection, open an item, and inspect shared content at the bottom. Check branches, back-navigation, and external links too.

See Collections and content trees, Templates and reusable content, and Blogs.