Composer and TYPO3 have had a long journey together. Now, work done in v11 is paving the way for v12—so that TYPO3 can become a fully-realized standard Composer project and consequently, an even more secure CMS.
One of TYPO3’s most successful and powerful features is the so-called “Page Tree”. At its heart, it’s representing the structure of a web site or application in a node-structure which most people know from Windows Explorer or Mac Finder. It has a hierarchical layout and allows to quickly blaze through a websites’ structure as an editor.
TYPO3’s Page Tree has been improved over the past years. In fact: My very first code contribution for TYPO3 Core was to re-load only parts of the TYPO3 Page Tree in TYPO3 4.1 back in 2006. The latest iteration was a SVG-based tree which was introduced in TYPO3 v9 back in 2018.
At b13, we’re working with TYPO3 every day, and we've found room for improvements. But “fix” something from a developer side isn't enough: One needs to think as an editor, and see all the implications that might be.
My colleague Laura started to draft a concept about an improved TYPO3 Page Tree, which you can now dive into and read while sipping a cup of tea.
Read our UX concept as a proposal for the TYPO3 Page Tree, and share your feedback via Twitter.
Composer and TYPO3 have had a long journey together. Now, work done in v11 is paving the way for v12—so that TYPO3 can become a fully-realized standard Composer project and consequently, an even more secure CMS.
In 2021, many individuals and companies sponsored bug fixes and new features in TYPO3. We’re grateful for their support!
I’m pretty sure that the new Folder Tree in TYPO3 v11.1 feature will make editors daily lives with TYPO3 easier.
Let's see if we can improve TYPO3's Page Tree, from a non-developer perspective
Welcome to Core Insights by b13 - what is this place?