Separate element types

[bjarnef]

Currently element types are located under document types and are partial elements used in Block List and Block Grid.

However I wonder if element types should be separated under an Element Types tree?

Content types (document, media and member types) are more streamlined with (almost) same functionality, but I think there are some issues if using Block List or Block Grid on media or member type. I would probably not use a complex Block List or Block Grid on media or member type, but a basic Block List similar to legacy Nested Content on e.g. a member type could be useful.

Although element types show "History cleanup" I don't think they actually have partial versions stored - only at page level.

Anyway when element type is enabled it also disable functionality like list view, templates and child node permissions, so I think may be cleaner to separate.
I think it would also make the element type picker cleaner, when selecting blocks (content or setting) in Block List or Block Grid as we don't have the navigate through the regular document types and compositions.

Possible the same element type could be re-used in a Block List on content, media and member, but as mentioned I think block based editors currently have some limitations on media and member types.

[bjarnef]

It may also be worth considering this in future, when working with reusable blocks:
https://github.com/umbraco/rfcs/blob/0025-reusable-content-with-global-blocks-2/cms/0025-reusable-content-with-global-blocks.md