From TFA: > Note: In addition, the text of the UI components and header menu will be in English only, going forward. They will not be translated, at least not

From TFA: > Note: In addition, the text of the UI components and header menu will be in English only, going forward. They will not be translated, at least not initially. But that's the easiest part! I understand the part about translations becoming stale, and how it's hard to manage, but honestly, translating a UI isn't that hard. I think a good recipe to get better translations is: - Don't treat it as an aftertought. Co-locate the en-US assets with the translated versions, that way your contributors actually see that there are other languages to support. Each page on the MDN website should be a folder containing a file for each language. - If a translation is out-of-date, link to these more recent languages, and offer an auto-translated version in the meantime. Importantly, let the user switch between the automatic translation and the manual one. Also, make it obvious how they can contribute.