The screenshots gallery on WordPress.org plugin pages now renders core Gallery and Image blocks with the standard lightbox, while the masonry part stayed out of core. Here is what shipped, why core turned the masonry down, and how I would build the same thing.
The standard account says neural networks learn low frequencies first, so frequency content alone decides how hard a target is to fit. New experiments show the shape of the target near the edges matters too, and that changes which fix you reach for.
A multi-agent AI workflow is a few model calls in a row, each with its own role prompt. The pattern itself is simple. What decides whether it survives on a real WordPress site is the queue behind it, and what each agent actually sees.
June was a loud month: WordPress 7.0 is out, React 19 got reverted, and media processing moved into the browser. Here’s how I split the roundup into what gets tested now on real sites and what gets filed for later.
Most WordPress AI plugins scan every page on every reindex, so the bill grows with your content. There are three ways to route content to a model, and the block tree gives you one of them for free. I compare them and say when each pays off.
A llama.cpp project that prefills a shared document once and fans the KV cache out to many agents is really a lesson in prompt order. Here is how the same shape shows up when your agents are just API calls from PHP, and how to check it.
Automattic shipped ten experiments during Radical Speed Month, and most of them only exist on WordPress.com. The two that don’t are Desktop Mode and Studio’s Blueprints Gallery. Here’s how to sort the list, what a blueprint file looks like, and what I’d actually adopt.
A developer built a World Cup forecaster from 49,000 international matches, and the results say more about shipping prediction features than about football. The honest parts: draws that never get predicted, data leakage hiding in a rating column, and a simple regression that tied the boosted model.
Scroll effects in CSS come as four separate features, and they ship at different times in different browsers. I go through which one fits a progress bar, a sticky header, a reveal, and a page fade, and where the fallbacks still need JavaScript.
The June 2026 WordPress performance chat spent most of its time on cross-document view transitions for the frontend. The tickets say a lot about where core is heading, and you can already test the one-line opt-in on a client site.