| commit ae9cb15306bc1e22374536950d2add7b875d9017 parent 1c0ca27f86f24c2327e4839ed2905fe31522e953 Author: sqzer <110329244+sqzer-x@users.noreply.github.com> Date: Sat, 25 Jul 2026 22:08:35 +0900 Write the documentation, and stop writing Korean like notes The site had three pages and a sidebar with one entry in it. Whatever else was wrong with it, most of what made it feel unfinished was that it was unfinished. There are now five sections — getting started, writing content, templates, features, deploying — and thirty-eight pages across two languages. Only what the code actually does is documented. Every configuration key, front matter field and template value here was read out of the source rather than recalled, because a documented key that does not exist is worse than an undocumented one that does: it sends a reader looking for a bug in their own file. The pages that explain a decision explain the reasoning too — why URLs are directories, why slugs come from filenames rather than titles, why template selection is four steps and not twenty — since a rule whose reason is invisible reads as an arbitrary restriction. Cross-references are all `@/` links, which means the build checks them. Thirty new pages of prose is exactly where a stale link would otherwise slip in unnoticed. The Korean was rewritten. It was in the terse declarative register you use for your own notes — 빌드한다, 필요 없다 — which is fine in a commit message and wrong in documentation a stranger is reading; it lands somewhere between curt and machine-translated. It now uses complete sentences throughout, matching how Korean technical writing actually reads. The search index grew to 19 rows and 38 KB per language, still one fetch on first use. Checked against the finished site: 최적화 finds the three pages that mention 검색엔진최적화, and 존성 finds the three that say 의존성. Diffstat:
|
sqzass~ static site generator in Rust |
| git clone https://github.com/debuman/sqzass.git |