We needed a way to write and edit the courses. Instead of paying a CMS to own our content, I just vibe coded the editor — on the stack we already own.
by Nick
We just shipped a course editor for just vibe — and I built it the same way I'm going to teach you to build everything: by vibe coding the exact tool I needed, on a stack I already own.
Here's the funny part. Up to now I'd been writing lesson copy as files in the codebase. Totally fine for a developer. But "edit a file, commit, redeploy" is not the workflow I want when I'm tweaking a lesson at 1am — and it's definitely not the workflow this whole platform is about.
The usual play here is to reach for a CMS. Pay for Sanity or Contentful, or wire up some open-source headless thing, learn all its quirks, and hand it the keys to my content. That's the reflex: a problem appears, you go rent a platform to solve it.
Instead I just… vibe coded my own.
By the end of a session I had a real editor living right in the admin: a markdown editor with a live preview, a formatting toolbar, image uploads, and the ability to create, reorder, and delete lessons and whole courses. Everything I need to write and refine the curriculum — no code, no redeploy. The lessons moved into my own database (which I own), rendered by a few lines of code I can actually read and change.
That's the entire thesis, playing out on the platform itself. I didn't need a content platform. I needed a content editor — and the tools to build one were sitting right there, free, the same ones I'm teaching you to use. So I built exactly what I needed and not one feature more.
If a "non-developer" with an AI can build their own SaaS, they can build their own admin tools too. You are not limited to whatever a platform decided to hand you. When you own your stack, the answer to "I wish this had a tool for X" is just… build the tool for X.
And now I'm using that editor to write the very lessons that'll teach you to do the same. It's turtles all the way down, and honestly? I kind of love it.
f*ck it, we vibe.