Building this site with Jekyll
Jekyll gives each note a home, shares the page structure, and builds the links into ordinary HTML.
A small structure for an evolving practice
I want to add a note without copying the whole website around it. With Jekyll, the content lives in Markdown files, metadata lives beside it, and shared templates provide the navigation and page structure. Existing HTML can stay where it carries a particular layout.
This site was built by me and my AI agents. The move to Jekyll kept the existing card addresses and résumé anchors while making the content easier to maintain. The point was to preserve the connections as the site grows.
Two ways into the implementation
- Connected notes in Jekyll: individual cards, explained relationships, backlinks and ordinary mentions.
- Building Jekyll for Cloudflare Workers: the templates, plugins, validation and static output behind the publishing workflow.
The benefit is in the boundaries
The editable source is different from the published output. AI agents and I can work on the source, inspect the resulting pages, and run checks before publication. Visitors then read static files; following a card link does not depend on an AI service or an application server.
Cloudflare handles the other side of the setup: the domain and the hosting workflow. Jekyll is what builds the site. That separation leaves the generated files usable on another static host if the hosting choice changes.