The latest articles on DEV Community by Yonatan Gross (@yonaigross). https://dev.to/yonaigross https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3819756%2Ff1220597-437f-4132-9de7-96c498250b9f.jpeg https://dev.to/yonaigross en Yonatan Gross Thu, 12 Mar 2026 10:32:21 +0000 https://dev.to/yonaigross/building-an-automated-content-pipeline-that-posts-to-6-platforms-h8a https://dev.to/yonaigross/building-an-automated-content-pipeline-that-posts-to-6-platforms-h8a <p>Every developer knows the pain: you write a great article, publish it on one platform, and then spend the next hour manually reformatting and posting it everywhere else.</p> <p>I built an automated content distribution pipeline that publishes to 6 platforms from a single source of truth. Here's how.</p> <h2> The Architecture </h2> <p>Write once, distribute everywhere:</p> <ul> <li> <strong>Hashnode</strong> (source of truth)</li> <li> <strong>Dev.to</strong> (you're reading this here)</li> <li> <strong>LinkedIn</strong> (article share + commentary)</li> <li> <strong>Threads</strong> (text teaser)</li> <li> <strong>Instagram</strong> (card image + caption)</li> <li> <strong>daily.dev</strong> (auto via RSS)</li> </ul> <p>Each platform gets a tailored variant — not a blind copy-paste.</p> <h2> The Platform Adapter Pattern </h2> <p>Each platform implements a common interface with a single <code>publish()</code> method. Adding a new platform is just implementing one class. Rate limiting is Redis-backed per platform.</p> <h2> Smart Content Composition </h2> <p>The hardest part isn't the API calls — it's making content feel native. Twitter gets a 280-char hook. Threads gets a 500-char teaser. LinkedIn gets a 3,000-char article share.</p> <h2> The Quality Ladder </h2> <ol> <li>Ollama (local, free) generates the first draft</li> <li>Quality gate checks readability and boring-start patterns</li> <li>Claude Haiku polishes if needed (~$0.002)</li> <li>Template fallback as safety net</li> </ol> <h2> The Feedback Loop </h2> <p>A weekly task evaluates performance, extracts patterns, and injects learnings into future prompts. The system gets smarter over time.</p> <h2> The Stack </h2> <ul> <li>Python 3.13, FastAPI, SQLAlchemy 2 async, Celery</li> <li>Next.js 16, TypeScript, TanStack Query</li> <li>AI quality ladder (Ollama → Haiku), RAG, pgvector</li> <li>1Password secrets, Redis rate limiting</li> </ul> <p><em>This post was cross-posted using the pipeline described above.</em></p> python automation api devops