Part 5 of 5. ← Part 1: The Why · ← Part 2: The Architecture · ← Part 3: AI Curation Workflows · ← Part 4: Agents and Weekly Audits

The previous four parts built the system and the habits around it. Capture works, curation is mostly automated, and a weekly audit keeps quality from drifting. But none …

Part 4 of 5. ← Part 1: The Why · ← Part 2: The Architecture · ← Part 3: AI Curation Workflows · → Part 5: The Publishing Pipeline

The first three posts built the system: the reasoning in part 1, the Hugo structure in part 2, and the capture plus curation workflows in part 3. This part is about what …

Part 3 of 5. ← Part 2: The Hugo Architecture · Part 4: Agents, SEO, and Weekly Audits →

The structural layer in part 2 handles visibility and builds. This post covers the AI workflows that handle the actual ongoing work of a second mind: capturing, curating, and surfacing knowledge.

The design …

Part 2 of 5. ← Part 1: The Why · Part 3: AI Curation Workflows →

The structural core of this system is deliberately simple. Hugo already does most of the work. The job is to wire it together correctly.

The visibility toggle: draft as a first-class concept

Hugo’s draft frontmatter field has …

In this blog post, I try using GitHub Codespaces to write this post in Hugo. Yes, it’s meta 🤓

A GitHub Codespace is a cloud-based developer environment attached to your GitHub repository. It contains the dependencies you need to work on your codebase in VS Code, either in the browser or from …