🧠
Alejandro Ramirez
🇪🇸🇬🇧
NavegaciónAlejandro Ramirez
🏠Inicio
Proyectos

Biblioteca

🗿The 3D Challenge: Beating the Retreat Cards
☁️Deploy your blog with Git
🛠️How I built my AI-powered MDX editor to publish again
🎁Retreat Gifts
Avatar de Alejandro Ramirez

Alejandro

🖼️Galería

For years I had the same problem: I wanted to write, but I never managed to publish consistently.

I tried several platforms: WordPress, Substack, and Beehiiv. WordPress was the one that blocked me the most. It was always the same cycle: install a theme, maintain plugins, keep up with updates, and spend time on everything except content. One of those websites even got hacked, and after that I stopped writing.

The turning point: back to content

At some point I found a project that let you edit articles with MDX, with a Notion-like experience. The idea was solid, but it depended on a third-party platform that charged you and kept you on their subdomain unless you paid more.

That is when I thought: with everything AI can already do, why not just build my own editor?

The problem I actually wanted to solve

I was not looking for "another CMS." I wanted to remove the friction that kept stopping me:

  • write fast,
  • add cool components,
  • and keep everything in Git with full control.

That is how this project started: an MDX-based blog where my content lives in my repository, versioned, portable, and independent from closed platforms.

What changed with this approach

For me, these two points matter most:

  1. The content is mine, and I can present it however I want.
  2. I can ask Cursor to help me write and edit without leaving my workflow.

The second point changed everything. Before, I had to jump between tools to generate text, review it, paste it, and edit it again. That context switching killed consistency. Now I can talk, draft, and refine in one place.

Result: less friction, more publishing

This project is not about adding tech for the sake of it. It is about solving a real blocker: publishing consistently.

In the next article, I explain how to deploy all of this on Cloudflare so anyone can access it.

🛠️How I built my AI-powered MDX editor to publish again

AIMDXProductivityBlog

For years I had the same problem: I wanted to write, but I never managed to publish consistently.

I tried several platforms: WordPress, Substack, and Beehiiv. WordPress was the one that blocked me the most. It was always the same cycle: install a theme, maintain plugins, keep up with updates, and spend time on everything except content. One of those websites even got hacked, and after that I stopped writing.

The turning point: back to content

At some point I found a project that let you edit articles with MDX, with a Notion-like experience. The idea was solid, but it depended on a third-party platform that charged you and kept you on their subdomain unless you paid more.

That is when I thought: with everything AI can already do, why not just build my own editor?

The problem I actually wanted to solve

I was not looking for "another CMS." I wanted to remove the friction that kept stopping me:

  • write fast,
  • add cool components,
  • and keep everything in Git with full control.

That is how this project started: an MDX-based blog where my content lives in my repository, versioned, portable, and independent from closed platforms.

What changed with this approach

For me, these two points matter most:

  1. The content is mine, and I can present it however I want.
  2. I can ask Cursor to help me write and edit without leaving my workflow.

The second point changed everything. Before, I had to jump between tools to generate text, review it, paste it, and edit it again. That context switching killed consistency. Now I can talk, draft, and refine in one place.

Result: less friction, more publishing

This project is not about adding tech for the sake of it. It is about solving a real blocker: publishing consistently.

In the next article, I explain how to deploy all of this on Cloudflare so anyone can access it.

En esta página

  1. The turning point: back to content
  2. The problem I actually wanted to solve
  3. What changed with this approach
  4. Result: less friction, more publishing

← Volver al inicio · 2026-04-13 · ~2 min