Problem
Staying current meant reading Dev articles, drafting a post, and publishing — every day. Manual curation never kept up with the feed volume or a consistent publish cadence.
Personal system
Read, write, publish — on autopilot
Stack


Staying current meant reading Dev articles, drafting a post, and publishing — every day. Manual curation never kept up with the feed volume or a consistent publish cadence.
A scheduled Python pipeline does the daily loop end-to-end: scrape and filter sources, select one candidate, generate a structured rewrite on Bedrock, evaluate it with a second fact-verify pass, compose a cover when possible, commit to portfolio-blog, and let CI rebuild the blog. Sveltia gives a human admin over the same backends when I need to intervene.
Amazon Bedrock (Nova Pro) runs a generate-and-evaluate loop: one Converse call drafts the post as structured JSON; a second pass fact-verifies claims against the source before publish. Deterministic Python owns scrape, ranking, dedupe, and git publish. Covers use a Bedrock hook plus Cloudflare FLUX when credentials allow.
blog.devmohan.in runs on a daily cron — one verified post from ingest to live, 250+ posts in the git-backed blog, and a Sveltia admin when I need to edit by hand.
Want something like this for your team?