TYPO3 as a Framework

This item was not updated in last three versions of the Radar. Should it have appeared in one of the more recent editions, there is a good chance it remains pertinent. However, if the item dates back further, its relevance may have diminished and our current evaluation could vary. Regrettably, our capacity to consistently revisit items from past Radar editions is limited.

Mar 2018

Hold

We should avoid building new projects around TYPO3 by default. A lot of past projects started with CMS-only features in the beginning, and, for example, developed toward highly customized E-Commerce platforms. Instead of rearranging the architecture in a useful way, functionality was built on top of TYPO3's core and its extension framework Extbase. In the context of larger projects, this lead to deployment monoliths and the inability to integrate new technologies.

While in the past it was easy to kickstart a TYPO3 project with DCX's custom-tailored kickstarter, we now have a lot of knowledge and tools available to start projects with a much smarter architecture. This does not mean you shouldn't use TYPO3 anymore, but use it as the tool it is: a content management system.