Portail in Russian, with its own web addresses
The landing page, the model pages, the comparisons and the feature pages now exist in Russian at their own addresses, such as portail.cc/ru and portail.cc/ru/compare. Before this, the Russian text only appeared after the page loaded, so Russian-language search could not find any of it. Now the page arrives in Russian from the first byte, with a Russian title, description and FAQ, and search engines are told which version belongs to which language. The EN and RU switch on these pages now moves between the two addresses, so what you see, the link you copy and the page you share always match. Choosing a Russian page also remembers Russian for the rest of the site. Nothing changes for the chat itself, and English addresses work exactly as before.
501 words
Russian pages at /ru for the landing page, models, comparisons and features.
The EN/RU switch on those pages changes the address, so shared links open in the right language.
Russian titles, descriptions and FAQ for search engines.
Portail v2.8.10 shipped on 2026-11-01 as a patch release focused on portail in russian, with its own web addresses. The landing page, the model pages, the comparisons and the feature pages now exist in Russian at their own addresses, such as portail.cc/ru and portail.cc/ru/compare. Before this, the Russian text only appeared after the page loaded, so Russian-language search could not find any of it. Now the page arrives in Russian from the first byte, with a Russian title, description and FAQ, and search engines are told which version belongs to which language. The EN and RU switch on these pages now moves between the two addresses, so what you see, the link you copy and the page you share always match. Choosing a Russian page also remembers Russian for the rest of the site. Nothing changes for the chat itself, and English addresses work exactly as before. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.
The main changes were direct: russian pages at /ru for the landing page, models, comparisons and features, the en/ru switch on those pages changes the address, so shared links open in the right language, and russian titles, descriptions and faq for search engines. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.
This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.8.10 moved that contract forward in its own narrow lane.
The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.
The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.