UX: remove empty/not-applicable content apps

[nathanwoulfe]

Nothing major, just a quick UX win (IMO 😄) - when editing a document type, and that type is an element, the list-view and templates content apps are available in the header, but have no content other than a message:

If it's not applicable, why not remove it? Dead-end navigation isn't a GoodThing™️, and in this case is easily avoided.

Happy to make the change if it's deemed worthy 😃

[nul800sebastiaan]

Channeling my inner UX designer: consistency in the UI. How frustrating if you KNOW that on all other document types you could set a list view or a template. And nobody is telling you why the heck these are missing on just 2 of your document types. I'd much rather know: oh, it's not applicable... actually, maybe I didn't need this to be an element type anyway,

[nathanwoulfe]

Fair point. What about different visible state in the header (eg faded to indicate disabled/not available)?

[nul800sebastiaan]

That makes more sense to me, maybe a little help text on the "element type" toggle ("this will disable list view/template")?

@madsrasmussen what do you think?