One Ecosystem, One Look: Completing the TYPO3 Visual Relaunch
The TYPO3 visual relaunch is complete. All 12 web properties — including the Symfony applications, extensions.typo3.org, and docs.typo3.org — now share a unified design language.
When we relaunched typo3.com, typo3.org, typo3.community, and news.typo3.com in November 2025, we set a new visual direction for the TYPO3 universe. At the time, the job was not finished. Eight more platforms were still running their own look and feel — functional, but visually disconnected from the rest. This update closes that gap.
One Design System, Twelve Platforms
During the main relaunch, it became clear how much friction comes from moving between TYPO3 services that feel like different websites. A developer jumping from the documentation to the Extension Repository to Forger to their certification exam should not feel like they are leaving the TYPO3 world. With this update, they no longer do.
The unified design language now covers the complete TYPO3 web ecosystem: intercept.typo3.com, reimbursement.typo3.com, elts.typo3.com, extensions.typo3.org, forger.typo3.com, my.typo3.org, exam.typo3.com, and docs.typo3.org.
The Final Phase of the Relaunch
No single platform caused major problems. The challenge was the accumulated variety of styles, templates, and UI patterns that had evolved independently over the years. The dashboard UI alone existed in four different versions across the Symfony applications. Harmonizing all of that took roughly three weeks of focused work.
extensions.typo3.org required the same careful approach: align the visuals without disrupting a platform that handles the entire TYPO3 extension ecosystem, deeply integrated with Solr for search.
docs.typo3.org: A Different Kind of Challenge
Of all twelve platforms, docs.typo3.org was the most distinctive to work with. It does not run on a conventional CMS or application backend — it renders documentation for the TYPO3 Core and thousands of extensions automatically from source repositories. Visual changes had to be introduced in a minimal, non-disruptive way within the rendering pipeline itself.
We will be exploring the changes, challenges, and lessons learned in a dedicated session at T3DD in Karlsruhe this year. Stay tuned — and if something looks off or you have feedback, drop a message in the TYPO3 Slack.
