Not a ton of changes. Just the background image, the prompt style titles are new, that's fun. Oh, and the entire back-end's been changed up. I asked Claude to summarize the changes we made.

*A few weeks ago, your website was built with Next.js (a fancy JavaScript framework) running in a Docker container. Every time you wanted to change literally anything - even just fixing a typo - you had to rebuild the entire container and restart it, which took minutes. It was like having to rebuild your entire house just to change a lightbulb. This got really annoying really fast, especially since all you wanted was a simple personal blog to post updates about your projects.

So we converted it to a static HTML site with a Python build script - no more container, just plain files served by nginx. That was better, but you still had to run a build script every time you edited a blog post. Then we switched to pure PHP, which meant changes appeared instantly on the site with zero build process. But the files ended up scattered between two different directories because of how the containers were set up. Today we finally consolidated everything into one clean directory that's managed by Git, added proper timestamps to blog posts, made the admin panel smarter about handling edits, and basically turned it into a simple, fast website where you can write a post, hit save, and it's live immediately - no builds, no waiting, no complexity.*

This shit is so worth the $20/month. Come on, this is fun lol.

The entire point of this experiment is to let Claude do things on its own. I'm using the Claude Sonnet 4.5 model, my prompts were all natural language, like "hey i'm getting a 404 error on the site, please investigate i didn't ask it to use a particular language, i just said "i want a website, it'll look like this" with a badly drawn sketch of the layout. Then there were a dozen or so iterations where I realized just how shortsighted Sonnet 4.5 is. Why was a full-docker-rebuild strategy used during the design phase? Why did it split all my files up into two places later? why did it create another public_html folder? I was figuring out how it was thinking, really.

AIs are children. They have no object permanence; they'll accomplish their goal without considering their affect on the big picture, they don't have any vision *into* a big picture, it's just "you want a login button, ok i'll do that" and deletes/replaces my entire footer with a login button. Ya did it. Technically.

But the iterations are good for learning what this model's capable of. I'll use the Opus 4.5 model for planning my next project, then switch to Sonnet 4.5 for any maintenance on that project.