Mister Blocks has a full Ukrainian version, and translating it turned out to be less about code and more about tone. A surprising amount of it came down to one small word: what do you call a stud?
This post covers how the whole site, every page, every build and every printed booklet, became Ukrainian at misterblocks.com/uk, and the rules that keep the translation sounding like a real instruction book rather than a machine.
Same address, one prefix
English has no prefix and Ukrainian lives under /uk. Slugs stay the same in every language, so a page's other version is found by swapping the prefix: /builds/cars ↔ /uk/builds/cars.
That makes the rest simple:
- Every page lists its other language with
hreflang, plusx-defaultpointing to English. The sitemap repeats the full set for every URL, because Google wants every version to list all the others and itself. - As a final pass on every page, every internal link is moved into the page's language. Assets, API calls, absolute URLs and the language switcher are left alone.
- If a page doesn't exist in the other language yet, the language switch goes to that language's home page instead of a 404.
Three kinds of text
-
Interface strings are keyed by their English text, with
{placeholders}and real plural forms. Ukrainian has more of them than English: 1 деталь, 2 деталі, 5 деталей. They're handled withIntl.PluralRules. - HTML templates are translated by a list of [English, Ukrainian] pairs applied in order, longest first, so a short phrase can't eat part of a longer one. A check script fails the build if a pair no longer matches, if three Latin words in a row survive on a Ukrainian page, or if any Russian-only letter appears.
- Search pages (categories and landing pages) were written by hand for how people in Ukraine search, not translated word for word. The gallery's Ukrainian title is "Лего інструкції безкоштовно", because that's what people type.

Володимир Зеленський: 140 pieces, 17 steps. In famous people (українською).
Translating 100+ builds with Claude
Every build has a name, a tagline, piece names, colour names and dozens of step texts. That's done with Claude, in a fixed shape:
- One call translates the "head": the title, the names, the taglines, every piece and colour name, and each distinct step heading once (a voxel sculpture can have "Water shuriken" twenty times).
- The step texts go in batches of 40 in parallel, and each batch gets a glossary of the names chosen in step 1, so the shuriken is called the same thing in step 3 and step 93.
- Checks, then one write to the database.
Every call returns a strict JSON schema. If an id is missing, a {placeholder} was lost, or a Russian-only letter slipped in, the model gets up to three attempts and is told exactly what was wrong last time.
The translation stores a hash of the English it came from. If someone changes the build while it's being translated, the result is thrown away. If the English changes later, the old translation is still shown until it's redone, so a page never goes half-English.
Builds that nobody has opened in Ukrainian yet are translated on the first visit: that visitor sees English (and the page isn't indexed), and the next one gets Ukrainian.
The rules in the prompt
The system prompt is mostly about tone and vocabulary. A few of the rules:
- Readers are kids and parents building brick by brick, so write natural, warm, simple Ukrainian, the way a good instruction book reads. Never a word-for-word calque.
- Pure literary Ukrainian: no Russian words, no russisms, no surzhyk, and never the letters ы, э, ъ, ё. (Those letters are also checked by code, not just asked for.)
- Speak to the builder as one friendly "ти": "Поклади", "Постав", "З'єднай". Never the formal "Покладіть".
- Sizes keep the × and go after the noun: "2×8 brick" becomes "цеглинка 2×8".
- Real people use their standard Ukrainian spelling (Володимир Зеленський, Еліна Світоліна, Дженсен Хуанг). Characters use their official Ukrainian names when there is one. Car and product names stay in Latin letters: Porsche Mission S, DeLorean, Waymo. "LEGO" stays "LEGO", and "MOC" stays "MOC".
So what is a stud?
The first version called studs шипи. It's a real word, but it means spikes or thorns, and it isn't what kids building with LEGO say. The word families actually use is пупирки (little bumps), so every string and every stored translation was changed to пупирка, with the grammar agreed. A small change, but it's the one that made the site sound like it was written by someone who has actually built with their kid.
The same goes for the home page. The search title targets "lego ai", but the big heading on the page says it the way a kid would: "Сфотографуй Lego блоки і отримай варіанти білдів", "snap your Lego blocks and get build ideas".

Еліна Світоліна: 135 pieces, 16 steps. More sports builds (українською).
Ukrainian on paper too
The printed booklets and PDFs come in Ukrainian as well: the same headless-Edge pipeline prints /uk/builds/<name>/print to Letter and A4 PDFs, skipping builds that aren't translated yet. The offline page, the app manifest and the "install the app" bar are translated too. English pages offer the Ukrainian version in a small bar to people whose browser prefers Ukrainian, and never redirect anyone on their own.
If you read Ukrainian, try it at misterblocks.com/uk: лего інструкції, покемони, відомі люди. If you don't, the English gallery has the same builds.
Unofficial fan builds. LEGO® is a trademark of the LEGO Group, which does not sponsor or endorse this site. Characters, people and brands belong to their owners.

Top comments (0)