Talking Drupal 10/16/26

Talking Drupal4 min read
Forwarded this email? Subscribe here for more

Talking Drupal 10/16/26

Oct 16

#574 - UN Open Source Week

Today we are talking about the UN, Open Source, and Drupal with guests Tim Lehnen & Henry Poole. We’ll also cover Live Update as our module of the week.

Topics

  • What Is UN Open Source Week

  • Why Open Source Fits UN Goals

  • Who Attends and What Tech Is There

  • Conference Audience and DPI DPG

  • Drupal as a Digital Public Good

  • UN Uses Drupal at Scale

  • Why Attend and What to Gain

  • Upstream First Contracting

  • Open Procurement Curriculum

  • Reaching Procurement Conferences

  • Steering Spend Upstream

  • Funding Open Source Legally

  • Talking Louder Beyond Drupal

  • Digital Sovereignty Explained

  • Governance Values Matter

  • Fixing Funding Perception

  • Community Next Steps Closing

Resources

Guests

Henry Poole - civicactions.com henry-poole
Tim Lehnen - drupal.org hestenet

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan
John Picozzi - epam.com johnpicozzi
Tim Sharp - tea-sharp

Module of the Week

with Martin Anderson-Clutz - mandclu.com mandclu

Live Update - Drupal Live Update is the reusable event layer Drupal never had. Modules publish events to named channels; browsers receive them and refresh only the pieces that matter — no full page reload, no reinventing the wheel every time someone needs a live dashboard, notification or block.

The base module ships with Drupal-side polling. It works out of the box, zero extra services required. When you want real push, drop in a transport: WebSocket, Server-Sent Events, Node.js… or the purpose-built Live Update Go service.


Upcoming Episodes

#575 - The Drupal Advocacy Program with Tiffany Farriss. Recording October 20.

#576 - Inside & Outside Drupal AI with Scott Falconer. Recording October 27.

#577 - A Chat With Randal Schwartz. Recording November 3.

#578 - Talking with Nicky Pike. Recording November 10.

Submit your questions on the #TalkingDrupal channel on Drupal Slack.


Reasons Not to Use Drupal: Debunking 5 Common Myths

by Mart Anderson-Clutz

Think Drupal is outdated, slow, or hard to learn? Here's what's true about five common Drupal myths, and what's changed in the reimagined platform.

If you’ve searched for reasons not to use Drupal, you’ve probably found plenty. Most of them trace back to a version of Drupal that was powerful but hard to work with; a CMS you chose for its muscle and tolerated its learning curve.

That reputation used to make sense, but it no longer describes the platform today. Drupal has been reimagined, and it’s worth a second look when you’re in the market for a CMS. Here are the five most pervasive myths about Drupal, insights on what’s changed, and the one myth that still holds a grain of truth.

Is Drupal outdated?

No. Drupal is built to evolve without forcing you into a rebuild, and its structured approach to content is exactly what AI systems now demand.

The true cost of an outdated platform shows up later, in the replatforming project you’ll face in three years. Acquia commissioned research of 575 developers and 250 CIOs and CTOs. One of the top development priorities it uncovered: finding a platform that won’t need a full rebuild as AI evolves. Fifty-seven percent of non-Drupal developers and 47% of Drupal developers rank it in their top three.

Since Drupal 9 launched in 2020, each major release has been designed as a straightforward upgrade from the one before. And because Drupal is modular, you can update specific capabilities, like AI integrations, as your needs evolve without touching the rest of your site. On Acquia, that upgrade path comes with enterprise compliance and hosting built in.

Additionally, our survey found that developers now rank AI readiness as the third most important factor when choosing a CMS (40%). On the other end of the spectrum, CIOs and CTOs rank it second to last. So the people building your stack are already shopping for AI, even if the people approving the budget aren’t there yet.

Leadership isn’t ignoring AI, though it is insisting on having the foundation in place first: 56% of CIOs and CTOs say they won’t deploy superficial AI features until their content is well structured. Marketing leaders see the same problem. In Acquia’s CMO survey, 56% of CMOs say their content was built for people to read rather than for AI to use, and 47% aren’t confident an AI assistant would answer a customer correctly from it.

Continue Reading at Acquia.com


Contact Us

#talkingdrupal on Drupal Slack

[email protected]

© 2026 Talking Drupal
5 Wayland Rd Bristol RI 02809

Get the appStart your Substack

33 links in this issue

Sent by eBPFChirp. Links that track readers or name the subscriber were removed from this copy; its images still load from the sender's own servers. If you publish this newsletter and want an issue corrected or removed, write to us.