How I Built This Site in a Weekend
7/3/2026 · build, tech
For years I published on platforms I didn't own — Substack, LinkedIn, other people's spaces. It works, until it doesn't. The algorithm shifts, the rules change, and the audience I thought was mine was never really mine at all.
So I decided to build my own corner of the web: somewhere I control the content, the data, and the domain. This site is the result — and I built it in a weekend, with AI, without being a developer.
Here's the honest walkthrough.
The stack, in plain terms
Three pieces, nothing exotic:
• A front end — the pages you're reading — built with Next.js.
• A database, where posts and leads live, on Supabase.
• Hosting on Vercel, which redeploys the site automatically every time a change is saved.
I didn't hand-write most of this. I worked with Claude Code: describing what I wanted, reviewing what it built, and testing each piece before moving on.
How it came together
I built it in stages, not all at once:
1. First, the writing — posts I can create, edit, and publish, and a public feed anyone can read. The core had to work before anything clever went on top.
2. Then the point of it all: leads. A contact form that saves each visitor's message straight into my own database, and an admin view where I can see every lead and log each conversation. This is what rented platforms never gave me — the relationship, captured and mine.
3. Then locking it down: a login so only I can reach the admin side, and security rules so visitors can submit the form but can't read anyone else's data.
4. Finally, polish — tags to filter posts, filtering leads by status, proper share cards when a link is posted to LinkedIn, and my own domain.
The parts that weren't smooth
It wasn't all clean, and the lesson I keep relearning showed up again: the hard part isn't the technology, it's the design and the details.
When I added the security rules, they were a touch too strict and quietly broke the contact form — visitors got an error and their messages never saved. It took real debugging to realise the "lock the doors" step had locked a door that needed to stay open to the public. The fix was small once we found it, but it was a good reminder that shipping fast and shipping carefully have to travel together.
Connecting my domain was its own small puzzle. I already run buildglobalbridges.com on another service and didn't want to touch it, so this site lives on a subdomain — blog.buildglobalbridges.com — and the two run side by side, neither stepping on the other.
What I have now
A site I own end to end. I write a post and it's live in seconds. Someone reaches out and their message lands in my own database, where I can track every follow-up. No middleman, no borrowed audience, no platform that can change the rules on me.
If you've been meaning to build something of your own and assumed you needed to be a developer — you don't. You need a clear idea of what you want, the patience to test each piece, and a willingness to sit with the messy middle. The tools have caught up; the bottleneck is design, not code.
Rented reach is fragile. Owned channels compound. This site is me betting on the second one.
Grace