Nobody asked for a CMS. Organisations needed to share knowledge; users needed answers they could trust. AI is making that original purpose impossible to ignore and it may be exactly where Drupal becomes more valuable, not less.

Prerequisite

Basic familiarity with Drupal as a CMS or content platform is helpful. No coding or AI implementation experience is required. This is a strategic and practical session, not a step-by-step technical build tutorial.

Target Audience

Digital leaders, product owners, solution architects, agency leaders, technical strategists, and content/search owners in higher education, public sector or complex enterprise environments. This session is especially useful for people who use Drupal or are evaluating Drupal as part of a wider digital ecosystem, and who need to understand how AI, search, content governance and composable architectures fit together. It is not primarily aimed for a code-level RAG implementat

Outline

Nobody asked for a CMS. Organisations needed to share knowledge; users needed answers they could trust. Yet many digital projects still revolve around the CMS itself: content types, workflows, menus, permissions and publishing models while users remain stuck between search results, intranets, PDFs and support channels.

This session uses Helsinki Uni Help, a Finnish university/public-service AI search project, as the main proof point for a wider shift: content management is moving from page publishing toward governed knowledge flow. We will show how Drupal can act as the trusted content and governance layer behind an AI answer experience: structured source material, editorial ownership, multilingual content, integrations, retrieval, citations and feedback loops.

We will also briefly contrast this with our own Astro + LLM publishing experiment, where the traditional CMS UI is no longer the primary editing interface. The point is not that CMSs are dying. The point is that AI changes what the CMS is for.

Attendees will leave with a practical model for deciding when Drupal should be the editing interface, when it should be the content infrastructure, and how to think about AI, search and content governance beyond “which CMS should we use?” And even further, can content governance learn - and even teach - organizations to find the true gaps that keep them from reaching their goals?

Learning Objectives

After this session, participants will be able to:

- Explain why AI shifts CMS value from page publishing toward governed knowledge flow.
- Identify the parts of a Drupal ecosystem that matter for AI answer delivery: structured content, ownership, APIs, retrieval, citations, feedback loops and governance.
- Use lessons from HelsinkiUni Help to evaluate when Drupal should be the editing interface and when it should act as content infrastructure.
- Ask better discovery questions before starting CMS, search, content strategy or AI projects.

Experience level
Intermediate