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

Jacob Floyd cognifloyd at gmail.com
Mon Jul 29 15:59:38 CEST 2013

I believe the idea is that other people (and their apps) will provide their
own NodeTypes package.

So, we could have

TYPO3.Neos.NodeTypes then becomes the model for how other people can
quickly create their own set of 'content elements' and replace all of the
Neos provided node types (except for the bare minimum that all
Neos-using-apps will require, which should be provided in Neos itself.)


On Mon, Jul 29, 2013 at 7:27 AM, Robert Lemke <robert at typo3.org> wrote:

> Hi Christopher,
> Christopher Hlubek wrote:
>> we really need to make Neos work without any bundled node types for a
>> good experience when building custom (CMS) applications. Even the Page node
>> type is already problematic if it's not possible to use a custom node type
>> but I see it absolutely the same way as Sebastian.
>> The experience is not improved by some lock-in decision. We really need a
>> lot of development tools for a smooth experience like a node type manager /
>> wizard / builder.
> you know that I'm just checking if we can improve the user experience.
> In which technical sense do the non-used node types of
> TYPO3.Neos.NodeTypes stand in a way if you use Neos in a custom way? Which
> possibilities are blocked (lock-in decision) by requiring the NodeTypes
> package?
> Cheers,
> Robert
> ______________________________**_________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/neos<http://lists.typo3.org/cgi-bin/mailman/listinfo/neos>

More information about the Neos mailing list