Trim unused WordPress core blocks to speed up the admin
A client’s store had every core block loaded and a sluggish backend to show for it. Here is how we worked out which WordPress core blocks to unregister, and the snippet we used.
A client’s store had every core block loaded and a sluggish backend to show for it. Here is how we worked out which WordPress core blocks to unregister, and the snippet we used.
A client’s whole API auth was a hardcoded key checked against a query parameter. Here is how I rebuild API key authentication in WordPress as a real security layer, using the REST authentication filter.
A client wanted their marketing team to pick which custom product attribute shows on a page, from the editor. Custom block bindings in WordPress 6.9 make that possible, and here is the source registration I used.
How WordPress 6.9’s unique IDs stop Interactivity API directives from clashing on the same element, plus the data-wp-ignore deprecation and new TypeScript helper types.
A WordPress agency published solid dev tutorials and still landed no clients. The fix was not more SEO, it was writing content around what clients actually struggle with.
WordPress 6.9 fixes the parts of the Interactivity API that made SPA-like navigation painful: dynamic scripts and stylesheets load on their own, nested router regions update, and a new attachTo property can place a region anywhere.
A tiny custom post type tweak turned into a two-month project because we chased perfection instead of shipping. Why incremental development, the way WordPress 6.9 itself is built, works better.
A client outgrew their all-in-one site builder and hit a wall. Why WordPress open source gives you ownership, portability, and customization a closed platform can’t.
WordPress 6.9 strips out the old Internet Explorer compatibility code. If you run an older custom theme, here is what tends to break and how to audit and modernize the CSS and JavaScript behind it.
WordPress is moving the block editor into an iframe in 6.9 and 7.0. Blocks on apiVersion 2 or lower throw warnings now and can break later. Updating to apiVersion 3 is the fix.