tala.run, talac.tala.run and tazel.tala.run now each open on a landing page
of their own. talac.tala.run and tazel.tala.run used to redirect "/" to
their first documentation topic. Every landing page has one headline, two
ways in, a "Why Tala?", "Why Talac?" or "Why Tazel?" section of tabs over
one code panel, and a short row of next links. The tabs follow the ARIA
tabs pattern: arrow keys, Home and End move between them. The code panel
stays left to right on the Hebrew pages and has a copy button.

Every sample is something that works today. The Tala tabs show
HelloWorld and PrimeNumbers, which are copies of Examples/ (a test compares
them), a small program that shows an argument evaluated by need, the
LLVM IR that talac -O2 made of the gcd loop of Examples/GCD, and a Tazel
project file. The Talac tabs show the terminal output of talac 0.6.0 for
one command, --emit=metadata, each --emit stage, the optimized IR and a
type error. The Tazel tabs show the project file, the everyday commands,
target selection, lock graph and a did-you-mean hint. Of the fifteen
programs in Examples/, talac 0.6.0 builds four (HelloWorld, GCD,
PrimeNumbers, CollatzTrace), so the classes, generators and pattern
matching of the others are not shown yet.

The old home page said in nearly every paragraph that the work was
unfinished, linked "Why Tala?" three times, and numbered its sections. It
is gone. The state of the project is said once, as a small badge beside
the name in the header. The header no longer repeats a Home link, since
the name leads home. On talac and tazel it lists their documentation
topics. Styles that only the old home page used are removed.

The titles and descriptions of "/" come from the landing content of each
site, and the talac and tazel sitemaps list "/". The tests follow:
siteHome is "/" everywhere, the tazel canonical path is "/", and the
example comparison reads the landing samples.

Document the lock commands and hints of Tazel

Progmasoft/tala#86 added tazel lock create-dump --path, tazel lock graph,
tazel viget vipkg-desc and did-you-mean hints. The Tazel commands page now
covers them in all four languages:

- The command list names create-dump with [--path File] and says that the
  folder has to exist. It adds lock graph, and it lists viget vipkg-desc
  among the commands that wait for ViGet.
- A new section explains lock graph and its options, with a code example.
  --invert reads Publisher.Name, a path ending in .vipkg, or a project.name.
- A short section shows the hint a mistyped word gets.
- The Hebrew text keeps its direction marks before options and Latin names.

Name the hosts the compiler workflows test

Progmasoft/tala#90 reduced the compiler's CI to Windows Server 2025, Ubuntu
26.04 LTS and macOS 26 on Apple silicon. Its documents now call those the
official hosts. The Getting Started page still listed macOS Sequoia and Fedora
43, so its two host sentences, in all four languages, now name Windows 10/11,
macOS 26 Tahoe on Apple silicon and Ubuntu 26.04 LTS, and the Linux sentence
speaks of Ubuntu alone.

Write the compiler's name as Talac in prose

Describe the libc++ toolchain of the Linux hosts

The site wrote the compiler as talac wherever it named it: the brand and
the sibling link of talac.tala.run, the page titles, descriptions and
leads of its documentation, and the Tazel pages that say which program
Tazel starts. As a name it is now Talac, like Tazel, in all four
languages. What a reader types stays lowercase: the command lines, the
`talac --help` the guide asks for, and the host talac.tala.run.

The site test that reads the German title of the outputs page expects
the new name.

The compiler now builds with libc++ on Ubuntu and Fedora and links LLVM
built with libc++, which the developer helper of the compiler repository
downloads. The getting-started guide still said that the LLVM
development packages of the distribution are used; in all four languages
it now says that Clang, LLD and libc++ come from the distribution and
that the helper downloads LLVM built with libc++.