Random ideas

[nhovratov]

Allow nested folder structures for Content Blocks (1 extra level)

• This would allow to group blocks when the list gets bigger
• types which belong together can be grouped
• Does not break current logic
• Same already available for Basics
• nice extra: the folder name could represent the group -> Decouple the group from the definition. Fallback "default" will still work.

Allow to define custom Content Block Types

• This means essentially named RecordTypes. E.g. type News which EXT:news could provide.
• Developer provides base definition, which can be extended. Maybe Yaml file in folder ContentTypes with basic definition could work.
• Needs to be loaded before concrete Content Block definitions.
• This extension provides special types Content Element and Page Type. Record Type is fallback for everything without a definition.
• Enhances overview of types
• Slims down generic Record Type folder.
• -> this needs some bigger refactoring. A ContentTypesRegistry is needed.

Rename RecordType to GenericType

• The term "record type" clashes with the "record type selector" field / value.
• If we rename RecordType to GenericType we can also rename typeName to the more known term recordType.

Allow to structure editor yaml without the need for (global) Basics

• If the yaml gets big the standard way was to extract tabs/palettes into Basics. But Basics should be there to be re-used and not only for one specific block.
• Maybe we could structure multiple yaml files into separate tabs and then include them in the main yaml file.
• E.g. folder "Tabs" or (local) "Basics" with multiple yaml files.
• This way the Content Block is easier to copy/paste and does not have dependencies to global Basics.