The Translation tab is where you translate an experience. It appears at the top of an experience once that experience has more than one language.
It has two views: Content for text, and Media for files. Media is covered in Using media in other languages.
The Content view
Every translatable field in the experience appears as a row, grouped by section and activity, with one column per language. The English column is read-only — that's your source. Every other column can be edited directly.
Click into a cell and type to translate it. An untranslated cell is empty and shows the English text greyed out behind it, so you can tell "not translated yet" apart from "translated to the same words".
Reading the badges
Each cell can carry one badge in its top-right corner:
Amber globe — untranslated. This cell is falling back to English.
Orange warning — out of sync. The English text has changed since this was translated, so the translation is probably out of date.
Violet pencil — custom. Someone edited this by hand, so auto-translate will leave it alone. Click it to discard the hand-written text and translate again from English.
If your organisation has auto-translate, the amber and orange badges become buttons — click one to translate that single field. See Auto-translating your content.
Finding what's left
Show: Untranslated hides every row that's already done, so you're left with the work.
Show: Only custom narrows to the fields someone has hand-edited.
Use the column controls to hide languages you're not working on — useful when an experience has more than two or three.
Click the Field header to collapse or expand all the groups at once.
Emails
Below the content rows there's an Emails section covering your post-experience email sequence. Subject lines are editable in place; bodies are shown read-only and are edited in the Email tab. See Sending post-experience emails in other languages.
Using an external translator
If a translation agency or a colleague is doing the work outside Makeshapes, use XLIFF — a standard file format that translation tools understand.
Click XLIFF, then Export .xlf, and choose a language.
Send the downloaded file to your translator.
When it comes back, click XLIFF, then Import .xlf, choose the same language, and pick the file.
You'll get a summary of how many translations were applied. Anything the translator changed is marked as custom, so a later auto-translate run won't overwrite their work.
An XLIFF file carries text only — content fields plus email subjects and bodies. Media isn't included; language versions of files are added separately.
Editing in another language outside this tab
The Translation tab is built for bulk work. If you'd rather work in one language and see the experience as you build it, use the globe in the toolbar at the top of the experience to switch your editing language. The Content, Agenda and Email tabs will then show and save that language.