-

·
Three themes, one question: where should your design live?
Mētis is a lot like Ollie, but it lacks child theme support at the moment. Ipsum supports child themes very well, but its guide for agents using the MCP Adapter tells AI to save design changes to the database. In many ways child themes have become less relevant, but they will remain in the agency / builder toolkit. They may even become a rich product ecosystem again, built on frameworks like Ollie.
-

·
Do you need a child theme?
When should you use a child theme with fully native WordPress block themes in late 2026? Use this guide to decide which design changes can live in WordPress’s Site Editor and database and which need to be more portable in files you can review and deploy from a code repository.
-

·
A Week of WordPress Contributions
What I worked on in WordPress core, the block editor, and some docs last week, mostly at WCEH26 Contributor Day.
-

·
Three WordPress.org projects and what they taught me
An admin menu editor, a bibliography block and a block theme have nothing in common functionally, but each one had a good lesson or reminder: hiding a menu item isn’t access control, content should outlive the plugin that made it, and a version floor is a design decision.
-

·
A simple theme project can lead to contributions all across WordPress
Building a brutally simple block theme turns out to be a good bug detector: with so little of your own code on the page, WordPress’s own bugs are easier to spot. Dirtbag is that kind of theme, and it led me into a 15-year-old curly-quote ticket, Gutenberg CSS, and core accessibility issues.