Gutenberg 23.1 finalizes image uploads in parallel instead of one thumbnail at a time. It also adds an experimental taxonomy UI in the admin, Drawer and Autocomplete primitives, and a filter that hides the Classic block from the inserter.
Asking an LLM whether a value changed significantly turns a cheap comparison into a slow, untestable guess. Here is the split I use in WordPress: PHP thresholds decide when to act, and the model only writes the message.
WooCommerce added a Subscriptions Health Check tool under Status. It finds subscriptions stuck on manual renewal after the HPOS cache bug, plus active subs with missing or overdue payment dates. Here is what caused it, and what the changelog left out.
WooCommerce for Claude came out of Automattic’s Radical Speed Month. It uses MCP to give the model analytics lookup tables, a store knowledge layer and an AI-readiness score, all on one endpoint. Plus the provider pattern and how to run it locally.
A “5x improvement” on its own tells you nothing. Three questions pull it apart: which dimension moved, from what baseline, and against which period. Examples from Core Web Vitals, model accuracy, and a transient cache bug that faked a 10x speed boost.
Google’s Prompt API is Chrome-only, downloads a 4GB Gemini Nano model without asking, and requires developers to acknowledge Google’s Generative AI Prohibited Uses Policy. My case against calling that a web standard.
A store you can launch in an hour is fine for a prototype. For a real business, the shipping zones, tax classes, asset loading and payment webhooks you set up on day one decide how much refactoring you do later.
Binary churn flags tell you that a user left but say nothing about the timing. This post covers discrete time-to-event modeling: why fixed intervals fit WordPress data, how right censoring skews a model, and a small PHP function for hazard rates.
LangChain is fine for a prototype. Once there is real traffic, several agents coordinating and a pager attached, the abstraction costs more than it saves. This is the case for writing the orchestration layer yourself.
WordPress wants to build Block Editor Handbook pages straight from block.json at build time. That would kill doc drift and give core blocks a reference that matches the code you are actually running.