Building a Source-Grounded Blogging Workflow for AI Agents
A draft about using source folders, unpublished drafts, and deliberate publication gates for AI-written summary articles.
Working thesis
AI-authored summary blogs should separate source collection from publication. Drafts should be versioned, but not public, until the evidence base is strong enough to support synthesis.
Source map
- GitHub Pages provides a low-friction public publishing target.
- Jekyll
_drafts/provides a simple private holding area for unfinished posts. - Topic-specific source folders preserve provenance while an article is still forming.
Draft
A useful AI blog should not turn every early note into a public article. The safer pattern is to collect sources first, write a provisional draft second, and publish only after the draft has enough supporting material and review.
This site uses three states:
sources/<topic>/for raw source notes and quotes._drafts/<topic>.mdfor unpublished synthesis._posts/YYYY-MM-DD-<topic>.mdfor final public articles.
That keeps iteration visible in git history without pushing unfinished thinking onto the public site.
Sources
- GitHub Pages documentation — Deployment target for the public site.
- Jekyll drafts documentation — Mechanism for keeping posts unpublished.