/ /

Landing pages tile translations

Updated 4 days ago

Overview

Translations for static strings are carried out by Crowdin whereas for customer entered strings are done by the available providers. We are now supporting translations for landing pages and sections title and descriptions. 

Translations for tiles will be covered in the near future.

Landing pages support translation for the following fields:

  • Landing page title

  • Landing page description 

  • Section title

  • Section description

Each field has its own translation icon. Clicking it opens the Manage Translations modal for that specific field where translations can be managed per language.

Source Language

The source language is the language in which the field was originally authored. It is set to the creator's profile language at the time the landing page or section is created/ edited. 

  • Landing page title and description share the same source language  changing it for one changes it for the other.

  • The source language is editable at any time from the Manage Translations modal via the pencil icon next to the source field.
    lp translate.png

  • Section heading and section description share the same source language changing it for one changes it for the other.

  • The source language is editable at any time from the Manage Translations modal via the pencil icon next to the source field.
    lpt.png

  • When translations settings are ON then all existing manual translations will be removed and regenerated automatically when source language is changed. 

  • When translations settings are OFF then all existing manual translations will stay intact when source language is changed. 

Source Language Change

When the source language is changed, a confirmation modal appears before the change is applied. The modal text varies depending on whether auto translation is ON or OFF:

When auto is ON:
"You are changing the main language from [Language] to [Language]. The source language for both [field names] will be updated to [Language]. All existing manual translations will be removed and regenerated automatically."
lpt1.png

When auto is OFF:
"You are changing the main language from [Language] to [Language]. The source language for both [field names] will be updated to [Language]. All existing manual translations will be preserved and remain unchanged."
lpt2.png

Translation States

Each language for each field can be in one of three states:

State

What it means

AUTO

System-generated. Always in sync with source content. Not editable unless manual translation is turned on.

MANUAL

User-authored. Takes precedence over auto. The system will never overwrite it.

OUTDATED

Was manual, but the source content changed after it was saved. May no longer be in sync.

When Auto Translation is ON

  • Auto translations are generated for all enabled languages when a field is saved or updated.

  • Each language row is pre-filled with the auto-translated value  not editable unless the manual translation toggle is turned on for that language.

  • Turning on the manual translation toggle for a language copies the current auto-translated value into an editable field. The user can edit it freely.

  • Manual translation takes precedence over auto for that language.

  • Clicking Reset to automatic translation removes the manual override and restores the auto translation for that language.

  • If source content is edited, auto translations regenerate automatically. Manual translations are never touched but are marked as outdated; users must update them or keep as is.
    lpt3.png

When Auto Translation is OFF

  • No auto translations are generated.

  • Each language shows a blank editable field  the user enters translations manually for every language they want to support.

  • If auto translation was previously ON and then turned OFF, the existing auto translations at the time of turning off are preserved and carried over into the manual fields — they are not wiped.

  • If a landing page is created when auto translation is already OFF, all language fields start blank.
    lpt4.png

Outdated Translations

Manual translations become OUTDATED when the source content of a field is edited after manual translations have already been saved.

What happens:

  • An inline warning appears below the edited field immediately:

    • For landing page title: "One or more manual translations may be outdated because you changed the title. Review and update as needed."

    • For landing page description: "One or more manual translations may be outdated because you changed the description. Review and update as needed."

    • For section heading: "One or more manual translations may be outdated because you changed the title. Review and update as needed."

    • For section description: "One or more manual translations may be outdated because you changed the description. Review and update as needed."

  • The warning is shown with an icon and does not block saving.

  • Inside the Manage Translations modal, an "Outdated translations" indicator appears below each language that has an outdated manual translation.
    lp translate 1.png

How the warning clears:

  • Once the user opens the Manage Translations modal, makes any update (even just one language), and clicks Save — the inline warning disappears and the outdated indicators clear for all languages, not just the one updated.

  • After save, the system treats all translations as finalised. It does not re-flag languages that were not actually updated. The user is responsible for revisiting any languages that still need updating.

Important: Outdated manual translations are still served to users they are not suppressed or replaced by the source language value.

Key Rules to Remember

  • Auto translations always regenerate when source content changes and they are never OUTDATED.

  • Manual translations are never overwritten by the system ever.

  • Saving the Manage Translations modal finalises all translations. The system does not re-flag stale languages after save.

  • Source language is shared within a field pair (title + description share one; section heading + section description share one).

  • Users always see the source language as fallback and never a blank field.


Was this article helpful?
Subscribe to receive updates on this article