The Honest Answer to What Languages This Site Works In

When somebody asks whether a site is available in Spanish, they might mean two things. Can I read the menus and the lessons in Spanish? Or can I study Spanish-language material here? A single answer to both is almost always wrong, and the wrong half is usually the one that matters to the person asking.

The language-support page answers them separately. The interface and every written lesson are English. Study material can be built from any of the Wikipedia language editions the search supports, which is a considerably longer list.

• Menus, help articles, tutorials, blog posts and policy pages are English.
• Every authored lesson, including the aptitude skill lessons and the coding course, is English.
• Assessment items and their explanations are English.
• There is no language switcher, because there is nothing behind one yet.

Open the search, choose a Wikipedia language edition, and the topic you open is in that language. The study material built from it carries the source's language, because the pipeline is extractive: claims are the source's own sentences, so a French article produces French claims. The dictionary follows the same rule, reading the Wiktionary edition you pick.

This is a genuine capability rather than an accident. If you are learning a language, opening a topic you already understand in an edition you are learning is one of the more useful things the product does, and none of it required a translation layer.

The wider Novus estate has a five-locale contract. This site does not serve it. There is no localised route, nothing in the interface is translated, and the page says that in plain terms instead of advertising a switcher that would hand a reader an English page in a Spanish wrapper.

There is a cautionary history behind that bluntness elsewhere in the estate: a switcher that set a preference and reloaded, where exactly one component could respond, so every visitor who chose another language got an English page anyway. Shipping the appearance of a feature is worse than shipping nothing, because nobody files a bug against a page that merely looks translated.

One naming detail confuses people, and it is worth stating. On this site the languages route means programming languages: it is the coding hub, with a written course and citation-index paths beneath it, and it has been indexed under that meaning for months. The language-support page therefore lives at its own address rather than taking a URL that already meant something else.

Taking it would have broken a real content section to gain consistency in a slug while destroying consistency in the meaning, which is the wrong trade in both directions.

Open a topic you already know well in a language you are learning. Because the pipeline is extractive rather than generative, the claims, the flashcards and the quiz are all built from the source article's own sentences, which means you are reading real published prose in that language rather than material written for learners. That is a different and harder exercise than a graded reader, and it is the right one once the grammar has stopped being the obstacle.

Two practical notes. The size and quality of a Wikipedia edition varies enormously between languages, so a topic that produces a rich study space in one edition can produce a thin one in another, and the page will tell you its coverage state rather than filling the gap. And the interface around that material stays English, so you get English navigation wrapped around source-language content, which is a slightly odd combination and an honest one.

The dictionary behaves the same way and is worth using alongside rather than afterwards. Looking a word up while you are reading the sentence it appeared in fixes it far better than a vocabulary list does, and the define-on-tap popover exists so that lookup does not cost you the place you had reached. If a word turns out to be worth studying properly, the same popover opens it as a topic of its own.

• Pick a topic you could already summarise from memory in your first language.
• Read the claim list before the article: short sentences, each independently checkable.
• Use the dictionary popover on the words you do not know rather than switching tabs.
• Export the flashcards, which carry the source language with them.

Tell us. A request for a specific locale, from somebody who would actually use it, is worth more than a general intention to internationalise, and the contact page is a short route to a real person.