If you’re bundling Composer dependencies in your WordPress plugin, you need to namespace them. You’re setting up your users for conflicts with other plugins if you don’t implement proper namespacing.

Some @woocommerce.com extensions do it wrong — read how @yoast.com does it right

Don't call it a relaunch.

ZeroPoint helps you create "marketing" style websites without a monolithic (and increasingly corporate) CMS like WordPress.

Focused on DX, version control, and native web technology, you get: an @11ty.dev base, a CMS, and a new "blocks" system.

Check it

getzeropoint.com

New Acorn guide: Creating WP-CLI commands with Laravel's Artisan Console

`composer remove wpackagist-plugin/safe-svg && composer require roots/allow-svg`

github.com/roots/allow-...

bsky.app/profile/benw...

It's 2025 and you still need a plugin in order to upload SVG files to a WordPress site... and the plugin (safe-svg) used to be fairly minimal, but now it includes a shitty block

The 12 year old ticket that WP core still won't touch: core.trac.wordpress.org/ticket/24251

Acorn v5 and Sage v11 have been released! Sage is now using @vite.dev for the build system along with Tailwind v4

roots.io/sage-v11-and...

WordPress 6.8 is bringing native bcrypt password hashing, which means our wp-password-bcrypt package is no longer needed. We're officially sunsetting it:

roots.io/sunsetting-w...

roots/sage in Pressonia (the country of WordPress) from the Map of GitHub

https://anvaka.github.io/map-of-github/#10.93/-36.7418/9.8018