How this handbook works

The handbook is a static site: every article becomes complete HTML before publication. That keeps the client payload small, improves the first load, and leaves the content usable when JavaScript is disabled.

Architecture

Hugo handles routes, Markdown rendering, tables of contents, sitemaps, language variants, and metadata. The project has no React, Astro, or component library. Templates live in layouts/, styles in assets/css/main.css, and articles in the language directories under content/.

Language variants

English is the default language and has no URL prefix. Russian lives under /ru/; German lives under /de/. Every translation shares a translationKey, so the language switcher opens the equivalent article instead of sending readers back to a home page.

What runs in the browser

One small vanilla JavaScript file has two jobs: remember the light or dark theme and search a local JSON index. Navigation, article reading, and language switching work without it.

Updating the content

Edit the relevant Markdown file in content/en, content/ru, or content/de. When adding an article, create variants with the same relative path and translationKey; Hugo will connect the translations and emit the corresponding hreflang metadata.