website/Documents/ARCHITECTURE.md, branch main The site of tala.run: a Vue frontend and an ASP.NET Core API. Describe the Web Analytics exception in the architecture and runbook 2026-11-06T06:30:09+00:00 Leitwolf11 2026-11-06T06:30:09+00:00 7d1ef624fd8842acab54fce6373b4ad2bbb25eb9 The four hosts of the site now allow Cloudflare's Web Analytics beacon, but ARCHITECTURE.md and OPERATIONS.md still said the policy blocks every script an intermediary adds. Both now name the beacon, where it loads from and where it reports, and keep the forum placeholder's same-origin policy apart. 
The four hosts of the site now allow Cloudflare's Web Analytics beacon,
but ARCHITECTURE.md and OPERATIONS.md still said the policy blocks every
script an intermediary adds. Both now name the beacon, where it loads
from and where it reports, and keep the forum placeholder's same-origin
policy apart.
Check the tazel.tala.run redirect and describe it in the documents 2026-11-06T04:58:09+00:00 Leitwolf11 2026-11-06T04:58:09+00:00 1439b240a8231c5206e3c8d4f245493a076f2841 The integrity tests still expected tazel.tala.run to serve the Vue build with its own robots.txt and sitemap.xml. They now count four app-shell hosts and check the redirect itself: the two former pages go to their pages under tazel.net/docs/reference/ with the query string, other docs paths to tazel.net/docs, everything else to the same path, the /docs/ prefix is a plain one so the regular expression is reached, and HSTS stays. OPERATIONS.md and ARCHITECTURE.md list tazel.tala.run as a permanent redirect instead of a documentation site. 
The integrity tests still expected tazel.tala.run to serve the Vue build
with its own robots.txt and sitemap.xml. They now count four app-shell
hosts and check the redirect itself: the two former pages go to their
pages under tazel.net/docs/reference/ with the query string, other docs
paths to tazel.net/docs, everything else to the same path, the /docs/
prefix is a plain one so the regular expression is reached, and HSTS
stays.

OPERATIONS.md and ARCHITECTURE.md list tazel.tala.run as a permanent
redirect instead of a documentation site.
Document tala.run, the documentation hosts and the ASP.NET Core API 2026-10-15T15:03:29+00:00 Leitwolf11 2026-10-15T15:03:29+00:00 e0051b082ffce6e3cf066433980539c330d32181 - README, Architecture and Operations describe the three sites one build serves, their routes, the per-host sitemap and robots files, forum.tala.run, the permanent redirects of the former domain, and that tala.run has no ViGet host. - The backend sections describe the ASP.NET Core 10 API: how to build, test, run and publish it, its lock files, and its place on the server in current/site-api beside the legacy process of Progmaweb. - Development explains ?site=talac and ?site=tazel on a development host and lists the new test file; the release and rollback steps label current/site-api for SELinux as well. - The development server proxies /api to port 5086, the port the API uses unless PORT says otherwise. 
- README, Architecture and Operations describe the three sites one
  build serves, their routes, the per-host sitemap and robots files,
  forum.tala.run, the permanent redirects of the former domain, and that
  tala.run has no ViGet host.
- The backend sections describe the ASP.NET Core 10 API: how to build,
  test, run and publish it, its lock files, and its place on the server
  in current/site-api beside the legacy process of Progmaweb.
- Development explains ?site=talac and ?site=tazel on a development host
  and lists the new test file; the release and rollback steps label
  current/site-api for SELinux as well.
- The development server proxies /api to port 5086, the port the API
  uses unless PORT says otherwise.
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>