thank you for your prompt answer! As I mentioned, Christopher, I don’t have a perfect solution either. And what you say, Florian, is certainly correct: There won’t be an out of the box solution that fits everyone’s needs.
So we might think of something that
a) lets the integrator decide on the segmentation of the dialog,
b) works with every package that implements node types,
c) survives updates of Neos or any of the packages.
Since the original
NodeTypes.yaml will be overwritten every time you update Neos maybe Neos should look for an optional file called
CustomNodeTypeCollections.yamlfirst. If it is there, the
NodeTypes.yamlwill be ignored.
CustomNodeTypeCollections.yaml references to packages that are not installed or don’t even exist, would be ignored by Neos.
Apart from the file name and implementation details do you think this is the right direction?