Care a lot about accessibility as a web design principle. On this blog, thought through keyboard navigation and screen reader support for blind users
Shared a similar thought on duplicating content when starting my Telegram blog
Going multilingual extends the same principle
Translating into every language is hard. Picked widely spoken ones, plus languages where friends can help catch nuances:
- Russian as my native language
- English as the international language
- Spanish and Portuguese, learning both bit by bit
- French, from school days
- and German!
- it’s just interesting to see the differences
I know absolutely nothing about Asian languages. After studying the nuances of CJK, I decided not to risk translating without an editor. Next-gen AI models will probably make it possible to translate into them too — after all, I want the whole world
Browser translators are a bit weak, and without a translation, a text has a hard time crossing the boundaries of its language bubble
If a post isn’t translated yet, the site falls back to an available language
Translation methodology
I put a lot of time into the original and aim for comparable quality in translation
A long prompt translates the text in chunks and explains the differences between phrasing options. I read closely and choose, then pass it to another AI — and so on in a loop, minimizing inaccuracies
Facts and names are localized [in not-yet-published articles]
Most drafts start in Russian before getting translated, though I’m writing a new piece on design straight in English
I edit the English version myself; the others get a lighter touch since my grasp of them is weaker