Create a backend module to show the NodeType configuration in details

[neos-bot]

Jira issue originally created by user @dfeyer:

As a developer I need to have a proper overview of the NodeType configuration, the basic module must have:

• Nice overview of NodeType
• Filter by Package Name (node type namespace)
• Show the local property and super type property (merged properties)
• Validation based on schema
• outdated: Auto generated TypoScript overview
• First version is read only (but keep in mind that this module should allow edition in a future release)

As a inspiration source, check:

• dead link: Mockup: https://moqups.com/aertmann@gmail.com/pN1DrWwP/ (from Aske)
• Screenshop of the prototype: https://dl.dropboxusercontent.com/s/kft5ils1wsbmu9k/2015-01-23%20at%2012.40%202x.png?dl=0, https://dl.dropboxusercontent.com/s/q3hb6x3yxm22evp/2015-01-23%20at%2012.03%202x.png?dl=0, https://dl.dropboxusercontent.com/s/5fbexsbuv2zy04g/2015-01-23%20at%2012.40%202x%20%281%29.png?dl=0
• Raw brainstorming of information that need to be visible: https://docs.google.com/document/d/1wVpXXRzBvQAnf5wkWV4zvjKnnYDechBkBaiCP9HRBvE/edit#heading=h.jqreav2ydw2z
• More detailed brainstorming about the future NodeType editor module (one of the next step for this module)

About the futur Editor, check how Contentful or Gather Content does theirs "content modeling" modules.

This module must be provided as an external package, but an official one (with the Neos namespace), to not clutter the core with feature not required for everybody, like it's pretty nice to have it in Developement (require-dev) but not in production.

Jira-URL: https://jira.neos.io/browse/NEOS-1611

[mhsdesign]

Hmm i had the same idea ^^ https://discuss.neos.io/t/wizard-for-creating-basic-content-node-types-like-typo3-mask/5500

[Sebobo]

I could migrate all or parts of my https://github.com/Sebobo/Shel.NodeTypes.Analyzer to the core to solve this at some point. But would only do it with some support regarding concept and implementation adjustements.