AJR/TechRadarAJR
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added articles in markdown

Browse Source 
Added all (missing) current articles of each quadrant.
This commit is contained in:
Philip Feldmann
2017-04-04 17:22:21 +02:00
parent 67b1b9e944
commit 461c4e7dda
62 changed files with 763 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
radar/2017-03-01/typo3-as-a-framework.md Normal file
View File

@@ -0,0 +1,11 @@
---
title: "Typo3 as a Framework"
ring: hold
quadrant: tools
---
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 AOE'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.