Misadventures in CSS
May 2026
After many days of studying and refactoring, the first round of CSS optimizations are here. I'm working with a very small sample size — the index and the Witch Hat Atelier article — and using a separate stylesheet so that I can make big changes without affecting the entire layout of the site.
And oh boy, is it affected. All of the html, all of the CSS was rebuilt completely from scratch with performance, readability, and proper naming in mind. If you take a look at the html of the index versus any other page, you'll notcie that it's already a radically different beast (even though it looks essentially the same).
Right now I'm working towards smooth CSS transitions; that means removing all of the box-shadows and replacing them with ::after pseudo-elements. It means changing how the Style Drawer works on every single page. It's a huge project! Why am I doing it?
Well, the truth is that this site is five years old. When I started working on it, I didn't know anything about web design. I named classes based on sheer instinct and used all of the wrong html tags. And after years of using the site that way, I can't rebuild the site's scaffolding without tearing the whole thing down and rebuilding it. It's that unsteady.
I've rebuilt this site multiple times. It gets easier each time. As I learn more about web design, I make more decisions that mean less rebuilding and more building. Now, I'm at a level where I believe that this site will meet a public standard — not just my own.
It's a long journey, and I'm still on it, but this site is my home. And I want it to be the best that it can be.