The panel now speaks your language, and where it still does not
Every screen behind the login is now in Polish and German as well as English - dashboards, jobs, billing, monitoring, partner pages, dialogs and error screens. Here is what that took, and the two places English deliberately remains.
Die Artikel sind auf Englisch geschrieben.
Selling accessibility in a language somebody does not read is a contradiction. Our public site has been in English, German and Polish for months, but the moment a customer signed in, the panel switched to English and stayed there: every button, every status, every confirmation dialog. That is fixed. The whole interface behind the login now reads in the visitor's language.
What changed
Twenty-eight portal screens, the shell around them and the components they share: the dashboard, the request wizard, job detail with its quotes and approvals, billing and invoices, reports, monitoring, your sites, automation, courses, the help centre, the developer API and the partner pages. Statuses, priorities and SLA times come from the same catalogue, so a ticket that is waiting on you says so in your language everywhere it appears, not only where somebody remembered to translate it.
Dates follow the reader too. An invoice dated in the American convention on a Polish page is a small thing that quietly says the product was not built for you.
The bug underneath it
Localised routes carry the language in the address, so the public pages always knew which one to use. The panel does not live under those routes, so it never received a language at all and silently fell back to English - the login screen included, which meant picking Polish on the home page and then signing in put you back in English within one click. The panel now reads the language you chose from a cookie, which is why the auth screens changed language the day this shipped.
Where it is still English, and why we say so
Two things inside the panel are still English: course lessons and help-centre articles. That is content, not interface - translating it well is editorial work, not a code change, and we would rather list it as a known limitation than ship a machine translation of our own documentation. Our accessibility statement names both, with a date. Blog articles are the same story: they are written in English and served on the German and Polish addresses, so their text is now marked as English in the markup, and the page says so before you start reading. A screen reader switches voice instead of reading English words with Polish phonetics.
The admin console stays in English on purpose. One team, one language, and nobody outside the company sees it.