My personal web garden & blog. http://git.krz.sh/cmc/cleberg.net.git/atom?h=main 2026-08-12T01:35:15+00:00 2026-08-12T01:35:15+00:00 Christian Cleberg hello@cleberg.net 2026-08-12T01:34:02+00:00 urn:sha1:a6ee2e0ca79b83b7f6bd4a521777cffdaf2260f2 Remove what the migration left behind, then cut build.py down to the work orgo does not do: 443 lines to 168. - Delete publish.el and theme/templates/, superseded by content/orgo.toml and content/templates/. theme/static/ stays; orgo publishes it as assets. - Drop the tag builder, the org-source copy, and the helpers that only fed them. orgo generates /tags/ and a page per tag from a collection. - Rewrite the README and the migration-era comments that explained the config by pointing at what weblorg used to do. - Serve styles.css as authored. Minifying 1KB of CSS saved 52 bytes over the wire once compressed, which did not pay for a build step and a toolchain dependency. - Stop wiping the output directory. The .orgo-cache.json inside it is what makes a build incremental, and orgo already prunes outputs whose source is gone and re-emits any that are missing. Production keeps .build/ and development gets .build-dev/, because production rewrites image URLs in the output and a shared directory would let one environment reuse pages rendered for the other. An incremental build is byte-identical to a clean one, and the site output is unchanged apart from the /uses/ stack row. 2026-08-12T01:35:15+00:00 Christian Cleberg hello@cleberg.net 2026-08-11T21:48:53+00:00 urn:sha1:5d60a70d6a963c234d311ca87829cf3150f72ef6 The config file follows the tool: content/org-ssg.toml is content/orgo.toml, and the build cache it writes is .orgo-cache.json. Nothing about the site changes — 196 pages, same output.