I've been quietly running a small network of niche content sites for a few weeks. Two are live on real domains:
The niche isn't the interesting part. The pipeline is.
Instead of one model for everything, a router picks per article type:
Every draft, before it ships, passes through:
A daily job re-scores everything published in the last 24h and auto-regenerates the failures. The whole thing is Next.js 16 + MDX, one git repo per site.
The honest target: a $30k/mo run-rate in ~24 months across 30 mature sites, monetized through guest-link sales, not ads. Slow on purpose.
Happy to go deeper on the router logic or the QA scoring if anyone's interested.
source & further reading
dev.to — original article
I Made Claude Code Ding When It's Done (And It Changed My Workflow)
I scanned my MCP setup and it scored 0/100. Here's what was wrong.
Azure Databricks for MLOps and Feature Engineering at Scale with Apache Spark, Delta Lake, and MLflow