<feed xmlns='http://www.w3.org/2005/Atom'>
<title>website/frontend/src, branch design/docs-layout</title>
<subtitle>The site of tala.run: a Vue frontend and an ASP.NET Core API.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/'/>
<entry>
<title>Lay out the documentation like kotlinlang.org/docs</title>
<updated>2026-10-18T06:00:14+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-18T06:00:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=47ffd40c8b61aa9dd131e567bfb2ce78ec7f354c'/>
<id>47ffd40c8b61aa9dd131e567bfb2ce78ec7f354c</id>
<content type='text'>
The three documentation pages each drew their own sidebar. The two hand-built
pages listed different topics: Getting started had no link to Syntax. Each page
also opened with a capitalized section kicker.

DocShell now frames every documentation page:

- On the left, the topics of the site, with the current one marked. On a
  narrow screen they fold into a Contents button above the page.
- Above the page, a breadcrumb: site / Documentation / topic.
- The page in a column of at most 720 px.
- On the right, "On this page". It is read from the h2 headings of the
  rendered page, and each heading gets an id from its words in any script.
  It is hidden below 1100 px.
- Under the page, previous and next topic cards and an "Edit this page"
  link to the file the page is written in.

DocPage, OverviewPage and GettingStartedPage use it and drop their own
sidebars and kickers. The styles of the old layout are removed. The labels
are in all four languages.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The three documentation pages each drew their own sidebar. The two hand-built
pages listed different topics: Getting started had no link to Syntax. Each page
also opened with a capitalized section kicker.

DocShell now frames every documentation page:

- On the left, the topics of the site, with the current one marked. On a
  narrow screen they fold into a Contents button above the page.
- Above the page, a breadcrumb: site / Documentation / topic.
- The page in a column of at most 720 px.
- On the right, "On this page". It is read from the h2 headings of the
  rendered page, and each heading gets an id from its words in any script.
  It is hidden below 1100 px.
- Under the page, previous and next topic cards and an "Edit this page"
  link to the file the page is written in.

DocPage, OverviewPage and GettingStartedPage use it and drop their own
sidebars and kickers. The styles of the old layout are removed. The labels
are in all four languages.
</pre>
</div>
</content>
</entry>
<entry>
<title>Give each site a calm landing page with a "Why" section</title>
<updated>2026-10-17T22:45:32+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-17T22:45:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=43c431a793affe2fa41ead816268d6af760f72d0'/>
<id>43c431a793affe2fa41ead816268d6af760f72d0</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Document the lock commands and hints of Tazel</title>
<updated>2026-10-17T20:59:24+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-17T20:59:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=b070590df7e01963574e9efa313902c0ccfffb90'/>
<id>b070590df7e01963574e9efa313902c0ccfffb90</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Name the hosts the compiler workflows test</title>
<updated>2026-10-17T17:08:23+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-17T17:08:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=a0e7dbad88a90d3d168dc363776d79e31a6f973b'/>
<id>a0e7dbad88a90d3d168dc363776d79e31a6f973b</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'origin/main' into content/talac-name</title>
<updated>2026-10-17T08:40:11+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-17T08:40:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=828ed9f8eef15b2481178ec0c1db8da6858deb05'/>
<id>828ed9f8eef15b2481178ec0c1db8da6858deb05</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Write the compiler's name as Talac in prose</title>
<updated>2026-10-16T20:11:14+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-16T20:11:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=ae680314045aedb291ef773f1b9941a22971e734'/>
<id>ae680314045aedb291ef773f1b9941a22971e734</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Describe the libc++ toolchain of the Linux hosts</title>
<updated>2026-10-16T18:31:31+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-16T18:31:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=efca790acb61ad35fedec22bd99c35657f1c6675'/>
<id>efca790acb61ad35fedec22bd99c35657f1c6675</id>
<content type='text'>
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++.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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++.
</pre>
</div>
</content>
</entry>
<entry>
<title>Correct stale statements on tala.run and rename the vxs storage keys</title>
<updated>2026-10-16T03:05:28+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-16T03:05:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=3c3c9b10e1ccf218831789bcc59d488200ed12c6'/>
<id>3c3c9b10e1ccf218831789bcc59d488200ed12c6</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Serve tala.run and the documentation of talac and Tazel</title>
<updated>2026-10-15T15:00:48+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-15T15:00:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=ef68517d39fc329cf3286ad70056e00acf8b4855'/>
<id>ef68517d39fc329cf3286ad70056e00acf8b4855</id>
<content type='text'>
The language now lives at tala.run. One frontend build serves three
sites and picks its content from the host name:

- tala.run: the home page, /docs/overview, /docs/getting-started and a
  new /docs/syntax, a first look at programs, comments, declarations,
  operators and evaluation by need, with every sample taken from the
  public specification.
