I Got Tired of Gluing Together n8n, GPT Prompts, and a CMS So I Built My Own Blog Engine for Next.js

Over the past year I kept trying to automate blog content for my SaaS projects. It always started simple. Generate ideas with AI. Write drafts. Push them through n8n. Store them in a CMS. Render them in Next.js. Update the sitemap. Revalidate cache. Ship. But the system kept getting heavier. Every time I added one more automation, I added one more thing that could break. Eventually I realized the problem was not AI. It was the glue. The friction was not obvious at first n8n workflows fail quietly. A credential expires. A node changes output shape. A webhook times out. Now your publishing pipeline is half working and you do not notice for days. Then there was context. Most AI blog tools generate content in isolation. They do not understand your product. They do not know your positioning. They do not know your terminology. They do not understand your internal linking structure. So you end up editing more than you expected. Then SEO slowly drifts. Titles are slightly off. Meta description