I had been considering a self-nomination for the Drupal Association At-Large Board Seat a few times. This year, I decided to throw my hat into the ring. I've been a bit busy with baseball season kicking off (three kids, three teams 🫠) that I haven't written a blog yet, but I will, explaining why I've considered now the right time. 

If you caught the State of Drupal presentation (aka Driesnote) from DrupalCon Atlanta, maybe you noticed something missing. There was no news about Drupal 11 or what lies ahead with Drupal 12. Instead, we talked about Drupal CMS, Experience Builder, and the upcoming concept of site templates.

PHPStan 2.0 was released a month ago, a massive milestone for the project. To learn about all the changes, I recommend reading the release announcement.

This blog expands on my DrupalCon Barcelona talk,

I was doing website maintenance and checked for outdated dependencies with composer outdated. I usually filter with -D for checking direct dependencies and -p for packages with patch releases. These are typically easy pickings.

Well, it's official. My Drupal Lenient Composer Plugin has allowed the lenient Composer repository endpoint on Drupal.org to be sunset and removed.

Drupal CMS is the official name for Drupal Starshot.

Earlier this month, I debuted a way to try out Drupal core and the Starshot prototype running in the browser using WebAssembly. It started as a passion project and fascination with new web technologies, something I had tried a year before but didn't find a fit for.

At DrupalCon Portland, Dries announced Starshot during his State of Drupal presentation. Part of Starshot is the idea that we have Drupal CMS and Core. The big difference is that the Drupal CMS offering comes with standard contributed modules used by almost every existing Drupal build. Then, Dries showed a proposed wireframe for the Drupal.org download page.

This blog post was inspired by my time at DrupalCon Portland and the Driesnote, announcing Starshot.