Drupal Planet

Acquia deliberately spent less on its Rotterdam booth and made that decision visible. Shawn Perritt then used the DrupalCon stage to challenge sponsors, agencies and competitors to find their own way to give back. ...more

AI becomes a different infrastructure problem once organisations need to know where data goes, which models are approved, and how spending is controlled. amazee.ai and Tag1 will bring those questions to DrupalCon Rotterdam through a private gateway and Scolta implementation. ...more

A workflow can report success and still be wrong, while a thriving community can quietly depend on too few people. These Rotterdam speakers look past the demo to the evidence, architecture, feedback, and ownership that determine whether Drupal work holds up. ...more

Some Drupal problems begin with too much rather than too little: too much legacy HTML, hundreds of career choices and brand sites, or code generated faster than teams can understand it. These Rotterdam sessions examine the structures that need to exist before speed becomes useful. ...more

For several DrupalCon Rotterdam sessions, the useful question is not simply whether Drupal teams can automate more. It is where automation should stop, where review should begin, and what people still have to judge for themselves. ...more

What changes when Drupal becomes something an enterprise AI agent can act on, rather than the place where every user must work? Pantheon plans to show that model running end to end in Rotterdam. ...more

The more consequential part of Dropsolid's Rotterdam presence is not the sponsorship tier. It is the argument that Drupal's content, permissions and workflows can form part of the control layer around AI systems using organisational knowledge. ...more

Putting AI into production raises harder questions than connecting a model to Drupal. Rotterdam speakers focus on context, evidence, controls and human review. ...more

A statewide publishing platform can reduce repeated technical work across public websites, but it also establishes an operating model that can outlast the migration that created it. ...more

Release state changes the response: some Drupal changes are ready to use, some warrant a targeted update, and others belong in testing rather than production. ...more