AI may accelerate output, but the featured speakers are looking at the content structures, application design, development processes, and working conditions that surround its use.
...more
TDT weekly newsletter 'Editor's Pick: Volume 4, Issue 32' asks what happens after publicly funded software is delivered. Security response, supplier handover, upgrades and governance must continue after the original contract ends.
...more
Reusable Drupal components become awkward when each placement needs a different presentation. ERFO adds controlled variation without duplicating or altering the referenced content.
...more
Drupal’s automation tools solve different problems. The harder question is how they can exchange work without weakening their execution models, permissions, or auditability.
...more
Changes to how Drupal handles dynamic page updates could force contributed-module maintainers to support different behaviour in Drupal 11 and Drupal 12.
...more
Drupal’s shared infrastructure does not sustain itself. Volume 4, Issue 31 of Editor’s Pick follows the funding, review, governance, and maintenance work behind the systems the ecosystem relies on.
...more
A developer I work with sent this skill over recently, asking whether it was worth adopting across the agency's client projects (an additional pass before publication under a client's name).
Farriss says reserves are covering a gap in Drupal’s wider stewardship work, prompting proposals to expose programme costs and connect enterprise use with ongoing support.
...more
Matthew Saunders links his board candidacy to a question now facing Drupal: how the Association can earn community trust through measurable listening, accessible participation, and public accountability.
...more
Scott Falconer links his board candidacy to a question now facing Drupal: how the project can grow without allowing AI adoption, enterprise influence, or vendor dependence to weaken community control.
...more