Today I learned posts published on GitHub Pages.
The live site is built by GitHub Pages using GitHub’s hosted Jekyll stack and the dependency set they maintain.
Jekyll and gem versions follow GitHub’s Pages release line; this repository does not pin that environment with a Gemfile or Gemfile.lock.
For the versions GitHub uses in production, see Dependency versions.
Pushing to the publishing branch runs Jekyll on GitHub Pages; that is the canonical hosted build. Automated tools and contributors should follow AGENTS.md, including the policy of not suggesting an extra CI job just to duplicate that Jekyll build.
For development, mise run serve runs Jekyll in Docker using an image (naoigcat/github-pages) that mirrors GitHub’s published Pages dependency set.
The image ref lives in mise.toml under [vars] github_pages_image so we can bump it when refreshing against GitHub’s stack.
It is not duplicated here: production builds stay tied to GitHub’s hosted environment, which can change without updates to this repo.
Requires Docker and mise. The first time you work in this repo, run mise trust in the project
root so mise will load mise.toml (see mise trust).
mise run serveThe command starts the server, maps port 4000 to localhost, and opens the site in your default browser (macOS).
Tag navigation uses a single page at /tags/. Each tag links to /tags/?tag={slug} (for example /tags/?tag=sort).
At build time Jekyll embeds a lightweight tag index plus full post lists for tags listed in _data/tags_embed.yml;
other tags load /assets/tags/{slug}.json on demand in the browser.
Regenerate those JSON files with mise run tags after adding or retagging posts.
Production builds run on GitHub Pages’ hosted Jekyll, which does not execute custom Ruby in _plugins/.
This repository does not rely on _plugins for site behavior; features that must work in production are implemented with
committed pages, Liquid, and small client-side scripts (such as the tag index above).
Local mise run serve uses a Docker image that mirrors GitHub’s Pages dependency set. It may run Jekyll with different
flags than production, but anything committed under _plugins/ would only affect local output—not the live site.
Do not add custom plugins unless you also change the deployment model.