1 Comment // Reading Time: 3 min.
For more than a month we have been working on the website at hand and filing all corners and edges in order to create a pretty and at the same time stable substructure. Due to our technical preference, the only choice for the CMS was the TYPO3 CMS - especially after the Neos team recently separated from the TYPO3 Association. As you may know, Neos was the previous system and we consciously decided against further use. At the end of this article, I'll talk briefly about the reasons.
In addition to the new technical substructure, we have screwed on many details of the existing layouts and partially adapted them to new concepts or simply made them look better. The website is of course - as before - completely usable on mobile devices in good quality. We attached great importance to designing the existing functions for further growth of the presence.
In particular, we have upgraded the OpenSource page and added many missing articles on our part. Have a look and maybe you will find one or the other pearl for your projects.
A further attention we put in particular on the news range and converted this with an internal Extension maintained by us. We hope that the use of Shariff for easier sharing via the social media channels as well as the integration of pw_comments for commenting appeals to you. Just give it a try! We are looking forward to any feedback.
Last but not least we have our own mascot now. The error case will reveal it. ;-)
The reason for our decision against Neos lies in a few points, which have pushed us however in the last months ever further in the direction of a technical relaunch. The most important point of criticism so far has been the stability and performance of Neos.
In principle, the website was fast and stable once everything had been installed and configured, but some tools for further optimization such as static caching and the merging of scripts were not feasible without major technical effort. In TYPO3 CMS we rely on the easy to use combination of the extensions nc_staticfilecache and scriptmerger to achieve our goals.
In addition, Neos has repeatedly prevented us from working with exceptions, data loss and various editor bugs. Unfortunately, this has partly led to the fact that new contents could not be put online as intended, much more complex or even only with workarounds. Partly this may have been due to our experience with the system. But since we had already been using Neos since a pre-1.0 version and the basic problems haven't changed much to this day, we don't regret the decision.
Further problems of Neos for us were the lack of many stable(!) standard extensions as there are for the TYPO3 CMS as well as the mostly unfortunately insufficient documentation. At this point, however, we don't want to reproach anybody, but only want to mention the points that led us to this decision. We continue to hope that Neos will go its way and create its own basis in the future. We will continue to support the CMS in the future by actively maintaining the integration of Neos TypoScript in our TypoScript plugin for the IntelliJ IDE.