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.
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.
WordPress itself is free to download, but hosting, premium licenses and maintenance are not. Where the money actually goes once a site has to earn its keep.
A client built a business site in twenty minutes with an AI prototyping tool. It looked great and could not talk to his inventory system or be crawled properly. Here is where AI website building stops and production work starts.
Real-time collaboration is targeted at WordPress 7.0 in 2026. Beta feedback says native blocks work fine and legacy post meta does not, so custom fields need registering for the REST API before then.
A client lost 70% of their reach in a week when a social platform changed its algorithm. This is the case for keeping your content on your own WordPress install, including how I organize it with custom post types.