The program is taking shape — join us and be part of the experience
We’re working together with our speakers and partners to shape a set of in-depth sessions that build on the spirit of CMSCamp and reflect the topics the community cares about most.
If you’d like to be part of it, tickets for CMSCamp Mallorca 2026 are already available. Join early and help shape the conversations that will define the event.
AI agents are only as reliable as the content model beneath them. In this hands-on 2.5-hour workshop, you'll learn why multibrand content architectures break and why adding AI makes those failures worse. Then you'll fix it.You'll build a structured, relational content model in Hygraph that handles multiple brands, regions, and governance requirements, then connect it to an AI assistant via the Hygraph MCP Server to run real agentic operations: querying across brands, creating governed content entries, and exploring the boundaries that keep humans in control.Whether you're managing content for two brands or twenty, you'll leave with a clear framework for designing content systems that AI can actually work with and a practical understanding of what separates brittle AI workflows from trustworthy ones.
Kristy McDougal
Director of Solutions & Support
The term "CMS" once had a fairly clear meaning, mostly as a web CMS for page maintenance and delivery. Today, it covers much more: data modelling, editing, workflow, staging, delivery, integrations, and increasingly AI-supported content creation. Over time, more and more responsibilities have been absorbed into the CMS, until its central role in content architecture has become almost unquestioned.
AI changes that. It does not simply add new features; it challenges the structural role of the CMS itself. Which responsibilities still belong at the core of a content system? Which ones can be decoupled? Where does AI replace existing logic, reshape editorial workflows, or introduce new dependencies and complexity?
The key question is no longer how to add AI to an existing CMS. It is whether the traditional CMS model is still the right structural foundation for modern content systems.This workshop offers a reality check on CMS architecture. Together, we will map classic CMS responsibilities against AI impact zones and examine what belongs in the architectural core of a content system today, what should move into more specialised services, and where AI can create real strategic value instead of additional overhead.
The workshop is hosted by Stefan Priebsch - thePHPcc
Stefan is a Software Success Consultant who helps organisations turn software investments into measurable business results by replacing architectural ambiguity and growing complexity with clear decision-making and robust technology strategies. He supports teams in dealing with rapid technological change, integrating AI into everyday work in ways that are practical and secure, and designing technology landscapes that enable growth while reducing risk.
Participants will leave with a clearer framework for evaluating historically grown CMS landscapes, reassessing architectural responsibilities, and making more conscious decisions about the future evolution of their content platforms. No tool talk, no salvation promises. Just a sober look at what a CMS should be responsible for in the age of AI.
One central change in Figma. Automatically updated and transferred directly into the CMS — including all defined effects on components, states, and output channels.
Five brands can look completely different while still being built on the same underlying system. New websites can be launched faster. Changes no longer need to be discussed and implemented hundreds of times. They are decided once, centrally, and rolled out everywhere in a controlled way.
Used consistently, a design system is therefore far more than a tool for visual consistency. It becomes the central control logic for digital platforms — and a powerful driver of speed, scalability, quality, and cost efficiency.
In this masterclass, we provide a comprehensive and accessible demonstration of the true potential of a consistently structured design system.
Even companies that already work with a design system usually leverage only a small part of its potential. Key relationships are often not addressed systematically, while inheritance mechanisms and automation are missing.
As a result, significant value remains untapped.
We show what design systems are truly capable of. Step by step, a fully integrated system emerges: from atoms, molecules, and organisms to their practical application within a digital platform.
“I’m a button — and I can trigger 450 different discussions.”
Everything that should remain identical is systematically connected. Differences are created intentionally through defined values — rather than uncontrolled copies, manual adjustments, and individual one-off solutions.
This results in:
• far less maintenance and coordination effort
• significantly greater consistency
• manageable technical complexity
• reliable quality and testability
• faster continuous development
• significantly lower operating and development costs
Using a real-world example, we demonstrate how brands with very different visual identities can be based on shared components, which properties are centrally shared, and which values are deliberately defined for each individual brand.
This makes it clear how functionality only needs to be developed and tested once, while each brand retains its own distinct visual identity. The company can control its digital platform down to the smallest detail while remaining flexible enough to respond to new requirements, websites, and brands.
“Figma-to-CMS Pipeline”?
The transition from design to technology is particularly exciting. Using our “Figma-to-CMS Pipeline,” we demonstrate how changes made in Figma can be transferred automatically into the CMS design system. We explain which information is transferred, how it is processed technically, and how design and development become part of one integrated process.
We demonstrate the technical implementation partly through general principles and partly using Neos CMS as a practical example. However, the principles, ideas, and tools presented are relevant regardless of the CMS being used. They can also be applied to TYPO3 and other modern content management systems.
At the heart of the masterclass is one fundamental question: How should a design system be structured so that a company can continuously develop its digital platforms in a manageable, scalable, and cost-effective way?
The masterclass is led by Sven Ditz, Managing Director of sitegeist, and Martin Ficzel, Neos core developer at sitegeist. Alongside insights, inspiration, and practical examples, the instructors will also dedicate time at the end to individual questions, discussions, and conversations about participants’ own design system challenges.
Anyone managing multiple websites, platforms, or brands who wants to do more than simply document their design system — and instead use it as a truly systematic foundation — should not miss this masterclass.