A client wanted a Pinterest-style WooCommerce gallery, which used to mean Masonry.js or fragile grid math. The CSS Working Group settled on display: grid-lanes instead, and it is still rolling out behind flags.
A 30,000-line stylesheet taught me that BEM cannot outrun global scope. Web components and the Shadow DOM can, and the idea goes back to a 1998 proposal for HTML components.
My niece walked into the office and asked what I was typing. Explaining HTML as bricks and CSS as paint was harder than I expected, and it showed me where I had gotten sloppy in my own work.
A WooCommerce homepage carousel was wrecking Core Web Vitals. Dropping the JS slider for CSS animation-timeline and view() cut the script weight and pulled the LCP score back into the green.
A core update took a client’s checkout page down at 2 AM. Reading the release retrospectives and controlling minor auto-updates per environment is how I stopped that from happening again.
WooCommerce 10.4 makes the Interactivity API mini cart the default, lazy-loads two REST namespaces, and takes HPOS caching out of experimental. Here is what to test before you update.
WordPress 6.9 beta ships the server-side half of the Abilities API. You can register and retrieve abilities in PHP, but the client-side JavaScript moved to the Gutenberg repo, so there is no native AI interface in the editor yet.
WordPress 7.0 pulls View Transitions into core, and ticket #64066 raises preloading eagerness when a proxy cache is detected. Here is what that changes for admin speed, and why blanket prefetching pinned my CPU at 100%.
A Friday night emergency on a site I had not touched in six months cost me two hours of MAMP wrangling. WordPress Studio blueprints and selective sync are what I use now to keep client environments consistent.
Nobody checks whether $wpdb exists before running a query. The AI team wants models treated the same way in WordPress, with hosts providing the model and developers registering Abilities instead of wiring up API keys.