<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog-Workflow on Corey Daley</title><link>https://coreydaley.dev/tags/blog-workflow/</link><description>Recent content in Blog-Workflow on Corey Daley</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 10 Mar 2026 15:40:00 -0400</lastBuildDate><atom:link href="https://coreydaley.dev/tags/blog-workflow/rss.xml" rel="self" type="application/rss+xml"/><item><title>The Blog That Builds Itself: AI Automation Behind the Scenes</title><link>https://coreydaley.dev/posts/2026/03/building-a-blog-automation-pipeline-with-ai/</link><pubDate>Tue, 10 Mar 2026 15:40:00 -0400</pubDate><guid>https://coreydaley.dev/posts/2026/03/building-a-blog-automation-pipeline-with-ai/</guid><description>&lt;p&gt;What happens when you stop treating AI as a writing assistant and start treating it as a co-publisher? This blog has accumulated a full automation stack: a /create-blog-post command that pits Claude and Codex against each other in a competitive draft workflow, a Python script that generates hero images using DALL-E 3 and Claude vision, pre-commit hooks that block commits with unoptimized images, and a Bash script that handles WebP conversion and thumbnail generation automatically.&lt;/p&gt;
&lt;p&gt;The design principle behind all of it: treat each stage as a contract, not a prompt. The meta-detail: this post was written by the same pipeline it describes.&lt;/p&gt;
&lt;p&gt;What would your content workflow look like if you designed it the same way you&amp;rsquo;d design a software system — and which parts would you never automate at all?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/03/building-a-blog-automation-pipeline-with-ai/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/03/building-a-blog-automation-pipeline-with-ai/&lt;/a&gt;
&lt;/p&gt;</description></item></channel></rss>