Spoiler: a lot of caffeine was involved.
This website didn’t come together because I wanted a redesign. It came together because I wanted to test myself, and test what building an AI website really looks like in practice.
I wanted to see what happens when you mix curiosity, modern AI website builder–style tools, a blank canvas, and a hard personal constraint: ship fast, but ship right.
What follows is not a “how-to tutorial.” It’s a reflection on thinking, building, and choosing structure over shortcuts, even when AI generated website tools promise magic.
Why I Decided to Build This Site (Again)
I’ve been in the WordPress ecosystem for years. I’ve built websites, shipped platforms, fixed broken builds, optimized performance, and rescued more sites than I can count.
So why rebuild my personal website?
Because the landscape has changed.
AI tools are everywhere now:
- tools that write,
- tools that code,
- tools that refactor,
- tools that deploy,
- tools that almost think for you.
And I wanted to answer one simple question honestly:
If I had to build a modern, fast, SEO-ready personal AI website today, how would I do it, and what would actually matter?
The 24-Hour Constraint (and Why It Matters)
I gave myself a rough window of about 24 hours. Not because that’s impressive, but because constraints force decisions.
When time is limited:
- you can’t over-engineer,
- you can’t chase shiny abstractions,
- you can’t blindly trust “one-click” AI site builder promises.
You have to think clearly about what actually matters.
This wasn’t about perfection. It was about clarity.
Yes, I’m a WordPress Guy
Let’s get this out of the way.
I love WordPress. I still believe it powers the web for a reason.
But being “a WordPress person” doesn’t mean:
- using it for everything,
- ignoring other architectural patterns,
- or pretending tradeoffs don’t exist when you build websites today.
This site isn’t a rejection of WordPress. It’s an experiment in separation.
The Core Decision: Separate Content From Presentation
One decision shaped everything:
Content should not be trapped inside the same system that renders it.
I wanted:
- clean, portable content,
- flexible presentation,
- fast delivery across mobile devices and desktop,
- and minimal moving parts on the front end.
That meant thinking in terms of:
- structure first,
- rendering later,
- and performance as a default, not an afterthought.
This mindset completely changes how you approach an AI website.
“AI Will Build It for You” (Almost)
I used a lot of AI tools while building this site.
Some helped with:
- drafting copy,
- exploring layout ideas,
- sanity-checking logic,
- accelerating repetitive work.
Others helped with:
- live coding,
- refactoring,
- spotting mistakes,
- and moving faster without cutting corners.
But here’s the honest truth:
AI did not replace thinking. It amplified it.
You still have to:
- decide what to build,
- decide what not to build,
- understand tradeoffs,
- recognize when an answer “sounds right” but isn’t.
AI tools can generate websites. They can’t judge intent, usability, or long-term website’s visibility in search engines.
Even With AI, This Took Time
This is important to say out loud.
Even with modern live-coding tools, assistants, copilots, and so-called free AI website builder experiences:
- things break,
- assumptions fail,
- integrations need reasoning,
- structure still needs intent.
AI speeds up execution, not clarity. And clarity is still human work.
The Caffeine Factor
There was a lot of coffee involved.
The kind where:
- you forget what time it is,
- browser tabs multiply,
- ideas feel brilliant at 2 a.m.
- and slightly questionable at 9 a.m.
But there’s a moment, and builders know this, when things click.
Pages load instantly. The structure feels solid. The content flows cleanly. The site feels quietly confident and user friendly.
That moment is worth the caffeine.
What I’m Proud Of (Beyond “It Works”)
I’ve launched many sites. This one made me pause.
Because never in my life did I think I’d casually ship a personal AI generated website that is:
- pixel-clean,
- extremely fast,
- SEO-ready by default,
- structured for scale,
- translation-friendly,
- schema-capable,
- and future-proof for experiments,
…without plugin anxiety, performance debt, or duct-taped features.
The structure matters.
Performance Wasn’t Optimized, It Was Designed
This site loads fast not because I “optimized it later.”
It loads fast because:
- there’s no unnecessary overhead,
- no bloated runtime,
- no accidental complexity fighting search engines.
Performance wasn’t a checklist item. It was a design constraint.
That changes everything.
SEO Without the Usual Pain
SEO is often treated as:
- an afterthought,
- a plugin,
- a toggle,
- a checklist.
Here, SEO is structural.
Clean URLs. Predictable metadata. Structured content. Schema readiness. Translation support.
These aren’t hacks. They’re outcomes of good structure, and good structure compounds website visibility over time.
Why I Didn’t Name the Stack (On Purpose)
You’ll notice I’m not listing platforms or naming systems.
That’s intentional.
Because tools change. Principles last.
The takeaway isn’t:
“Use what I used.”
The takeaway is:
“Think the way this was thought through, even when using AI.”
What This Site Is (and Isn’t)
This site is:
- a living experiment,
- a personal playground,
- a thinking space,
- a place to ship ideas fast.
It is not:
- finished,
- frozen,
- or pretending to be perfect.
I’ll keep populating content. I’ll keep iterating. I’ll keep breaking and rebuilding pieces.
That’s the point.
Why This Matters to Me
Building this reminded me of something simple:
The joy of the web is not tools, it’s intentional creation.
AI makes building websites faster. Modern architectures make them cleaner.
But the real work is still:
- deciding what matters,
- choosing simplicity,
- respecting users’ time,
- and shipping thoughtfully.
That hasn’t changed.
What’s Next
This is just the beginning.
I’ll be adding:
- more writing,
- experiments,
- small tools,
- playful ideas,
- and probably a few things that make other builders smile.
If you’re here because you care about:
- WordPress,
- performance,
- SEO,
- AI,
- or simply building better, faster, more thoughtful AI websites ,
Welcome. Pull up a chair. Coffee’s probably already brewing.
Related reading
→Prompt engineering in 2026: what it is and what it pays
→AEO and GEO in 2026: a practical playbook with Tavily, Winston, and schema
→WordPress vs Next.js in 2026: my honest comparison