TYPO3 Developer Days 2026

Same Content,
Different CMS

Susi Moog T3DD26 · August 2026

“

CMS? That’s a trivial problem.
Even Hybris has one built in.

— A colleague, Hybris (now SAP Commerce), ~2015

A few years back I was at lunch with a colleague from Hybris — which most of you probably know today as SAP Commerce. We got to talking about content management, and he said — more or less — "CMS? That's a trivial problem. Even Hybris has one built in." So I asked him to show me. [pause] It was a text field. Per page. Not a WYSIWYG, no media library, no multi-language. One text field per page. [pause — let the room react] Now — to be fair — for what Hybris was built for, that was probably enough. Nobody's buying industrial machinery because the hero banner copy was well-crafted. But that moment stayed with me. Because he wasn't wrong to call it a CMS. It solved a real problem for a real audience. It just wasn't built for our problems.

880+

content management systems

Most of us have looked at maybe three.
I looked at five.
Still 875 unexplored — but it’s a start.

The five systems

TYPO3 Enterprise CMS
Strapi Headless CMS
Pimcore DXP
Storyblok Headless + Visual Editor
Payload Code-first CMS

Five systems. Very briefly: TYPO3 — you know this one. Enterprise CMS, PHP, been around 25 years. Multi-language and access rights built in. Strapi — headless, Node.js, API-first. Editors work entirely in an admin panel with no visual preview. Pimcore — DXP, not just a CMS. CMS + PIM + DAM in one product. Austrian company, commercial licensing since 2023. Storyblok — headless but with a live visual editor. SaaS. The one where editors actually see what they're building. Payload — code-first, TypeScript. Schema defined entirely in code. Admin panel is auto-generated. That's all you need to know for now. We'll see each one in detail in the demos. Same 5 tasks per system - Create a new page & place it in the navigation - Add a hero section — headline, image, CTA button - Upload an image & add alt text - Add a German translation of the page headline - Find a published page, change a headline, republish

Let’s
find out.

Not a ranking. A map.

Live demo

Payload

Code-first CMS

shown live at the talk

Live demo

Strapi

Headless CMS

shown live at the talk

Live demo

Pimcore

DXP

shown live at the talk

Live demo

Storyblok

Headless + Visual Editor

shown live at the talk

Live demo

TYPO3

Enterprise CMS

shown live at the talk

Now what?

You’re going to keep
using TYPO3.

And that’s exactly the point. You just saw what’s possible elsewhere — now bring it back.

You're not going to switch to Storyblok after this talk. You're TYPO3 developers. You're going to keep using TYPO3. And that's exactly the point. You just spent the last hour watching other systems solve problems. Some of them solved those problems really well. TYPO3 is open source. That means you're not just a user — you're a potential contributor. Those ideas you just saw? They don't have to stay in other systems. Liked the visual editing experience in Storyblok? There's work happening on that in TYPO3. Get involved. Noticed somewhere that TYPO3 makes your editors work harder than they should? That's not a complaint — that's a bug report waiting to happen. Or an extension. Or a core patch. The best thing that can come out of a talk like this isn't "I should use a different CMS." It's "I know what good looks like now — and I'm going to help build it."

Every CMS solved at least one
problem brilliantly.

The question is whether you’re
learning from it — or ignoring it.

Even a text field per page taught someone something.

The person you’re building for

Your editor spends hours
every day in the system
you built.

They don’t know what TypoScript is.
They don’t care about the content model.
They just want to publish a page without calling you.

Before we close — one thing. The editor. The actual human being sitting in front of the system you built. They don't know what TypoScript is. They've never seen a TCA configuration. They don't know why the image upload works differently on this page than on that one. They just want to publish a page. Without calling you. Without filing a ticket. Without giving up and sending the content in an email instead. [pause] Every system we looked at today was built by developers, for a specific vision of what editing should feel like. Some got it right. Some didn't. You have the same choice in every project you build. Sit with your editor for five minutes before you call it done. Don't explain anything. Don't help. Just watch. That's it. That's the whole talk.

Same Content,Different CMS

The five systems

Now what?

The person you’re building for

Same Content,
Different CMS