Skip to main content

Vibe Coding Alert! How I Rebuilt a Wix Site and Fed the “AI Will End SaaS” Panic


My better half is an artist and maintains a Wix.com site. For the second time in two years, Wix decided to raise the hosting fees. That’s when I suggested to my spouse that I could rebuild the website and host it on Firebase (where I host most of my projects). I assumed this wouldn’t be a big deal (I was wrong) and started researching ways to use a lightweight CMS with Firebase support. Such a system exists — it’s called FireCMS — and it’s excellent.

Before I dive deeper, here’s her original site (no longer a paid Wix site):  Miyuki's WIX site

Her instructions were clear: replicate it as closely as possible. So I went to work. I created a product development document with use cases, scope, screenshots from the original site, the required features, and of course FireCMS integration. I used ChatGPT to draft the document, then set up a new Firebase instance, and finally launched the Vibe Coding agent (Claude Code).

The process wasn’t too different from my other projects, but what surprised me was how much I actually learned this time. When reviewing code or asking questions like “how would I do that?” or “what’s the best way to achieve this?”, I often got insightful answers that introduced me to tools, features, and practices I hadn’t known about. In short, I gained a much deeper understanding of Firebase, especially its storage facilities (which I used for the images of her paintings), user permissions, Google ID integration, and whitelisting.

But the biggest breakthrough was discovering that I could embed structured data directly into a site’s header using Schema.org Naturally, I went ahead and did exactly that.

So, what’s the outcome of this roughly 5-day effort spread across 5 weeks? I built an open-source content management system for artists — anyone familiar with Firebase and Angular can use it. Her new website (completely free) is now live here:

 https://www.tribecaconcepts.com

And the source code is available on GitHub:

 https://github.com/ugubser/artcms

It’s another example of “vibe coding.” I didn’t write a single line of code or documentation — I only reviewed it, ensuring we avoided storing API keys or other sensitive data in the repo.

If you’re familiar with Firebase, I’d love to know whether you can spin up your own instance just by following the instructions. Let me know in the comments here. 

Labels:

Comments

  1. Mia Rose SaasAugust 27, 2025 at 11:13 AM

    nice post.

    ReplyDelete
  2. Mia Rose SaasAugust 30, 2025 at 2:31 PM

    This open-source CMS for artists built on Firebase and Angular is a brilliant example of vibe coding and lean innovation. If you're exploring creative, scalable tools like this, check out micro saas projects—perfect for turning smart builds into sustainable products.

    ReplyDelete

Post a Comment

Popular posts from this blog

The case for central bank digital currency as public infrastructure to enable digital assets

I have dabbled a fair amount with all sorts of crypto currencies and their respective permissionless networks. In fact, I have been dabbling since 2012 which is by my last count a whopping 12 years. While I have always maintained that I do believe the general concept for digitization and programmability of assets is on the right path, its implementation, the user experience, the accessibility, the fraudulent activities, and the overall inefficiencies permissionless DLTs have, never made me into a true believer. I have stated that opinion on several occasions, here , here and here . There are still barriers to entry when it comes to digitization of assets: sustainable- and interoperable infrastructure. To illustrate this, I recently asked a notary public here in Zurich, why they can’t store the notarized documents as PDFs, the answer surprised me: because they must keep records for at least 70 years. Now, think about what would have happened if we stored these documents on floppy disks...
Post a Comment
Read more

Apples Vision Pro Headset strategy is all about its Arm-chips.

  Apple has given us a vision of what their VR and AR future might entail. But as have others pointed out numerous times, the whole point of the showcase at the WWDC 23 was to let people experiment, I’ve heard others say that it’s like the launch of the Apple Watch when Apple didn’t really know what would become of it. This is similar and yet different.  Just like the Apple Watch (and the iPad before it), Apple sought to porting its whole ecosystem onto a watch – granted, the Apple Watch can’t live on its own and a better comparison would probably be the iPad. The iPad can live without any other Apple device and unlike the iPhone, never really had a clearly defined function other than to watch movies and browse the web. It was not until it gained the ability to be used with a pencil that artists and designers started to explore the potential.  I’m trying to point out that Apple took 5 years from the first iPad in 2010 to the iPad Pro with pencil in 2015 to find its “kille...
Post a Comment
Read more

I've Been Vibe Coding for 2 Months, Here's What I Believe Will Happen

In the past few months, I've embarked on an experiment that has fundamentally changed how I approach software development. I've been "vibe coding" - essentially directing AI to build software for me without writing a single line of code myself. This journey has been eye-opening, and I'd like to share what I've learned and where I think this is all heading. My Vibe Coding Journey I started vibe coding with Claude and Anthropic's Sonnet 3.5 model, later upgrading to Sonnet 3.7, Claude Code, and other tools. My goal was straightforward but comprehensive: create a CRM system with all the features I needed: Contact management (CRUD operations, relationships, email integration, notes) Calendar management (scheduling meetings, avoiding conflicts) Group management for organizing contacts A campaign system with templates A standalone application using the CRM's APIs for external contacts to book meetings direct The technical evolution of this project was inter...
Post a Comment
Read more