Zensical for the wiki's site
Created
Zensical for the wiki’s site
Decision (2026-10-02): the wiki is published as a static site built with Zensical, pinned, with a small converter for its Obsidian-style links. The Quartz site was retired.
Alternatives
| Option | Why not | |
|---|---|---|
| B | SilverBullet (read-only) | a live editor-style app; path in the header, tags wrap badly on the phone, and editing would break the one-writer rule |
| C | Material for MkDocs + a links plugin | maintenance mode; MkDocs 2.0 drops plugins. Kept as the fallback engine, same config, no plugin |
| D | Otter Wiki | needs full-path links (25 of 28 broke) and shows file names as titles |
| — | Wiki.js, BookStack, Outline, Docmost | keep pages in a database, so the files stop being the truth |
Why
The cleanest reading on desktop and phone (left nav, table of contents, instant search with tag
filters), static files only, and nothing changes for the writers: the vault keeps [[slug]] links
and the converter rewrites them at build time. Codex reviewed the publisher four times; the last
verdict was “ready”.
What would change it
- Zensical breaking or being abandoned: build with the Material fallback (
build.sh <vault> <out> material, same config) and look again at the alternatives. - Gregory wanting to edit pages from the browser or phone: that is the case for SilverBullet (B), with a rule for who writes.
- Upgrades: Zensical’s dependable 0.1.0 line is due 2026-11-05; re-pin only after
check.shpasses.
See llm wiki. Proposal and screenshots: <path>.
Scope
This decision covers the private wiki’s site. The public edition of selected pages is a separate static site built with Hugo, so its look and layout are not set here.