Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
path: root/README.md
diff options
context:
space:
mode:
authorLeitwolf2026-11-13 20:24:46 +0300
committerGitHub2026-11-13 20:24:46 +0300
commit98d8dbb62b3e22d7067936a94f48ff7e29a28563 (patch)
treea3786a21529dcb25acc1d3e45ed5b68275f4e4c1 /README.md
parent8debdb66b8fe031cb70714888a07026f450f097b (diff)
parentf9172e456d2980f32b417a3776f47f097bd7f009 (diff)
downloadwebsite-renovate/backend-packages.tar.gz
Merge branch 'main' into renovate/backend-packagesrenovate/backend-packages
Diffstat (limited to 'README.md')
-rw-r--r--README.md17
1 files changed, 12 insertions, 5 deletions
diff --git a/README.md b/README.md
index 58fdf50..cdc994c 100644
--- a/README.md
+++ b/README.md
@@ -5,8 +5,15 @@ SPDX-License-Identifier: AGPL-3.0-or-later WITH AdditionRef-Progmasoft-Patent-Gr
# Tala website
+> [!IMPORTANT]
+> The Tala language and its tools (Talac, talafmt, talalint, tala-analyzer) are no longer developed as of 2026-11-10.
+> Progmasoft puts its work into [Tazel](https://tazel.net), now a build system for C, C++, Objective-C,
+> Objective-C++ and Zig. tala.run is closed for maintenance: every page and subdomain leads to
+> `https://tala.run/unavailable?reason=maintenance` while the domain is prepared for OpenTala, a kernel, and TalaOS.
+> The site below is kept for reference.
+
This repository owns the public language website at [tala.run](https://tala.run) and the documentation of the
-compiler and the build system at [talac.tala.run](https://talac.tala.run) and [tazel.tala.run](https://tazel.tala.run).
+compiler at [talac.tala.run](https://talac.tala.run). The build system has its own site, [tazel.net](https://tazel.net).
It does not own
Progmasoft's corporate or account sites. Tala uses its own supplied purple leopard SVG identity;
the Progmasoft mark is a different brand.
@@ -19,16 +26,16 @@ One frontend build serves three sites and picks its pages from the host name:
explains the design direction, `tala.run/docs/getting-started` links the real compiler checkout and toolchain, and
`tala.run/docs/syntax` gives a first look at the syntax from the public specification.
- `talac.tala.run/docs/command-line` and `talac.tala.run/docs/outputs` document the compiler.
-- `tazel.tala.run/docs/commands` and `tazel.tala.run/docs/project-file` document the build system.
+- `tazel.tala.run` redirects permanently to [tazel.net](https://tazel.net); its two pages go to
+ `tazel.net/docs/reference/commands` and `tazel.net/docs/reference/project-file`.
- `forum.tala.run` is a standalone informational page. It is *not* a forum service; accounts and posts do not exist
there yet. It stays noindex until a real community forum is launched.
Every path of the former domain, `xsharp-lang.xyz`, redirects permanently to the same path of `tala.run`. tala.run has
no ViGet host; the registry lives at `viget.progmasoft.com`.
-The sites are public and served with `ops/nginx/tala.conf`. `ops/nginx/tala-maintenance.conf` remains in the
-repository as the configuration to fall back to when the main domain has to be taken offline. The forum page is
-deployed independently of the main site. See the [operations runbook](Documents/OPERATIONS.md) for the route and
+The sites are closed: `ops/nginx/tala.conf` and `ops/nginx/forum.conf` send every page to
+`https://tala.run/unavailable?reason=maintenance`, a page of its own (`ops/maintenance/unavailable.html`). See the [operations runbook](Documents/OPERATIONS.md) for the route and
release boundaries.
## Documentation