I publish one technical article per day. I don't write them manually.

Here's the full system — architecture, scripts, real numbers, and what I learned after 45 published articles and 473 total views.

The Problem I Was Trying to Solve

I wanted to sell a technical ebook. The standard advice is "build an audience first." But building an audience manually takes time I didn't have — writing articles, posting on social, engaging in forums, repeating every day.

So I automated it.

The goal: a Python pipeline that handles the full content lifecycle. From topic idea to published article to cross-posted content — without me touching it daily.

What the Pipeline Does

outline.json ↓ Claude API → generates article markdown ↓ Validator → checks code blocks, frontmatter, links ↓ publish_queue.json → queues article for scheduled publish ↓ launchd (macOS) → runs at 10am daily ↓ Dev.to API → publishes article ↓ Hashnode API → cross-posts with canonical URL ↓ cover_map.json → attaches cover image ↓ link_patches.json →…