TYPO3 v14: It’s Just the Beginning

To ground decisions in real user insight, we turned to the community. The TYPO3 Marketing Team ran a Sales Enablement Survey. Our Product Strategy Group interviewed editors. And one thing’s clear: no one can agree on exactly what we need, or what the current state of TYPO3 actually is.

After receiving feedback like Let’s Start from Scratch! (a random TYPO3 developer, someplace sometime) and I like that TYPO3 works the same way as 20 years ago! (definitely not me), we concluded it would be difficult to keep our full community happy with whatever changes we make.

In open source—especially in a framework as flexible as TYPO3—it’s natural that people use the system in many different ways, so we can’t always meet every competing priority at once. But four clear themes emerged, all grounded in a sense that TYPO3 can be overly complex and uncomfortable to use. Here’s what came up:

1. Improved backend user experience
2. Development that puts APIs first
3. Built-in themes and ready-to-go frontend 
4. Easier integrations

A modernized backend with a focus on usability and visual clarity. While we wish, as always, to refrain from chasing trends, we recognize that intuitive interfaces make for an easier backend experience. Visual updates include a new design system, lighter icons, rounded corners, and a re-arrangement of backend modules and labels. We’ve also enabled quick actions and contextual editing.

Developer-centric API improvements enable smoother integrations and a cleaner architecture—building a strong foundation ready for headless or composable approaches. We could list the specific features

• XLIFF2, 
• new TCA types, 
• new APIs, 
• Fluid5, 
• more PSR-14 events, 
• improved Scheduler, 
• an AI toolbox, 
• a QR Code Module, 
• improved translation workflow,
• …

But who’s counting? (We are: there are over a hundred.)

The first default theme brings you a ready-to-use frontend so you don’t have to build one in addition to your backend development work. Camino comes in four color variants and uses the same modernized visual elements we included in the backend interface.