[TYPO3-core] (New) TYPO3 CMS Vision

Philipp Gampe philipp.gampe at typo3.org
Sat Aug 16 11:24:50 CEST 2014

Hi Michael,

Michael Stucki wrote:

>> I would keep the TYPO3 CMS backend, drop CMS frontend support and use
>> Neos for Frontend Editing. I guess Neos would need some work to fully
>> work on custom models (CMS tables), but it should be doable. The CMS
>> backend would need some love to read and edit content repository
>> contents.
> Uhm... I haven't heard anyone requesting such a feature, so why do you
> think we should work on it?

Heard that before. And if we start using Flow as a technical base for CMS, 
then Neos would just be one of many packages that might be installed.
It might be strange to not have some sort of interaction going on between 
Neos and CMS.
After all, if someone is in the need of such a feature he will hack it 
himself or let someone code it for him.

> I wouldn't object if this was a small and useful feature, but what you
> suggest sounds like rewriting Neos in TYPO3 CMS. What's the point of that?
> Here's a thought: Why do you want to spend your energy for projects like
> this in TYPO3 CMS instead of doing it the other way around and
> contribute your plans to TYPO3 Neos?

I do not think this is a one way street. And I am a CMS developer currently. 
I might contribute to Neos once I start using it, but until then, I focus on 

Best regards
Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
Documentation – Active contributor TYPO3 CMS
TYPO3 .... inspiring people to share!

More information about the TYPO3-team-core mailing list