Neos Without TYPO3—A Snapshot

Reading time: about 2 minutes

The Background

I can partly understand why this split has been in the works for some time and why some have even written that it had already happened long before the announcement. As co-leader of the TYPO3 Marketing Team and leader of the TYPO3 Design Team, I viewed this split with very mixed feelings. On the one hand, of course, because our teams had just spent half a year working intensively to better align the brands with one another and to revamp the communication strategy surrounding the so-called “umbrella” brand strategy. On the other hand, I also felt that the effort required to maintain both systems side by side was so great that it was hardly worth it.

But what does this mean for us at the company? Thankfully, it’s always punkt.de always been very important to us to understand and support the systems we use in the company. At the time of the split, for this reason, we already had people like Bianca Niestroj and myself who were more involved in the TYPO3 ecosystem, as well as colleagues who were very actively engaged in the Neos community, such as Sebastian Helzle and Daniel Lienert. 

Even on our own small scale, we saw what was happening on a larger scale: All fears of insults and unpleasant scenes during the split were largely unfounded. The general sentiment was more along the lines of: “Thank you for your time, and all the best moving forward.” This was also evident within our company. There were no disputes between the systems. Instead, there was a genuine interest in supporting the systems wherever we could be most helpful—and, of course, a commitment to providing excellent and comprehensive support for both systems. The reason is simple: We always want to offer our customers the best possible solution using the system that’s right for them.

How we’ll move forward with TYPO3 and Neos

We, as punkt.de have also discussed the pros and cons of the systems in depth and believe that both systems have a bright future ahead of them. Given the requirements we’ll need to address in the future, we remain convinced that we can handle the majority of them using TYPO3, Neos, and Flow. 

To stay closely involved with TYPO3 on the technical side, Alexander Krist attended his first TYPO3 Coresprint this year and will continue to punkt.de represent us in this capacity to bring the issues and requests from our projects to the system and thereby help drive its further development. 

We’re also staying on top of things with Neos. Here, too, we intend to continue contributing both to development and to other forms of support for the Neos team and the project’s further advancement.

In closing, it’s worth noting that despite many intense discussions and differing opinions, we look back with great gratitude on the past few years in the community, during which we’ve all learned a great deal from one another and close ties have formed between the systems and companies. We hope to stay in touch with everyone and continue shaping the web landscape in Germany together. We look forward to many more events where perhaps both systems will once again have a place.