aboutsummaryrefslogtreecommitdiff
path: root/content/wiki/blogroll.md
diff options
context:
space:
mode:
authorChristian Cleberg <[email protected]>2026-08-11 20:34:02 -0500
committerChristian Cleberg <[email protected]>2026-08-11 20:34:02 -0500
commitab149c1ae4fe38048fc2d32edac6061e7f3b4638 (patch)
tree984019a98b20789890566c595b52d5ddc8b21064 /content/wiki/blogroll.md
parent5be4598b09a2685d73665b403bf80aad50b15834 (diff)
downloadcleberg.net-migrate-to-orgo.tar.gz
cleberg.net-migrate-to-orgo.tar.bz2
cleberg.net-migrate-to-orgo.zip
Finish the move off weblorgmigrate-to-orgo
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.
Diffstat (limited to 'content/wiki/blogroll.md')
0 files changed, 0 insertions, 0 deletions