Let’s bring it home. I started the month by explaining The Laboratory:
I decided to build a new website to tell stories again—a place where the smallest ideas or the biggest ones can live. Time is much more limited for me now, so being efficient with that time is critical.
Since then, I’ve shown up daily. The Archives will show this. Didn’t miss a day. Big posts and little ones. Maintenance, experiments, and family moments. But more than anything, the topic that I spent the most time on was the infrastructure of the site. Creating the foundation for what’s ahead.
Let’s reflect.
Infrastructure
Tools: I like to keep the tools to a minimum. Field Notes, an iPhone, and Ulysses. That’s basically all that’s needed to run this site most days.
ChatGPT: I have to give credit to ChatGPT. Upon my return, I knew that I’d lean into the help of AI. Especially since it’s just me trying to bring big experiments to life. It takes what I’ve always done and amplifies and streamlines the process.
Artifact: The blog engine is built on top of Blot, with custom code (Artifact, Terminal, Red Dot) everywhere. Artifact is what makes all of this feel alive.
Backdating: A big part of this new blog is the goal to backdate everything. Not just old blog posts, but splitting emails up into multiple blog posts, and even adding every song idea I’ve ever recorded, backdating them into the Backstage project.
Tags and Thumbnails: Seems small but it was a big priority for a lot of the month. The tags allow me to connect ideas, and the thumbnails show up everywhere.
Money: The site is funded by Backstage and Tribune. Backstage is the membership for my music. Tribune funds the daily writing. Both links are at the top of the site.
Collaborate
I couldn’t have done any of this alone. Between Jay Ray and ChatGPT, the process flowed incredibly well. For today’s post, I asked Jay to summarize what he’s been up to:
When Nash returned to Blot from GitHub Pages, it meant blending old and new. He likes to experiment with layouts and content but keeps friction low. The legacy code felt bloated. I stripped out what he wouldn’t use, simplified it, and cut about 1000 lines of CSS.
Thanks to this infrastructure (The site’s design and all the different layers around the site — all the little compartments and boxes to put ideas into), I already feel like I’m hitting my stride. I expect a lot of cool things to come out of this. Excited for what’s next.