[wp-trac] [WordPress Trac] #38049: Rename Headings in TinyMCE
WordPress Trac
noreply at wordpress.org
Wed Sep 14 00:33:16 UTC 2016
#38049: Rename Headings in TinyMCE
-------------------------+-----------------------------
Reporter: mrwweb | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Editor | Version:
Severity: normal | Keywords:
Focuses: |
-------------------------+-----------------------------
Forking a proposal from #27159 where Heading 1 will be removed from
TinyMCE in WordPress 4.7:
Multiple people have suggested renaming the Headings in the editor '''to
encourage correct usage''' (that is the goal of this ticket). I would add
that this might be combined with actually removing Headings 5 and 6 which
I imagine are barely [properly] ever used. (Theme and plugin authors will
always be able to add Headings back via filters.) Only having to name
three levels of headings also makes this much more feasible.
A few ideas just to get things started.
'''Concept 1'''
- Heading (H2)
- Subheading (H3)
- Subsubheading (H4)
'''Concept 2'''
- Section Title (H2)
- Subsection Title (H3)
- Subsubsection Title (H4)
'''Concept 3 (use indentation to imply hierarchy)'''
- Heading 2
- – Heading 3
- –– Heading 4
At least at first, I think it would make sense to retain the HTML heading
level in parentheses as shown above to help technical editors understand
what's going on.
To encourage correct heading usage, the new labels must communicate to all
editors that the heading levels are hierarchical and not selected based on
perceived importance or (obviously) visual appearance.
One primary problem is "what comes after sub? subsub?" Most rich text
editors editors I've looked at while writing this ticket either using
"Heading #" OR give only two levels of Heading (which avoids the
"subsubsub" problems).
'''References'''
- Medium [https://blog.medium.com/introducing-improvements-to-titles-
subtitles-and-headings-97978206d8f9#.n4ygmct3p just changed their
formatting toolbar to focus users on appearance over heading levels]
because they were apparently being abused. I think this is pretty
obviously the opposite direction this ticket intends to go (giving into
visual over hierarchy).
- I honestly can't find other examples of editors doing this beyond the
exceptions mentioned above, so examples are highly appreciated.
cc: @hugobaeta
--
Ticket URL: <https://core.trac.wordpress.org/ticket/38049>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list