Broken references stop the build
An unresolved link, a missing template, two pages claiming the same URL, a misspelled config key — every one is an error, not a warning you scroll past.
Static site generator · Rust
Most generators lean on their host for pretty URLs, redirects and cache headers. sqzass does that work itself, so the same output is correct on GitHub Pages, on Vercel, or in a directory served over plain HTTP.
The site you are reading is built with it. So is its own documentation — which makes the docs a regression test for the generator, since CI builds them with the binary it just compiled.
Design
None of these are preferences. Each one is a failure that happened somewhere else first.
An unresolved link, a missing template, two pages claiming the same URL, a misspelled config key — every one is an error, not a warning you scroll past.
Link rewriting, heading anchors and the table of contents are tree operations. A regex over finished HTML silently skips any attribute that is single-quoted.
Two builds of the same input produce the same bytes, and CI checks it on every push. Rendering is parallel; determinism comes from the merge, not the schedule.
Translations sit beside their originals, links resolve to the reader's language, and search matches substrings — the only way 최적화 inside 검색엔진최적화 is ever found.
Highlighting emits class names. Inline colours pin one theme into every document forever and put a strict style-src out of reach.
No Node, no Python, no system libraries. The thing you download is the thing that runs.
Quickstart
$ sqzass init mysite
# writes sqzass.toml, content/_index.md, templates/page.html
$ sqzass serve -i mysite
http://127.0.0.1:3000 live reload
$ sqzass build -i docs
60 pages → docs/public
Real output. The documentation site in this repository is 60 pages.
Built with sqzass, from the docs directory of the same repository. CI builds it with the binary it just compiled.