¶I think I finally grasped the power of AI, and specifically Claude Code, this morning.

¶I’ve been thinking of resurrecting Daystream over the last few weeks and had an interesting thought last night: maybe Daystream should be the software that generates the site, not the software that runs the site. Maybe Daystream makes more sense as a static site generator. I’m tired of configuring and running servers and have been working on a separate static site generator for my photography site. I’ve learned a lot from working with Claude Code to develop the system behind that site (Stringer, which is not yet public) and have enjoyed the work involved with hosting a static site, especially in comparison to hosting a rails app (the last iteration of daystream.com was a Rails app).

¶So this morning, at about 8AM, I asked Claude Code if it would take a look at the codebase for the Daystream Rails app, review the database backup, consider all of the work we’ve done on the Stringer SSG, and propose a process for moving Daystream to an SSG. I was pleasantly surprised when Claude Code told me it could do it all in one go and asked whether I’d be hosting the generated site on daystream.com or a new URL. On a whim, I decided to move my content to a new URL, thinking that setup would reflect use of Daystream the SSG, leaving the generated site to be hosted elsewhere.

¶I already owned somewastrue.com (I’ll tell that story later), so I made a few DNS changes and then authorized Claude Code to let it rip. About an hour later, I had new software that was generating a static site that includes all of my existing Daystream content (more than 1000 pages) and even had the look and feel of the old site.

¶Unbelievable.

¶So now I made the executive decision to run with it. I’m going to continue working on developing Daystream as a static site generator and will host my site, built with Dastream, on somewastrue.com.

¶Welcome to the future.