Eric Downs

The Claude Automation Pipeline That Runs This Site

How I built a content pipeline where I drop markdown and images, and Claude handles module selection, SEO, alt text, and publishing — in under 3 minutes.

AIClaudeAutomationSanityNext.js

I got tired of the publishing friction. Write content, manually create Sanity documents, pick modules, write meta descriptions, generate OG images, upload assets, set alt text. Every post took 30 minutes of busywork after the writing was done. So I automated all of it.

The pipeline is straightforward: I write in markdown with YAML frontmatter. Claude reads the content and picks the right Sanity modules — intro blocks, pull quotes, callouts, image layouts. It generates SEO metadata, writes alt text for every image, creates semantic tags for search, and publishes the structured document to Sanity. The whole thing runs as a single CLI command.

The best automation removes friction without removing control. I can override anything Claude suggests — but I rarely need to.

Sources

  1. Based on the production pipeline running ericdowns.co — all content published through this system
  2. Publishing time benchmarks measured across multiple content types

Key Statistics

  • Publishing time: 30 minutes manual → under 3 minutes automated
  • Zero manual CMS fields to fill per article
  • Stack: Next.js App Router + Sanity CMS + Claude (Sonnet) + Vercel

Expertise

Built and operates this pipeline daily for ericdowns.coTechnical Director with deep experience in CMS automation and headless architectures

Related

The Claude Automation Pipeline That Runs This Site — Eric Downs | Eric Downs