From WordPress to Nuxt: Building an AI-Powered Content Pipeline

💡 Quick Summary (TL;DR):

• Goodbye WordPress: Left behind an old, neglected WordPress installation that I had stopped updating due to maintenance friction and time constraints.
• The Shift in Value: AI has reduced the value of generic setup guides that contain no real decision or experience. Instead of chasing tech hype and parameter counts, I will write about AI philosophy, strategy, and hands-on project insights.
• The Brandbook & AI: Collaborated with AI to go through what felt like an enterprise-level brand consultancy process, creating a detailed personal Brandbook. Used AI agents to audit, edit, and align all past posts with this philosophy.
• The AI-powered content pipeline: Reduced the operational friction of static Git-based blogging with CLI-based AI assistants while keeping editorial and technical review in the loop.

It has been a long time since I last published a post here. Behind the scenes, my site was running on an old WordPress installation that I had neglected for a long time. Over time, the friction of keeping this setup updated and maintained eclipsed my desire to write.

But the issue wasn't just technical; I was also questioning the very purpose of my content. The setup guides and configuration tutorials I wrote years ago no longer excited me. More importantly, AI has changed what a static guide needs to contribute in order to be worth maintaining.

The Demise of "How-To" Guides

Today, if a developer needs to know "how to spin up MongoDB with Docker," they can ask ChatGPT or Claude for a starting point tailored to their environment in seconds. That answer may still be wrong, incomplete, or unsuitable for the reader's version, constraints, or security requirements. It needs verification and context.

That does not make every how-to article worthless. It changes the threshold. A generic sequence of commands that contains no real decision, trade-off, or lived experience is easier to replace and harder to justify maintaining. A guide that explains why a choice was made, what failed, and where the boundary lies can still be useful.

Similarly, I have no interest in chasing tech hype or writing superficial news about the latest model releases and their trillion-parameter counts. In a world where raw information is cheap and immediate, the real value lies in context, strategy, real-world trials, and honest failures.

Going forward, this blog will focus on:

• AI philosophy, business strategy, and its real-world implementation.
• Field notes, architectural decisions, and learnings from my own projects (like Redar, PeşinTaksit, and VaniBot).
• Unfiltered post-mortems of what worked and what didn’t.

A Personal Brandbook and My AI Agents

This transition wasn't just a technical upgrade. Before launching, I collaborated with AI to go through what felt like an enterprise-level brand consultancy process, resulting in a highly detailed personal Brandbook.

In this brandbook, we defined the "DO/DON'T" rules of my personal brand, its typography, colors, positioning, tone of voice, visual identity, and even the core prompt templates for AI-generated images.

The best part about this brandbook is its dual design: it is fully human-readable and optimized for my new teammates, my AI agents (AI-readable). Going forward, whether it's a new article on this blog or a new software experiment, this brandbook will serve as our shared source of truth and compass.

Additionally, during this migration, I collaborated with AI agents to audit and edit all my past posts, updating obsolete guides and aligning them with my new brand voice. That was the complete review I carried out before this site launched in June 2026.

August 2026 update: I have now carried out a second portfolio review. This one is not a revision of that June work: it is a new pass over which articles still deserve maintenance, which should be refreshed, and which no longer belong in the site. The principle remains the same: keep the work that carries a real observation, decision, or experience; do not preserve material merely because it once existed.

Why a Git-Based Blog, and Why Nuxt?

Historically, I shied away from Git-based static blogging. Locally creating Markdown files, manually formatting them, managing images, and running git commands created too much friction between having an idea and publishing it.

But this time, I have a powerful partner: AI.

By opening my CLI and explaining an idea or raw draft to an AI assistant, I can remove much of the mechanical work. It can structure Markdown, flag grammar, help locate links, and prepare a draft for deployment. I still need to check the facts, the links, the rendered page, and whether the argument says what I mean. The friction is lower; the responsibility is not.

For the stack, I went with something lean, fast, and modern:

• Nuxt as the framework, with Nuxt Content for managing posts.
• Cloudflare Pages (free tier) for hosting and instant global delivery.

The result is no database to operate, a simpler publishing surface, fast delivery, and a setup I actually own. It still has dependencies and maintenance work, but those are visible and manageable.

By leveraging AI not just for code but as a co-creator to organize my thoughts, I hope to write more frequently and share much deeper insights. See you on the new path.