Blog
Drupal Meets Matrix 03 - Better Conversations with Advanced Comment Threads
Commenting in Drupal hasn't noticeably changed in 15 years. That changes now.
Drupal Meets Matrix part 2: Live Comments with ECA and HTMX
A comment thread in Drupal works totally fine. You fill in a form, click submit, and your comment gets posted. Same way it has for over 20 years.
But if somebody else replies when you're on the page, you don't see anything change, you don't get any notification.
Beyond Bigger Servers: Keeping Websites Online Under Bot Attacks
Using AI to review AI-Generated code: Astra vs. Opus vs. DeepSeek
Drupal Meets Matrix part 1: Setting up Matrix API
I've been maintaining the matrix_api module on Drupal.org since 2016, nearly a decade of it doing one thing well: posting Drupal events into a Matrix room. This year that changed.
For the Long Haul: AI can build it. Who’s maintaining it next year?
WordPress Has Thousands of Maintainers. Does Your Replacement?
Last month, a critical WordPress vulnerability triggered emergency patching across the web — and reignited a familiar argument: if WordPress keeps having security problems, why not let AI build something new instead?
It’s a reasonable question.
AI has made software dramatically cheaper and faster to create. But somebody still has to understand it, patch it, test it, and keep it running eighteen months from now.
That’s the part of the “AI instead of WordPress” pitch we think is getting overlooked.
Zero to new Drupal site in 133 seconds
Gabor asked in Slack about how people contributing to Drupal manage multiple different Drupal versions, and different contributed module branches, when using AI agents:
We Patched wp2shell in 4 Hours. On a Friday Afternoon.
On July 17, WordPress shipped an emergency security release for a vulnerability chain now being called wp2shell.
Tempting Fate: What Happened When One of Our "Protected" Sites Got Hacked