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

UI strings and i18n

UI strings are separate from product content translations. Product content is written by operators for tours, tiles, and events. Application copy, including buttons, navigation, and errors, is maintained as product interface text.

How interface copy behaves​

Scoutello keeps interface copy organized by surface, such as shared navigation, dashboard labels, guest-app labels, and marketing pages. This keeps each experience focused on the text it needs.

If an interface string is missing, the issue should be visible during review so the copy can be fixed before it reaches guests or operators.

Copy groups​

Copy groups keep language work focused:

  • Shared fundamentals reused everywhere.
  • Dashboard-specific copy.
  • Guest-app-specific copy.
  • Marketing or landing-specific bundles where split packaging helps performance.

Adding or changing copy​

New interface copy should use stable translation keys and neutral wording. Engineering details for adding keys live in internal onboarding; public documentation should describe the expected copy outcome.

Guidelines teams follow internally:

  • Avoid constructing keys dynamically—static analysis needs to see literal keys.
  • Prefer interpolation placeholders instead of concatenating translated fragments.
  • Keep gender-neutral wording.
  • For German copy, avoid informal direct address so tone stays neutral across audiences.

Workspace automation keeps locale bundles aligned after copy changes.

UI copy versus product content​

  • Operator-authored values guests read on a published page → product translation workflow.
  • Labels belonging to the application itself → UI string workflow.
  • Mixed sentences should keep fixed grammar in UI translations and pass authored names or numbers as variables.

Related concepts: How translations work, Automatic translation, Languages and localization.