The week of June 6 had three tracks running in parallel, which is more typical than I usually admit.
The themes
I spent the first half of the week inside the Colophon theme collection, all eight themes, converting them to 100% Full Site Editing. FSE conversion touches every layer of a theme. The template files have to be rebuilt from scratch. Even the way colors get declared changes. I also pushed each theme through WP.org compliance review, which surfaces problems that don’t show up in local testing. Hardcoded footer text. Unsupported feature claims. Those aren’t big on their own, but they block submission, and they reveal gaps in the build process I hadn’t formalized.
By end of Thursday, all eight themes had GitHub Pages live previews, documented developer hooks, AI-generated hero images for the two that needed them, and a submission-ready ZIP for the first one.
The podcast
I’ve been planning Declamatio for a while. This was the week I actually made audio.
Episode 1 went through six iterations. That’s the kind of quality spiral that happens when you’re establishing a production standard for the first time. The intro timing was off. One channel had a 39-second glitch from a mismatch in how the voice cast was assembled. A character named Walter needed to become Claire. By end of the week, both episodes were complete, mastered, and deployed to the server. I also locked a 26-episode season arc, which changes how the work feels. It becomes less “let’s try this” and more “let’s build this.”
The content system
The third track was quieter but probably the most load-bearing. I ran a full audit of the the column archive, tagged 28 blog posts with pillar taxonomy, and started writing down the production gates that have been implicit in how I work but never actually documented.
The tagging work sounds administrative. What it showed me: a meaningful portion of posts I thought were on-pillar are actually adjacent. Close enough to publish, not close enough to compound. That gap doesn’t appear until you map it.
What I took from the week
Each track finished because the end was specific. The theme work was done when I had a submission-ready ZIP and live previews up. The podcast was done when two episodes were on the server. The taxonomy audit was done when all 28 posts were tagged.
When the exit condition is fuzzy, a track doesn’t finish. It stops when the next thing starts.
Product names referenced on this page — including GitHub — are trademarks or registered trademarks of their respective owners. Training offered here is independent and is not affiliated with, endorsed by, or sponsored by any of these companies.