A pipeline that turns source material into scheduled, publish-ready blog posts, from first draft to live page on the site.
Category
Content Production
Return
~2 hrs / week
Stack
Claude · Site platform
The Problem
A blog is easy to start and hard to keep alive. Source material exists, a newsletter, announcements, expertise in someone's head, but turning it into posts means drafting, formatting, titling and scheduling, week after week. The gap between "we have things to say" and "the blog says them" swallows most publishing plans.
The Solution
A pipeline from source to published page. Raw material goes in one end, and finished posts come out the other: drafted in the house voice, structured for reading, titled for search and scheduled across the week, ranked by what readers need first.
How It Works
- Source material enters the pipeline: a weekly newsletter, an announcement, a topic brief.
- Claude splits it into single-topic posts, because one clear idea per post beats a digest.
- Each post gets drafted in the publication's voice, with a headline, structure and metadata for search.
- Posts rank by importance and schedule across the week, most important first.
- Finished posts publish to the site on their scheduled mornings, and the archive grows on rhythm.
Built With
- Source-splitting and drafting rules in Claude
- The Writing Style rules of the publication
- A scheduling convention that spreads posts across the week
- Publishing to the site platform
I run this build in production for a client publication on a weekly cadence, and it draws its drafting standards from the same voice stack as everything else here.
What You Get
- A blog that publishes on schedule from material you already produce
- Single-topic posts that read cleanly and rank honestly
- An archive that compounds weekly without a weekly scramble
The Numbers
Two to three days to build for an existing site. It returns about two hours a week of drafting, formatting and scheduling, and the publication rhythm holds through the weeks that used to break it.