Translations
Where the content of your site gets translated: the titles and descriptions of works, series, projects, pages and the rest. Not the interface — your own text.
How it works
Content is grouped by type — works, series, projects, pages — and you can see
where a translation exists and where it is still blank. You edit one field at a
time: change a line, it saves itself, move on. Deliberately not a single
two-hundred-field form with one button at the bottom.
Site language and content language are different things
Site languages are the ones your site speaks at all. You switch them on in
settings, and they are what a visitor sees in the language picker.
Content language is the language you are editing **right now**. It switches
separately, in the menu at the bottom left, under «Content language». Switch it
to English and every field you open after that shows its English version: the
title of a work, the description, the bio, the pages. Switch back and you see
the Ukrainian ones.
This is where the common misunderstanding starts: someone turns on a second
language, does not switch the content language, types English into a field and
overwrites the original title. That is why a reminder appears at the top
whenever you are editing in something other than your main language.
So the same translation can be done two ways: switch the content language and
edit work by work where the works live, or come here and go through the whole
catalogue field by field.
How much to translate
How many languages you get depends on your plan. But the number of languages
matters less than finishing one: a site where half the works have English reads
worse than a site with no English at all — in the first case the visitor sees
the holes and concludes the site is neglected.
So it is better to finish one section completely than to get halfway through all
of them.