How translations work

Scoutello separates the structure of a feature from the language variants of its text. A tour, landing page, tile, event, or PDF keeps one stable record while translatable fields point to reusable translation entries managed by the platform.

That model lets teams author once and serve guests in many languages without duplicating entire experiences.

Content storage

Translatable product content is stored as language-specific rows linked to their parent object. Each row carries:

• The locale code.
• The text value (when present).
• Source metadata distinguishing manual authoring from generated translations.
• Optional audio attachments where narration ships beside copy.
• A flag indicating translation automation should skip the row when it must remain verbatim.

Related locales reference one another so Scoutello can treat them as a translation family for that paragraph or headline.

Authoring flow

Dashboard saves funnel translated fields through validated authoring helpers so blank noise is trimmed, duplicates collapse predictably, and new locales attach without breaking existing relationships.

The authoring flow is straightforward: save copy in the working language, optionally trigger automatic translation, then review variants before publishing broadly.

Runtime localization

Downstream experiences typically receive resolved strings—for example a single title or description field for the requested locale—rather than raw collections of every translation row.

Resolution prefers the guest's requested language, falls back through configured equivalents (organization defaults, shared locale aliases, then broadly understood defaults), and respects do-not-translate markers.

Guest language selection

Guest-facing surfaces choose a locale from routing parameters, headers, saved preferences, or contextual defaults. Servers return localized fields so clients render ordinary strings without bespoke fallback stacks.

Operational expectations

• Include every locale you intend to market before launch-critical moments.
• Treat automatic translations as draft-quality until a fluent reviewer approves them for high-trust surfaces.
• Keep UI chrome copy separate from authored marketing copy—the former ships as keyed translations, the latter lives with the tour, tile, or document itself.

Related concepts: Automatic translation, UI strings and i18n, Languages and localization.