Day 0 | An electrical engineer's fourth website

Day 0 | Finally getting around to a personal site

I'm Kelvin: electrical engineer, web designer, and AI summoner (lol).

This is my fourth website. (A few days in, it's already the fifth, and I'm getting ready for a sixth.)

Over the first few sites, almost everything changed, from the tech stack to the way I build. This time I want to pull what I learned into one place and write up the whole process as a series.

We were on Cloudflare and Next.js from the very first site. Four years ago there were a few other options, but cost kept winning, so we went with Cloudflare. Its dashboard back then had an ugly layout and no search. The plan did what we needed, so we used it anyway.

Next.js kept shipping new versions, and the projects moved along with each upgrade. How I write websites changed a lot too.

In the early days I did everything by hand: editing code, handling PRs, merging. Bit by bit I brought AI into the workflow. Now it reviews PRs and sometimes merges them, and Cloudflare deploys the projects automatically.

For site number four, I want all of that in one workflow: how the site is built, how the stack gets picked, and how AI helps build and maintain it.

This series records those choices from the start. Why this framework? Why this hosting platform? And how did the work I used to do by hand get handed to AI, one step at a time?

Looking forward to meeting you and talking more.