[TYPO3-core] subheader for all types, not just "header"?

[Benjamin Mack]

Hey Stefan,

On 26.01.14 00:28, Stefan Neufeind wrote:
> But is there really a reason why "subheader" is not commonly shown?
There is no reason (anymore).

> Or if not, might we consider to just use the palette "headers" instead
> of "header" for all content-types?
Yeah, that would be consistent.

However, I could imagine that the editors have problems with having
header (incl. header date, header link, header type) and subheader (no
options, why-so-ever) plus bodytext.

How about this:

* For CType "header" we remove "subheader" and integrate "bodytext" as
type "input" not type "text".
* we have a migration wizard to move all CType header "subheader" to
"bodytext" (it's basically a one-liner SQL).
* we adapt the CSS Styled Content output.
* We remove subheader completely from the system

My concern is this: One field less is less confusion. Seems like nobody
missed it before, why adding it now "because we can"? tt_content is
bloated anyway already :)

If somebody needs this field, he/she should write an extension then.

What do you think, Stefan?

All the best,
Benni.