Roadmap for TYPO3 v14 — the High-Level Objectives and Strategic Goals

Basing the roadmap on research is in accordance with our goal to make fact-based decisions (Strategic Goal 6). The roadmap is no longer based on what the Core Team Lead thinks is necessary, but rather on what research shows must be done.

Along the way to TYPO3 v14, you will also see changes to how we enable contribution and innovation, and look at the development of TYPO3 CMS as collaboration in fields beyond just code. This is a part of our goal to establish governance (Strategic Goal 5). The Product Strategy Group will elaborate on that in a future article.

In total, there are ten strategic goals. TYPO3 v14 will not bring us all the way, but the roadmap takes steps on the way to the remaining eight goals by addressing the product itself:

• Strategic Goal 1 — Target Customer Groups: TYPO3’s focus for the upcoming years has to be on the public sector and small to medium enterprises.
• Strategic Goal 2 — Reducing Complexity: TYPO3 should offer a modern and consistent user interface, self-explanatory workflows, and clear and unified best practices.
• Strategic Goal 3 — Enabling Better Content: TYPO3 should efficiently integrate with external tools, enhance content creation experience and in system management and health monitoring.
• Strategic Goal 4 — Improve Customer-Oriented Communication: Better backend user experience through clear best practices and in-system support.
• Strategic Goal 7 — Improve Interconnectivity: Expanding TYPO3's integration capabilities and allow effortless connections with popular systems through user-friendly integration processes.
• Strategic Goal 8 — Give Customers High ROI Through Long-Term Support and Easy Maintenance: By offering long-term support, straightforward maintenance and updates, TYPO3 should promote updates and security, accessible and less costly.
• Strategic Goal 9 — Support Customer and Agency Success: Clearly defined communication and feedback channels as well as official and central marketing and sales support assets.
• Strategic Goal 10 — Improve Scalability: Use IT resources more efficiently. Scalability and compatibility with diverse cloud, on-premise and shared-hosting environments to optimize the operational efficiency.

The Product Strategy Group has selected six high-level objectives for TYPO3 v14. The details will be ironed out over the next months, but contributors and contributions are already welcome. If you see an area where you would like to contribute, please feel free to contact us, and we will include you in the process.

Roadmap Objective 1 — User Experience (UX) Improvements

TYPO3 v14 will come with a modernized backend user interface with a fresh look and feel, optimized for speed and usability. It should have a clear and intuitive interface, built for editors and marketers with varying levels of technical expertise.

We will automate repetitive tasks and eliminate unnecessary steps in the page editing and preview workflow, so that editors can create appealing web pages efficiently. Content translation and permission setting workflows will become easier.

Roadmap Objective 2 — Themes, Standardization, and Best Practices

We will provide ready-to-use page templates, new reusable components, and streamlined workflows that avoid unnecessary steps.

TYPO3 v14 will ship with a default theme out of the box. In addition, the long-awaited support for reusable themes will be added. We will build on the concepts of Site Sets and Content Blocks to create themes that can be reused across multiple projects without complex configuration.

We will also continue to streamline TYPO3’s Core APIs to ensure that the CMS itself also follows the best practices.

Roadmap Objective 3 — Lowering the Entry Barrier

We will improve the user experience during installation, so that a quick install to evaluate the product will be possible for any newcomer.

With TYPO3, there are many ways to achieve the same objective. But which one is best? TYPO3 should guide you and give you best-practice recommendations. This means we will revive and define best practices for tasks like setting up the CMS, running it in a clustered cloud environment, and building custom extensions or content types. This means a huge overhaul in the official documentation. We will also provide you with tools and helpers to avoid roadblocks to getting a new site up and running.

Roadmap Objective 4 — Easier Migration and Upgrades

Upgrading from TYPO3 v13 to v14 will be super easy: We will make system upgrades straightforward and low-risk, with clear documentation and automated processes. We will provide documentation to smoothen migrations and teach how to use new features and good practices.

Roadmap Objective 5 — GenAI Toolbox

TYPO3 v14 will be AI-ready, and include the flexibility we all love about our CMS. TYPO3 v14 will provide APIs that enable external artificial intelligence services to support editors when creating, managing, publishing, and rendering content.

Roadmap Objective 6 — Marketing and Customer Acquisition

Agency differentiation and sales support will play a central role in the adoption of TYPO3 v14.

The TYPO3 Partner program will be developed to help agencies showcase their technical expertise and stand out from marketing-focused competitors.

It should be easier for customers to find an agency that matches their needs and requirements, such as location and project portfolio.

We will create resources, such as presentations, case studies, and ROI calculators, that can help agencies sway prospective clients. Resources optimized for specific regions will improve sales to local clients.

Will this roadmap make all your dreams come true? Probably not all of them, and we make no guarantees. However, with your help we will get much further!

Send an email if you would like to help out, either with anything we throw at you — or with a specific contribution related to your dream feature.

Of course, we still need to work together and not spread our resources too thin. The Product Strategy Group has final word on what features should be worked on, and by whom. But if you’re willing — coding or otherwise — we want you on our list!