Beyond The CMS #44 - Chris Bryce (Dotfusion) with Derk Majoewskij (Storyblok)
Beyond the CMS - A Content Management PodcastShow Notes
Derk Majoewskij is Senior Product Strategist at Storyblok, where he leads product discovery and roadmap prioritisation across the full product cycle. In four-plus years at the company he has worked across product management and product marketing, shipping features end-to-end from problem discovery through engineering delivery to go-to-market. He was the primary voice behind FlowMotion, Storyblok's native automation and orchestration layer built on n8n, and has been closely involved in Storyblok's AI direction including the MCP server and the Strata semantic vector layer.
The conversation starts where most CMS conversations don't: not at the platform decision, but at what happens to content after the site goes live. Derk and Chris dig into the gap between a CMS that holds content and one that actively operates it, and why that distinction is becoming the difference between brands that show up in AI-driven search and those that don't. Derk frames it directly: content used to be static and humans made every change. The shift underway moves the human into a loop where agents, automation, and semantic indexing do the operational work.
Chris walks through Dotfusion's own 140-node agentic content workflow, from AEO-informed topic selection through research, writing, governance, schema refactoring, and social distribution, all orchestrated through n8n and Storyblok. Together they cover the real upfront cost of building AI content infrastructure properly, why automation native to the CMS handles enterprise IT requirements that external tools can't, and how voice-to-content workflows are already running in production for franchise and retail clients.
Key topics include: FlowMotion: Storyblok's n8n-based automation layer, built natively inside the CMS with custom Storyblok triggers and actions already in place. One publish event can trigger translation, republishing, and a Slack notification with no external setup required — and no IT overhead for enterprise teams. Strata: Storyblok's built-in vector database, in active development, that makes an entire content history semantically readable by AI tools rather than just keyword-searchable. Essential for any brand managing GEO visibility across years of published content. MCP Server: Storyblok's Model Context Protocol integration that connects AI models directly to a Storyblok space, enabling natural language content operations, story search, and content updates without leaving the platform. The 25x rule: Building AI content infrastructure properly takes roughly 25 times longer than writing a single post. The argument is that teams investing now build a permanent operational advantage that compounds while others are still starting. Living vs. static content: Derk's framework for the shift from a CMS where humans manage every update to one where content is automatically updated, optimised for AI search, and made semantically available to agents while the human remains in the loop. Voice-to-content in production: How franchise and retail brands are using a phone, a store ambassador, and a FlowMotion governance model to turn raw audio captured on the floor into polished, on-brand content without stripping the authentic voice out of it.
The infrastructure decision you make now about your CMS determines whether your team is spending its time on strategy or on operations, and whether your content is visible to AI tools or invisible to them.
🎧 Listen now and join the conversation!
More from Beyond the CMS - A Content Management Podcast
What happens when website search evolves from a keyword box into an intelligent interface? In Episode 50 of Beyond the CMS, Chris Bryce speaks with Olivier Dobberkau, CEO and founder of dkd Internet Service GmbH and president of the TYPO3 Association, about how enterprise search is moving from keyword matching toward semantic search, retrieval-augmented generation (RAG), conversational experiences and agent-readable interfaces. Olivier explains why AI search begins with content quality, metadata and retrieval. They discuss Apache Solr for TYPO3, embeddings, document chunking, grounding, hallucination risks, search feedback and the difference between a generic chatbot and specialized search capabilities routed by user intent. In this episode: Why search is becoming an interface rather than only a search box How keyword search differs from semantic search and RAG How Apache Solr supports TYPO3 search Why poor content creates poor AI-search results How chunking can remove important context Why specialized search capabilities can outperform generic chatbots How real questions, zero-result searches and user feedback improve retrieval Why organizations should repair content before adding generated answers Chapters 0:00 Welcome to Beyond the CMS Episode 50 2:06 Olivier Dobberkau, dkd and the TYPO3 ecosystem 5:32 Apache Solr search for TYPO3 7:23 Why search is becoming the interface 11:21 From keywords to conversational and agentic search 13:47 Content quality, grounding and search quality 19:46 Why chatbots are not always the right experience 22:37 Specialized search capabilities and intent routing 24:02 Question-based website search in practice 26:19 Repairing content before adding RAG 28:33 Retrieval, metadata, feedback and supervision 31:25 RAG explained: indexing, embeddings and retrieval 34:16 Chunking, context and grounded answers 36:39 Open source, access and the TYPO3 community About Olivier Dobberkau Olivier Dobberkau is CEO and founder of dkd Internet Service GmbH and president of the TYPO3 Association. His work spans open-source CMS development, TYPO3 search, Apache Solr and the transition from keyword search toward intelligent content discovery. Connect with Olivier on LinkedIn Learn about dkd's TYPO3 work Learn about Dotfusion
Most accessibility tools tell you what is broken. Limena helps teams understand which accessibility barriers are disrupting valuable customer journeys, what those failures may be costing the business, and who owns the fix. Ryan Short, founder of Limena, joins Chris Bryce to explain how accessibility intelligence turns a long list of WCAG failures into business priorities. Limena connects accessibility barriers to customer journeys, conversion points, organizational ownership, and continuous verification. They discuss: Why accessibility work keeps losing to the product backlog How to connect accessibility barriers to customer journeys and revenue How Limena prioritizes issues by business impact Why closing a development ticket does not prove the barrier is gone Why widgets and point-in-time audits are not enough Where accessibility overlaps with SEO, AEO, and content quality How Limena fits into Git-based and composable delivery workflows Watch the episode: YouTube Learn more about Limena: limena.app Connect with Ryan: LinkedIn Learn more about Dotfusion: dotfusion.com
McGill University runs a thousand sites on its central platform, 500 more custom builds, and tracks 6,000 to 8,000 content edits a week. Joyce Peralta, Manager of Digital Communications at McGill, joins Chris Bryce to talk about the content model project addressing all of it. The number that anchors this conversation: 61 different terms used across the university for the exact same program component. Joyce's central point is that AI does not cause content inconsistency, it amplifies inconsistency that already exists. The inaccuracy people see in AI answers comes from information presented differently across websites, not from information that is wrong. McGill looked at building a separate content repository just for AI and turned it down, because a second repository means a second governance and synchronization problem. Joyce points to Dries Buytaert's markdown experiment, which found AI bots still hit the website itself the majority of the time. The content model work is federated across about 50 subject matter experts from departments across the university. Rollout runs concept by concept, with a timeline Joyce estimates at five years or more. Her real point on success: this cannot be a Communications project or an IT project alone, it has to be both working as one team, with alignment across the whole institution. Also in this one: the student usability panel that tracks how AI use among students changes year over year, why Drupal and the Drupal EDU Slack group are a real source of leverage, and what a taxonomy problem looks like at university scale. Chapters 0:00 Welcome to Episode 48 1:05 Meet Joyce Peralta, McGill University 1:38 The velocity of change since Beyond the CMS launched 2:35 Inside McGill's web services team: comms and IT as one team 4:12 Who owns the university's content model 5:56 The vision behind McGill's content transformation 9:34 Taxonomy at scale: a thousand sites, 500 custom builds, 6,000 to 8,000 edits a week 14:33 Federated with 50 subject matter experts: the 61-term problem 16:19 AI amplifies inconsistency, it does not cause it 17:19 Why McGill rejected a separate AI-only content repository 19:10 How McGill actually uses AI in the content model project 21:35 Concept by concept: a rollout Joyce estimates at five years or more 24:02 Open source, Drupal, and the Drupal EDU Slack group 26:49 Three feedback groups, including the student usability panel 29:50 The human side of technology as AI reshapes expectations 31:32 Lessons for higher ed teams just starting this work 33:38 Where to find higher ed thought leadership 34:52 Wrap-up Click here to watch a video of this episode.
Enterprise content supply chains run 15 to 19 steps. Joel Varty, CTO of Agility CMS, thinks AI can get that down to six, so people are the only bottlenecks left. Chris Bryce and Joel dig into the MCP server that connects Claude directly to your CMS and kills the copy-paste layer of content operations. Joel has spent 21 years building Agility, the Canadian headless CMS behind Cineplex, Scotiabank country sites, school boards, and higher education. He explains why Agility deliberately did not build an AI agent inside the CMS, and instead meets teams inside the AI they already use: Claude, Copilot, or Gemini. The MCP server now runs the full loop: content models for developers, a content pipeline that pushes up to 250 items per batch, and bulk publish, unpublish, and delete. Plus metadata vs JSON-LD schema in plain language, AEO, blogging from a phone with a Claude project, and content ops through a CLI for regulated industries that need sign-off and audit logs. Click here to watch a video of this episode.
Most enterprise sites are not ready to be found by AI search, and the fix starts before you ever migrate. Chris Bryce talks with Joel Goodman, VP of Growth Strategy at Squiz, about content intelligence, query fanout, and what makes a composable DXP AI-ready. Joel spent 13 years running an agency in higher education before joining Squiz, a 26-year-old Digital Experience Platform built in Australia with a growing North American presence. We get into what makes Squiz different from a traditional headless CMS, why accessibility is now the same problem as AI discoverability, and how Squiz Content Intelligence audits your content the way an AI search engine reads it. The sharpest idea: query fanout. Ask one question in ChatGPT and it breaks into 40, 50, sometimes 60 sub-queries your content has to answer, queries you never see. Click here to watch a video of this episode.