Prompt-to-page generation is already available in Drupal CMS. ExperienceKit shifts the question to who defines and maintains the components the AI is permitted to use.
A documentation problem with complex Drupal forms led to a broader idea: keep operational knowledge within the site, then reuse it wherever it is needed.
Drupal AI activity now spans releases, events, workstreams, and training sessions. The new briefing brings those updates into one recurring publication.
...more
Existing Drupal AI project lists can become incomplete or outdated. An automated pipeline now provides a sortable and filterable view of modules and recipes that directly depend on the AI module.
...more
A capable model becomes a fragile dependency when access, pricing, or policy changes. Drupal teams need routing and fallback plans that keep governance inside the site rather than inside one provider.
...more
Southwark reports substantial time savings, although results vary with document complexity. The practical test is whether councils can move long reports into an editable workflow without surrendering editorial review.
...more
The sessions place Drupal AI in front of service desks, editorial teams, and sensitive campaign moderation instead of leaving the discussion at roadmap level.
...more
AI systems need more than models. Matthew Saunders argues that Drupal’s existing content controls offer a useful foundation for governed AI workflows.
...more