User story:

As a Developer, I can tune the presentation of the content type editor independently of the actual data model, so that the editor UI will work the best for my authors

Notes:

("content type editor" is basically the Editor subapp.)

Although we strive for clean separation of data-model and presentation - this should be balanced with ease of development. It could still make sense to configure some presentation aspects in the model. For example the order of the fields - and perhaps location of tabs, etc.

Acceptance criteria:

• If a developer specifies nothing, the editor UI has a sensible default configuration.
• Developer can specify which fields go in which tab.
• Developer can specify which input field to use for a raw type - for example a "select" or a "radio button group". So a way to select which FieldType to use if you want to override the default that the content types system provides.
• Developer can specify an input type "mask" (email, number, etc) such that html5 entry forms can be used.
• Developer can choose how many lines an input field has.