And we kept at it. It worked. An actual website emerged. But ChatGPT wasn’t always the world’s most reliable programmer. Images would suddenly move, one change could break something else, and sometimes it was hard to understand what had happened. Especially for me, because I still couldn’t code. When something went wrong, I couldn’t just open the file and fix it myself. I depended on ChatGPT both finding the problem and managing to solve it.
After two versions, I put the half-finished site on hold and decided to think about something else for a while. It stayed that way for quite some time.
Then, in 2026, I started using Codex. With ChatGPT, it had been a bit like having a programmer on the phone: I described what I wanted, got code back and tried to put it in the right place myself. With Codex, I could get help directly in the website project, where the files were. It became easier to make changes and check the results together.
I hesitated for a long time before daring to let Codex into the house. But eventually I did, and so far I haven’t regretted it for a second.
That was when the site started moving again. Codex has built on what was there, cleared out old leftovers, improved the mobile version and helped me turn the whole thing into a website that actually works. It has also helped with search engine optimisation — making it easier for Google to understand what the pages are about and what’s here. The site now has a sitemap and is connected to Google Search Console, where I can see whether Google is finding the pages and, over time, how people find their way here.
The funny thing is that the website was originally just meant to be the place where I collected things I’d made. The images, films, music, writing, books and design.
Now the website itself is one of the things I’ve made.