How We Publish
Four stages from idea to live post. A human creates the content and gives one approval. Claude handles everything after that: images, build, index, and the log.
Human in front, AI behind
The handoff is a single sentence: “Photos are in. Build the post.” Everything before it is human judgment. Everything after it is automated.
The four stages
Posts start from the weekly content schedule or an ad hoc idea. Each one is drafted in its own dated folder and iterated until the writing is right. No build work happens here, just words.
The final human review. Photos get dropped into the post's source folder, and the approval is one explicit sentence: “Photos are in. Build the post.” Nothing ships without it.
Claude turns the approved draft into a live-ready post:
- Converts raw photos to WebP, resized to a 1200px max width at 85% quality
- Renames images descriptively and writes keyword-rich alt text
- Builds the post page to the site style guide, with image placement rules per post type
- Updates the blog index and stages the changes in git
Every publish gets a log entry: the post slug, category, date, image filenames and where they were placed, the commit hash, and any issues hit along the way. The log is the audit trail for the whole pipeline.
The seven elements
Every workflow we document has the same anatomy: seven elements, each assigned to a human, a machine, or both. This is the Centaur Map from our workflow design method.
The weekly content schedule or an ad hoc idea. Content starts with a human wanting to say something.
The approved draft, the photos, and the site style guide that governs how every post is built.
The approval gate, one explicit sentence: “Photos are in. Build the post.” Nothing ships without it.
Post type determines image placement rules: listicles get inline images, narratives get a hero.
Optimized WebP images, a built post page, and an updated blog index, identical in structure every time.
Changes staged in git and deployed through the pipeline. The post is live without a manual upload.
The publish log: slug, images, commit hash, and issues, one entry per post, forever traceable.
Quality gates before anything ships
- Every image loads with a correct relative path
- Every image has descriptive alt text
- Filenames are lowercase with hyphens, no exceptions
- Navigation links resolve, and nothing extra sneaks in
Why it works
- One approval gate keeps humans in control of what gets said
- Automation keeps the build identical every single time
- The publish log means every post can be traced to a commit
- Writers write. Nobody hand-edits HTML or resizes photos.