{"id":3364,"date":"2013-11-13T09:40:05","date_gmt":"2013-11-13T08:40:05","guid":{"rendered":"https:\/\/roodlicht.com\/?p=3364"},"modified":"2013-12-06T11:53:27","modified_gmt":"2013-12-06T10:53:27","slug":"typo3-neos-or-typo3-cms","status":"publish","type":"post","link":"https:\/\/roodlicht.com\/en\/typo3-neos-or-typo3-cms\/3364","title":{"rendered":"TYPO3 Neos or TYPO3 CMS"},"content":{"rendered":"

[lead]<\/p>\n

Both TYPO3 Neos<\/strong> and TYPO3 CMS<\/a>\u00a0will be launched shortly. TYPO3 Neos on the 10th of December and TYPO3 CMS on the 25th of March 2014. It is for the first time that the TYPO3 community delivers two content management systems. But which CMS should you choose? Is that TYPO3 Neos or TYPO3 CMS? In this article we will try to help you make the right decision.<\/p>\n

[\/lead]<\/p>\n

Short overview TYPO3 Neos versus TYPO3 CMS<\/h2>\n

TYPO3 CMS<\/strong> is an Enterprise Content Management System which was first launched in 1999. In the Netherlands, this CMS is widely used by educational, broadcasting, governmental and enterprise level organisations and businesses. It has a large amount of expansion options, and already out-of-the-box it is a ready-made \u200b\u200bsolution. The CMS scores high in search results, and thanks to the logical structure most editors can quickly find their way into the package. A strict separation between layout, content and application ensures that each design is possible.<\/p>\n

\n
\n
\n
\n
\n
\n
TYPO3 Neos<\/strong> is the newest addition to the TYPO3 set of projects. It is not the replacement of TYPO3 CMS. It is another CMS. What is immediately striking about TYPO3 Neos is the in-page editing. An editor works directly in the website. One of the other key features of TYPO3 Neos is the usability for content editors. Every step in the content creation process has been reviewed if it is really necessary or if it could be automated. One of the results is that each operation is automatically saved without any required action of an editor. Also the preview does not rely on the opening of a new browser window anymore, in TYPO3 Neos it is like pushing aside a curtain. In terms of additional functionality however, TYPO3 Neos is still limited.<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

The architecture of Neos versus CMS<\/h2>\n

One of the big differences – and improvements – can be seen when we compare the architecture of Neos to CMS.<\/p>\n

[one_half]
\n\"typo3-cms-architectuur\"<\/a><\/p>\n

 <\/p>\n

TYPO3 CMS Architecture (diagram)<\/p>\n

[\/one_half]<\/p>\n

[one_half_last]
\n\"typo3-neos-architectuur\"<\/p>\n

TYPO3 Neos Architecture (diagram)<\/p>\n

[\/one_half_last]<\/p>\n

What you see in the diagrams above is the biggest difference between TYPO3 Neos and TYPO3 CMS. With TYPO3 CMS all functionality is placed on top of the CMS. These modules are called TYPO3 Extensions. In TYPO3 Neos all extra functionality are applications that are based on the Flow Framework. Each module is called a Flow Package. Authorisation and database connectivity is for both Neos and for the modules done through the Flow Framework. This makes the architecture of TYPO3 Neos also much more open than that of TYPO3 CMS. Moreover, with TYPO3 Neos it is possible to choose other databases like Oracle, PostgreSQL, SQL Server and more.<\/p>\n

For whom is TYPO3 Neos and for whom is TYPO3 CMS?<\/h2>\n

Both TYPO3 Neos and TYPO3 CMS focus on the enterprise level. TYPO3 CMS has been very succesful with all its enterprise use cases. Consider, for example, the international users as Sony, Sixt, and Volkswagen, to name just a few. TYPO3 Neos has yet to prove itself, although the knowledge and experience within the TYPO3 community comes in handy. Obviously both packages are also suitable for non-enterprise users. Especially when you look at the many qualities of TYPO3 Neos, it is also a great CMS to use for non-enterprise users.<\/p>\n

It’s striking to see that while we work with TYPO3 Neos in the test setups we’ve done at ROODlicht that TYPO3 Neos especially is a content management system with an extremely low entry for content editors. In fact, anyone looking for a solution without complexity for editors, chooses TYPO3 Neos. Or as Karen McGrane says:<\/p>\n

[dropcap style=”simple”]”[\/dropcap]…[TYPO3 is] the only firm that is really trying to tackle these problems head on with the real focus on what the author experience should be…” – Karen McGrane<\/a><\/p>\n

Which CMS should you choose, and when?<\/h2>\n

The choice for TYPO3 Neos or TYPO3 CMS is largely determined by what is currently possible. In TYPO3 CMS there is much possible, but with TYPO3 Neos this is all relatively limited. But still there are enough reasons left to make this a hard choice.<\/p>\n

[one_half]<\/p>\n

TYPO3 Neos<\/h3>\n