Replacing a proprietary CMS does not automatically give governments control over their digital services. Five Government Summit speakers examine the responsibilities that come with adopting open source.
Universities can replace a CMS or reorganise their websites without knowing how difficult it would be to change providers again. The missing evidence lies in contracts, documentation and the cost of transferring technical responsibility.
The Netherlands has committed to greater open-source collaboration. But what will it take to turn that commitment into shared digital services that governments can develop and maintain together?
...more
Dashi demonstrates Drupal CMS's multilingual editing capabilities, but its first release exposes two compatibility problems that affect local installations.
...more
AI-generated Drupal code can look correct while using outdated APIs, invented fields or incomplete cache metadata. Project instructions and repeatable checks help developers identify those mistakes before committing changes.
...more
Patching the vulnerability may not be enough for affected Drupal Commerce stores. The Security Team has also instructed operators to check their orders for inconsistencies.
...more
Organisations without in-house developers may have a new way to support the maintainers behind the Drupal modules they depend on. How would that responsibility fit into certification?
...more
Companies already contributing to Drupal may find that their work carries more weight. A higher contribution score, however, does not automatically mean a higher Certified Partner tier.
...more
A new CISA deadline raises the urgency of the PHP2Shell response. Specbee's account of emergency Drupal patching shows why deploying fixes and establishing what happened before them are separate challenges.
...more
Sixty-three maintained Drupal AI projects, one per job, each with its install count, latest release and security advisory status from Drupal.org.
...more