- talac.tala.run: /docs/command-line and /docs/outputs, the compiler's
  options, the entry rule, warnings, --build and --emit, and the record
  of a check.
- tazel.tala.run: /docs/commands and /docs/project-file, the commands of
  the build system, target selection, workspaces and the project DSL.

The new pages are written in all four locales from one content model;
a test keeps code samples and option names identical across them. The
header links the three sites and forum.tala.run. On a development host
?site=talac or ?site=tazel selects a site.

Corrections to the existing pages:

- Getting started used `go run scripts/develop.go`, `talac check -File`,
  `talac build -File` and `-Help`; it now uses `go run ./helpers/cmd/...`,
  `--emit=metadata`, `--entry=` and `--help`.
- The overview no longer names the retired .vxse extension, and the
  project DSL is evaluated by Tazel.
- Canonical URLs, Open Graph data, robots.txt and the sitemap name
  tala.run; talac and tazel have their own robots and sitemap files,
  served per host by Nginx. The notice about the move is gone: the
  former domain redirects instead.
- The leopard mark files are called tala-mark.svg and tala.svg.

Nginx: ops/nginx/tala.conf serves the three hosts, redirects www.tala.run
to tala.run and every path of xsharp-lang.xyz to the same path of
tala.run, and keeps viget.xsharp-lang.xyz pointing at
viget.progmasoft.com; tala.run has no ViGet host of its own.
ops/nginx/forum.conf serves the informational page at forum.tala.run and
redirects the former forum address to it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The language now lives at tala.run. One frontend build serves three
sites and picks its content from the host name:

- tala.run: the home page, /docs/overview, /docs/getting-started and a
  new /docs/syntax, a first look at programs, comments, declarations,
  operators and evaluation by need, with every sample taken from the
  public specification.
- talac.tala.run: /docs/command-line and /docs/outputs, the compiler's
  options, the entry rule, warnings, --build and --emit, and the record
  of a check.
- tazel.tala.run: /docs/commands and /docs/project-file, the commands of
  the build system, target selection, workspaces and the project DSL.

The new pages are written in all four locales from one content model;
a test keeps code samples and option names identical across them. The
header links the three sites and forum.tala.run. On a development host
?site=talac or ?site=tazel selects a site.

Corrections to the existing pages:

- Getting started used `go run scripts/develop.go`, `talac check -File`,
  `talac build -File` and `-Help`; it now uses `go run ./helpers/cmd/...`,
  `--emit=metadata`, `--entry=` and `--help`.
- The overview no longer names the retired .vxse extension, and the
  project DSL is evaluated by Tazel.
- Canonical URLs, Open Graph data, robots.txt and the sitemap name
  tala.run; talac and tazel have their own robots and sitemap files,
  served per host by Nginx. The notice about the move is gone: the
  former domain redirects instead.
- The leopard mark files are called tala-mark.svg and tala.svg.

Nginx: ops/nginx/tala.conf serves the three hosts, redirects www.tala.run
to tala.run and every path of xsharp-lang.xyz to the same path of
tala.run, and keeps viget.xsharp-lang.xyz pointing at
viget.progmasoft.com; tala.run has no ViGet host of its own.
ops/nginx/forum.conf serves the informational page at forum.tala.run and
redirects the former forum address to it.
</pre>
</div>
</content>
</entry>
<entry>
<title>Call the language Tala in the text of the site</title>
<updated>2026-10-12T01:30:26+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-12T01:30:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/website/commit/?id=1fe6c7c32323f4dce488cbe11172f2963685b8e0'/>
<id>1fe6c7c32323f4dce488cbe11172f2963685b8e0</id>
<content type='text'>
The logo already said Tala while the header, the titles, the pages and the
forum notice still said Visual X#. The text now names the language Tala in
the four languages of the site, in the page metadata and in the forum notice.

With the name go the things that changed with it: source files end in .tala,
the project file is BUILD.kts, the compiler is talac, and the links lead to
Progmasoft/tala. A native executable still ends in .vxse, so that stays.

The forum page refers to its stylesheet and script with a new version value,
because the script changed and a cache in front of the host keeps the old
file for hours.

Not changed: the host names, the file name of the mark, and the keys under
which the browser keeps the chosen language and theme, so that a visitor
does not lose them.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The logo already said Tala while the header, the titles, the pages and the
forum notice still said Visual X#. The text now names the language Tala in
the four languages of the site, in the page metadata and in the forum notice.

With the name go the things that changed with it: source files end in .tala,
the project file is BUILD.kts, the compiler is talac, and the links lead to
Progmasoft/tala. A native executable still ends in .vxse, so that stays.

The forum page refers to its stylesheet and script with a new version value,
because the script changed and a cache in front of the host keeps the old
file for hours.

Not changed: the host names, the file name of the mark, and the keys under
which the browser keeps the chosen language and theme, so that a visitor
does not lose them.
</pre>
</div>
</content>
</entry>
</feed>
