[Neos] Role of Typo3 CMS/NEOS going forward

[Dominique Feyer]

My 2 cents regarding "Tesseract like" package for Neos.

Neos core support with TypoScript2 and EEL more or less all the features of Tesseract (abstraction to select content, list, paginate, display, …). That’s one of the key feature of Neos, being able to work with structured content, without spending time on a low level coding language and database configuration. In Neos it’s a matter of configuration, define your NodeType (basically you data schema), push some TS2 and Fluid template and you can display, filter, search your content without touching PHP. 

For the workflow review process, we plan to have that kind of feature in the future. If you can help, you are highly welcome.

Bests,

--   
ttree sàrl  
Dominique Feyer  
Rue du Valentin 34 et demi
CH - 1004 Lausanne
+41 21  312 36 35  
dfeyer at ttree.ch
ttree.ch - @ttreeagency - plan d’accès

Le 20 novembre 2014 à 15:40:03, François Suter (fsu-lists at cobweb.ch) a écrit:

Hi Daniel, 

> They've also had a demo of Typo3 NEOS, but we definitely need Workspaces 
> with a review model prior to publication, and we also want to use the 
> Tesseract extensions. 

I think Rasmus summed things up real well. If you look at the current 
activity on TYPO3 CMS, it's obvious that it's far from dead. On the 
contrary, I think it has been quite stimulated by what happened with 
Neos, and I think it's going to have an active community for a long time. 

And if you want to use the Tesseract suite, then better stick with CMS, 
as we currently have no plans on porting it to Neos. I'm not even sure 
that it would make sense, as it is quite opposite to the Domain Model 
paradigm on which Flow/Neos is based.