Unassigned Talks
We, open source developers, AI proletarians
Generative AI can produce code, but is code the most important achievement of an open source community? In this presentation, I will analyze why the AI era threatens the very foundations of our identity, both as individual contributors and as a community.
Back to the free open and decentralized web!
In this presentation, I will introduce you to In-Folio, a web publishing platform for the Fediverse. It is a personal initiative aimed at enabling non-developers to freely publish web pages, without relying on services from major corporations that eventually makes users feeling ashamed to use it.
Privacy Forms Studio: Next-Generation Forms in Plone: Privacy-First, Secure, and Powered by SurveyJS
Forms are a core part of many Plone projects: contact forms, registrations, applications, surveys, internal workflows, and structured data collection. Existing solutions such as PloneFormGen and collective.easyform have served the community well, but modern projects often need richer form logic, better usability, stronger privacy guarantees, cleaner storage models, and more flexible integrations. This talk presents Privacy Forms Studio, a new SurveyJS-based approach to building modern forms in Plone.
Why Wouldn't You?
We've all received a feedback email we didn't enjoy. The one where someone tells you, in no uncertain terms, exactly what they think of something you built. It stings. Not because it's personal, but because somewhere in the back of your mind, you wonder if they're right. This talk is about the person on the other end of that email. The communications manager. The person who got voluntold into managing the website. The one who logs in, tries to do the thing, and quietly concludes that they must be the problem. They aren't. But we sometimes build like they are. When you've spent twenty years building Plone sites for nonprofits and educational institutions (organisations where the editor is rarely a developer and always under-resourced), that gap between a tool that works and a tool someone is glad to use stops feeling abstract. This talk focuses on the question I try to ask on every build now, and what becomes possible when you start asking it too.
Open Source, Open Partnership: Building NITheCS on Plone and Volto
When NITheCS came to us, Prof Francesco Petruccione, the director, knew three things. He wanted Plone. He wanted open source. And he wanted a site that would grow with the institute into whatever it needed to become. He had a direction, and a willingness to figure out the rest with us. That turned out to be the best possible starting point. We are Karel Calitz and Alex Zeeman from Juizi, a South African agency that builds Plone and Volto sites for nonprofits, research institutions, and educational organisations. This is a case study of what we built for NITheCS, but more than that, it is about what becomes possible when a client treats their website as something worth investing in, and stays in the room while it takes shape. We will walk through the Volto extensions we developed, how each one grew out of a real need rather than a spec sheet, and what the collaboration looked like from both sides. The requirements got clearer. The ideas got bolder. And the work was better, and a lot more enjoyable, for it. If you have ever wished your clients cared about their sites as much as you do, this talk is what that looks like, and what it makes possible
Of Digital Sovereignty, Video Portals at the University, and Plone
"This talk describes two complex and critical Plone 6 based services for University of Jyväskylä. Moniviestin - Our recently renewed video platform with over 23 years of history behind it and a fresh migration done from Plone 4.3 to Plone 6. How can we safely and gradually move 65 000 videos from one system to another? Researchvideo with MyJYU AI Translation - Our secure media platform on Plone 6 for sensitive research material since 2024, now integrated with our mobile app for recordings. What kind of feedback our researchers have given and how we have improved the system? Through those use cases I will discuss the role of Plone for users and developers in these services, and the ever more important aspect of maintaining digital sovereignty over your data and your software, and how open source software can help you achieve that. In addition, our university is going through a merging process with Jamk University of Applied Sciences in Jyväskylä, and I am looking at how this might affect our own video platforms' future. Keywords: Plone 6, Volto, security, video, open source, digital sovereignty, university, public sector.
An Overview of the Authentication and Authorization Landscape
Modern enterprise and academic IT environments demand robust, scalable, and secure identity management. However, navigating the rapidly evolving Authentication and Authorization Infrastructure (AAI) landscape can be overwhelming. This conceptual, low-code presentation delivers a comprehensive architectural guide to modern identity and access frameworks from an architect perspective. We will trace the evolution of the AAA system (from HTTP-Basic, LDAP, and SAML to modern OIDC, OAuth2, and OID4VP) and evaluate the shifting paradigms of both identity verification and access control, including group memberships and entitlements. The session covers key concepts like Federated Identity (eduGAIN, SAML/OpenID Federation) and cloud/on-premise IdPs like Shibboleth and Keycloak, alongside current regulatory and governmental standards such as BundID, EU Login, and eIDAS 2.0. Additionally, we will contrast MFA security, evaluating modern MFA approaches like OTP, Passkeys, and EUDI Wallet PIDs. For each strategy, we will weigh the architectural pros and cons while highlighting existing integration pathways within the Python, FastAPI, and Plone ecosystems. Designed for architects, decision-makers, and developers, this session provides the strategic insights needed to build future-proof, compliant identity setups
What has Plone Marketing been up this year - what you’ve all been dying to know
So, what’s been happening in Plone Marketing since the last Plone Conference? Things are progressing well. We are getting the hard work by the developers noticed globally and championing the open source ecosystem. Come see the faces in our team - all volunteers doing this in their spare time - hear the stories, and maybe even catch a little behind-the-scenes stuff.
Community Recognition Program: What? Why? How?
The Plone ecosystem thrives on the incredible dedication of our worldwide community. The Community Recognition Program was established to publicly recognize the invaluable work that individuals and organizations do for the benefit of the Plone Community. A core principle of this program is that the volunteering of time and resources is just as critical to our long-term success as financial support. By valuing community, and code contributions, we proudly highlight Plone's identity as a true open-source project backed by a diverse, global network of supporters rather than a single company.
Plone on Kubernetes - conditions were cloudy
Plone on Kubernetes — Why you want it, what was missing, and what I built to make it thrive Running Plone in a container is easy. Running it well on Kubernetes — with replicas, rolling updates, autoscalers and PostgreSQL underneath instead of a lonely Data.fs — is a different game. Over the last while I've been rebuilding the pieces one by one under a single umbrella: Cloudbrine, the cloud-native PostgreSQL ZODB/Plone ecosystem. This is the 25-minute bird's-eye tour of the whole thing.
Have a nice and productive day?
Every morning starts with the same wish: "Have a nice and productive day!" Yet somehow the day often turns into a parade of changing requirements, misunderstood tickets, unexpected bugs, last-minute deployments, and the occasional "it works on my machine." Through a series of humorous, exaggerated scenes inspired by real Plone projects, we'll explore the everyday challenges between developers, project managers, and QA. After each scene, we'll discuss practical techniques that helped our team communicate better, reduce friction, and make projects run more smoothly. This talk isn't about blaming roles—it's about understanding each other's perspectives and finding simple ways to make collaboration more productive. Expect laughs, familiar situations, and hopefully a few ideas you'll take back to your own team.
Talking to Plone: Building an MCP Server for AI-Assisted Content Management
Large language models are getting good at using tools — but they need a bridge to your CMS. The Model Context Protocol (MCP) is that bridge, and plone-mcp is an open-source MCP server that lets AI clients like Claude Desktop manage a Plone site through its REST API. We'll cover what becomes possible when an LLM can create and edit content, assemble Volto blocks, run searches, drive workflow transitions and do translations — all through natural language. After a live demo (building multilingual pages, composing block layouts, publishing), we'll open up the architecture: how the server maps MCP's tools/resources/prompts primitives onto the Plone REST API, key design decisions like the block-layout preparation pattern, and where the rough edges still are. You'll leave knowing what MCP is, how it fits Plone, how AI-assisted editing could reshape content work — and how to try it and contribute.
Intranets in Plone - Experiences from the last year
Over the last few years, we at kitconcept have been working on multiple intranet projects and even developed the dedicated kitconcept.intranet distribution for those. In the talk I will show some of the problems we encountered while working on this projects, how we solved them and how we implemented the lessons learned into the kitconcept.intranet distribution.
Why We Rebuilt the Wheel: cs_dynamicpages and the Case for Behavior-Driven Classic Layouts
The Plone ecosystem does not need another page-composition tool. For years, we've had plone.app.mosaic. More recently, tools like collective.contentsections have offered a cleaner, content-tree-based alternative. But... after seeing so many page composition tools at 2025 Conference, we did what any Plone agency does: we built another option. cs_dynamicpages is our open-source attempt to bring a flexible, Volto-like block editing experience to Plone 6 Classic UI, but by leaning entirely on Plone's native assets: Dexterity Behaviors and standard ZCML views
How to maintain Python packages to attract free and open source software contributors
Placeholder. Will complete after return home from vacation on Aug 4. For evaluation, I'll focus on how the icalendar team encourages contributions from first-timers and experienced developers. I'll touch on topics including: - Documentation of how to contribute - Handling AI slop - Funding contributions - Automating the boring stuff
The state of Plone Volto and Plone Aurora
Join Piero and Víctor for an update on the current state of Plone's React frontend ecosystem. In the first part of the talk, we'll review the progress made in Volto over the past year and a half, culminating in the release of Volto 19. We'll cover the most significant new features, improvements, and what they mean for developers and integrators working with Plone 6. In the second part, we'll turn our attention to Aurora, the new React-based frontend being developed by the community for Plone 7. Started in 2024, Aurora embraces the latest React ecosystem and modern web development practices while building on the experience gained with Volto. We'll present its current status, architecture, key technologies, and roadmap toward becoming the next-generation frontend for Plone. Whether you're maintaining existing Volto projects or looking ahead to the future of Plone, this session will give you a comprehensive overview of where we are today and what's coming next.
Multilingual Nick: Translations That Have to Survive an Audit
In a Plone translation catalogue shipping today there is a string that asserts something its source does not — placeholder counts match, length is normal, every automated check passes, and only a human reading it would notice. If translations ever have to carry legal weight — and in the EU, safety information must, in up to 23 official languages — that is exactly the class of bug that matters. For more than a year I have run Nick and Volto in production as the backend and frontend of a regulated-documentation platform: 358,627 translations across 71 languages in one database-backed model — merged into Nick through the release team in June 2026 — guarded by a meaning-drift detector that structural QC cannot replace, with the AI kept on local hardware as a written architectural rule, not a preference. This talk is what a year of running that stack for real taught me, including the failures I paid for — and it ends with a question I want the room's answer to: how an AI-assisted corpus should live alongside Weblate.
From Regulation to Evidence: Building Compliance on Nick
Most compliance systems begin with documents, and most of them end as document graveyards. The relationships are what matter, and folders cannot express them. A regulation imposes an obligation. A policy interprets it. A control implements the policy. A risk assessment determines where the control is needed. Evidence demonstrates that the control exists and still operates. Break any link and an auditor's question — show me why this control exists, and prove it worked — has no answer.
Deploy multiple Volto sites with one backend.
You may have a friend who asks if you can make a small website for his bakery. Or your sports club or church is using Wordpress or some ugly site builder, or some overpriced and overpromising solution. You know what you need to do. But isn't Plone overkill for such small sites? Don't you need a bit too many Docker images and complex GitHub Actions workflows? No. Here is what I am trying out: - A cookieplone project as base - One Python backend container with multiple Plone sites - One Volto frontend container per site, same image. Yes, you can have some CSS per site. - Let GitHub Actions create the images - Start the remote deployment from your local computer
Storytelling Agent: How AI Agents Build Pages in Volto on Their Own
Last year at Interaktiv, we introduced the Prompt Tool, an early step into AI-supported editing. The Prompt Tool helps editors rewrite text according to predefined rules. However, this approach doesn't allow for the kind of comprehensive, agentic work with AI that has become popular in software development, for example. To get there, AI needs to be able to edit not just content, but also the structure of a CMS's pages. To share our vision for the future of editorial work in CMS, we want to present an AI system that does exactly that: the Storytelling Agent. This agent is based on modern LLMs, understands Volto's block logic, and its work can be observed in real time. In our presentation, we'll show: - Our new add-on that gives the agent a home in Volto - Building a new page from a PDF document - Refining an existing page according to editorial guidelines We invite you to join us in discovering the future of CMS.
The Migration You Can Watch: A Live Orchestrator for Classic Plone to Volto
Migrating a classic Plone site to Plone 6 with Volto means more than moving records from one database to another. Free RichText HTML has to become structured Volto blocks, and that conversion is easy to get wrong quietly. At Interaktiv we built a live Migration Monitor that makes the whole pipeline visible in one place. It drives export, transform and import, and streams the run to a realtime dashboard: a visual map of which content types land where, throughput in objects per second, and what's already migrated versus what's still open. The most useful view sits at the end: an A/B comparison that puts the old page next to the migrated one, side by side, with a field level diff. You can finally see that the content survived. Export and import build on collective.exportimport, used as intended. What is new is the live orchestration, the monitoring pipeline and the A/B validation on top of it. The toolkit is alpha and still moving. We will show the architecture, how HTML turns into Volto blocks, and a live demo from the Monitor with the A/B comparison as the finale.
Stop writing manuals nobody reads: recording AI-assisted guided tours in Plone 6
Every Plone project ends the same way: hundreds of occasional editors, a CMS they touch twice a year, and a PDF manual nobody reads. Training doesn't scale, support tickets pile up for the same three questions, and static documentation is outdated the moment the UI changes. We built a different answer: guided, in-CMS onboarding for Plone 6 and Volto. Instead of digging through a wiki or waiting for a colleague, editors get contextual, step-by-step tours right where they work — the moment they need them, in the exact screen they're stuck on. The real shift is in authoring: tours are recorded by clicking through the actual task, not written by hand — so tours stay cheap enough to update every time the UI changes, instead of rotting like the PDF ever did. Stable selectors are generated automatically. An AI assistant then drafts the step texts from the recorded context, in the editor's own language — while zero page content or user data is sent to the AI provider. This talk walks through the architecture, the hard parts, the privacy-by-design AI integration, and lessons from real editor onboarding — including what changed for editors' confidence and for the support load once tours replaced the manual. Live demo included.
Nothing Leaves the Page: A Privacy-First SEO & Accessibility Assistant for Volto
Most SEO tools share one uncomfortable habit: they send your content to someone else's servers. For organisations in the public sector, healthcare, or education, that's not a minor inconvenience — it's a real problem. We took a different route. The interaktiv SEO-Check Lite is a Plone 6 / Volto add-on that runs entirely in the editor's browser. No AI, no external service, no API calls to third parties. Nothing leaves the page. It lives as a floating badge right inside the editorial workflow, on the page your team is already editing. One tool covers two jobs that are usually split apart: core on-page SEO metrics (meta description, titles, internal links, a pixel-accurate Google snippet preview) and concrete WCAG accessibility checks (alt texts, link texts, table headers, heading hierarchy). Every check is deterministic and produces a transparent, CI-style score — no black box, no model to second-guess. Everything is configurable without code, and the add-on is a project-independent drop-in for Volto sites.