website/Documents/LOCALIZATION.md, branch main The site of tala.run: a Vue frontend and an ASP.NET Core API. Correct stale statements on tala.run and rename the vxs storage keys 2026-10-16T03:05:28+00:00 Leitwolf11 2026-10-16T03:05:28+00:00 3c3c9b10e1ccf218831789bcc59d488200ed12c6 An audit of the site against the compiler repository found statements that no longer hold, in all four languages: - the overview named BUILD.kts as the project definition, while Tazel reads one of five names; it now says a project file, BUILD.kts or one of four other names; - the overview and the getting-started guide named Windows and macOS as the only development hosts. Ubuntu 26.04 LTS and Fedora 43 are official hosts too, and the guide says which toolchain they use; - the getting-started guide listed the counterparts of the examples in C#, C++ and Java; the examples also have Rust ones; - the project-file page wrote build/debug/Example without the .exe a Windows build has. The talac, Tazel and syntax pages were checked against Documents/CLI.md, Documents/PROJECT_FILES.md and Spec/Language and are otherwise accurate. Of the 43 links in the repository, only the address inside the Fira Sans licence text no longer answers; that text is third-party and verbatim. The browser storage keys still carried the former name of the language: vxs-locale-choice, vxs-theme and vxs-forum-theme become tala-locale-choice, tala-theme and tala-forum-theme. A value under a former key moves to the current one on the first page load, so no visitor loses a choice; a forum test covers the move. The npm package is renamed from @visual-xsharp/website to @progmasoft/tala-website, and the forum assets get a new version query so Cloudflare serves the new script. 
An audit of the site against the compiler repository found statements
that no longer hold, in all four languages:

- the overview named BUILD.kts as the project definition, while Tazel
  reads one of five names; it now says a project file, BUILD.kts or one
  of four other names;
- the overview and the getting-started guide named Windows and macOS as
  the only development hosts. Ubuntu 26.04 LTS and Fedora 43 are official
  hosts too, and the guide says which toolchain they use;
- the getting-started guide listed the counterparts of the examples in
  C#, C++ and Java; the examples also have Rust ones;
- the project-file page wrote build/debug/Example without the .exe a
  Windows build has.

The talac, Tazel and syntax pages were checked against Documents/CLI.md,
Documents/PROJECT_FILES.md and Spec/Language and are otherwise accurate.
Of the 43 links in the repository, only the address inside the Fira Sans
licence text no longer answers; that text is third-party and verbatim.

The browser storage keys still carried the former name of the language:
vxs-locale-choice, vxs-theme and vxs-forum-theme become tala-locale-choice,
tala-theme and tala-forum-theme. A value under a former key moves to the
current one on the first page load, so no visitor loses a choice; a forum
test covers the move. The npm package is renamed from
@visual-xsharp/website to @progmasoft/tala-website, and the forum assets
get a new version query so Cloudflare serves the new script.
Call the language Tala in the API, the documents and the templates 2026-10-12T03:16:43+00:00 Leitwolf11 2026-10-12T03:16:43+00:00 1bb833c4b98f5cd7343ae7b227c0fc39ee44deca The pages were renamed; the rest of the repository still said Visual X#: - the site API answered with the name Visual X#, and its test expected it; - the documents, the issue and pull request templates, the support address and the name of the code scanning configuration. The documents also said that a left-to-right mark follows the name of the language in Hebrew text. That was for the `#` of the old name; the sentence now speaks of names that end in a symbol, such as C#. Not changed: host names, paths and unit names on the server, the name of the backend artifact, the Kotlin package of the backend, and the keys of the browser storage. 
The pages were renamed; the rest of the repository still said Visual X#:
- the site API answered with the name Visual X#, and its test expected it;
- the documents, the issue and pull request templates, the support address
  and the name of the code scanning configuration.

The documents also said that a left-to-right mark follows the name of the
language in Hebrew text. That was for the `#` of the old name; the sentence
now speaks of names that end in a symbol, such as C#.

Not changed: host names, paths and unit names on the server, the name of the
backend artifact, the Kotlin package of the backend, and the keys of the
browser storage.
Bring the documentation up to the published site and fill its gaps 2026-10-03T15:21:43+00:00 Leitwolf11 2026-10-03T15:21:43+00:00 8738fc4e138745f2d065cf54c25426e3d37c119d The documents still described a site in maintenance with two languages and a forum page with a language menu. They now describe what is published, and three documents are new. New, under Documents/: - README.md: index of the documentation. - ARCHITECTURE.md: the frontend, the backend and the forum page, what each serves, what the site deliberately does not contain, and how search engines and crawlers are treated. - LOCALIZATION.md: the four languages, how a page picks one, what counts as a visitor's choice, how Hebrew text is laid out, where the text lives and how to add a language. - DEVELOPMENT.md: requirements, the commands of each part, the dependency locks and checksums, the tests and what CI enforces. Updated: - README.md: the site is public; four languages and the browser-language default; a documentation section; the Dokka gate. - CONTENT.md: the forum notice without a language menu; translation rules for four languages, including preferring the term a reader would use over a literal one; the crawler rules as an owner decision. - OPERATIONS.md: the live route table; the release steps for the directory layout on the server, with the SELinux labelling order that caused an outage once; cache keys for the forum files and CDN caching; maintenance mode as a fallback instead of the current state; rollback by directory; checksum regeneration with --refresh-dependencies; the post-release check for four languages and right-to-left text. No source file changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 
The documents still described a site in maintenance with two languages and
a forum page with a language menu. They now describe what is published, and
three documents are new.

New, under Documents/:
- README.md: index of the documentation.
- ARCHITECTURE.md: the frontend, the backend and the forum page, what each
  serves, what the site deliberately does not contain, and how search
  engines and crawlers are treated.
- LOCALIZATION.md: the four languages, how a page picks one, what counts as
  a visitor's choice, how Hebrew text is laid out, where the text lives and
  how to add a language.
- DEVELOPMENT.md: requirements, the commands of each part, the dependency
  locks and checksums, the tests and what CI enforces.

Updated:
- README.md: the site is public; four languages and the browser-language
  default; a documentation section; the Dokka gate.
- CONTENT.md: the forum notice without a language menu; translation rules
  for four languages, including preferring the term a reader would use over
  a literal one; the crawler rules as an owner decision.
- OPERATIONS.md: the live route table; the release steps for the directory
  layout on the server, with the SELinux labelling order that caused an
  outage once; cache keys for the forum files and CDN caching; maintenance
  mode as a fallback instead of the current state; rollback by directory;
  checksum regeneration with --refresh-dependencies; the post-release check
  for four languages and right-to-left text.

No source file changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>