إنتقل إلى المحتوى الرئيسي

Multilingual content

Scoutello is built for teams that serve international guests. Teams maintain a single source of truth for tour copy, event information, hospitality guides, offers, and modular tiles. Scoutello stores translated variants beside that source content and serves the best available language for each guest-facing request.

The platform uses two related translation systems:

  • Product content translations for data created in the dashboard: landing pages, tiles, tours, events, PDFs, and audio-backed tour text. Work can finish asynchronously while guests see clear progress states.
  • UI string translations for labels, buttons, empty states, validation messages, and other application chrome. Teams manage these as keyed strings grouped by locale files and namespaces.

What this section covers

  • How translations work explains how authored variants link together and how guests receive a single localized field.
  • Automatic translation explains background processing, progress indicators, audio generation, and skipping translation where appropriate.
  • UI strings and i18n explains how application copy is organized and kept consistent across dashboards and guest apps.

Authoring model

Most product content starts in a dashboard form. When copy is saved, Scoutello stores language variants as structured translation rows tied to the parent record (tour, tile, landing page, event, and so on).

At runtime, guests and most dashboards receive already resolved strings for the requested locale—nested translation collections are collapsed into one field per concept (title, description, and similar) so clients do not implement bespoke fallback logic.

Responsibilities

  • Authors choose source languages, review machine translations when used, and mark content that must stay verbatim (brand names, codes, sensitive legal wording).
  • Scoutello orchestrates translation jobs, stores outputs, tracks progress, and applies configured fallbacks when a locale is partially ready.
  • Implementation teams follow internal engineering conventions so new fields participate in localization consistently—those conventions live outside this public documentation.

Related concepts: Languages and localization, Landing pages and tiles, Tours multilingual audio.