[Neos] [Team] NodeTypes in TYPO3.Neos.NodeTypes

Carsten Bleicker carsten at bleicker.de
Fri Jul 26 11:16:31 CEST 2013

right at this point i have to figure out how NodeTypes works and how they are configured.
and to get an overview of all given types i have to switch between several packages.
it was a little barrier to keep in mind wich node is configured in wich package.
ts2, yaml, templates etc.


Am 26.07.2013 um 07:19 schrieb Christian Müller:

> Hi Robert,
> that was my reasoning as well when I started the package and put everything in there. The question is what NodeTypes need to be delivered with Neos and which can optional. I think Page could move to TYPO3.Neos.NodeTypes (again) ;)
> Cheers,
> Christian
> Robert Lemke wrote:
>> Hi team,
>> using node types more frequently, I realize that it will likely be some
>> hassle for users to memorize which node types are part of the TYPO3.Neos
>> package and which ones are in the TYPO3.Neos.NodeTypes namespace.
>> As far as I remember, you moved types like "Page" to the Neos package
>> for dependency reasons. But wouldn't you think that, from a user's point
>> of view, it's much easier to have all (Neos) node types in
>> TYPO3.Neos.NodeTypes?
>> Cheers,
>> Robert
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos

More information about the Neos mailing list