<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tazel.net/content/he-IL/docs, branch main</title>
<subtitle>The site of Tazel, tazel.net.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel.net/'/>
<entry>
<title>Build the site of Tazel with Nuxt</title>
<updated>2026-11-05T02:56:00+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-05T02:56:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel.net/commit/?id=6f114e3df68d0b20c7e58c5ffb8c46070317008a'/>
<id>6f114e3df68d0b20c7e58c5ffb8c46070317008a</id>
<content type='text'>
tazel.net is the site of Tazel itself: a Nuxt 4 site generated to static
files, in en-US, de-DE, ru-RU and he-IL, light by default with a dark
theme that is kept per browser.

- Home: the release and its kind, what Tazel does, the steps from a
  project file to a program, and a sample.
- Docs: Markdown through Nuxt Content, highlighted by Shiki (Kotlin,
  shell, PowerShell, and Tala through the grammar of the compiler
  repository), with a tree of the pages on the left, the headings of
  the page on the right, and the previous and next pages below.
  Installation, a first project, and releases and support are written
  in every language; the reference (commands, project file, lockfile,
  plugins, how Tazel works) is copied from the Documents of Tazel by
  scripts/sync-docs.mjs, and a language without a page shows the
  English one with a note.
- Every page has its canonical address, hreflang alternates and a
  sitemap entry; generation fails on a link to a page that does not
  exist.

CI checks the format, the types and the language helpers, generates
the site and runs Dependency Review on pull requests.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
tazel.net is the site of Tazel itself: a Nuxt 4 site generated to static
files, in en-US, de-DE, ru-RU and he-IL, light by default with a dark
theme that is kept per browser.

- Home: the release and its kind, what Tazel does, the steps from a
  project file to a program, and a sample.
- Docs: Markdown through Nuxt Content, highlighted by Shiki (Kotlin,
  shell, PowerShell, and Tala through the grammar of the compiler
  repository), with a tree of the pages on the left, the headings of
  the page on the right, and the previous and next pages below.
  Installation, a first project, and releases and support are written
  in every language; the reference (commands, project file, lockfile,
  plugins, how Tazel works) is copied from the Documents of Tazel by
  scripts/sync-docs.mjs, and a language without a page shows the
  English one with a note.
- Every page has its canonical address, hreflang alternates and a
  sitemap entry; generation fails on a link to a page that does not
  exist.

CI checks the format, the types and the language helpers, generates
the site and runs Dependency Review on pull requests.
</pre>
</div>
</content>
</entry>
</feed>
