[wp-trac] [WordPress Trac] #38049: Rename Headings in TinyMCE

[WordPress Trac]

#38049: Rename Headings in TinyMCE
-------------------------+------------------
 Reporter:  mrwweb       |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  4.7
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+------------------
Changes (by ahortin):

 * focuses:  ui, accessibility => ui


Comment:

 Please don't do this. Any of it. Please.

 The removal of the Heading 1 will be a HUGE pain for anyone using a page
 builder plugin. When using a Page Builder, most of them don't
 automatically output the actual page title. They'll simply start off with
 a blank page (by default). This means you typically need to manually enter
 the page title and style it as a H1. Removing the 'Heading 1' option is
 obviously going to make this extremely difficult.

 As much as most people here wont like page builders, there are HUGE
 communities (Beaver Builder, Divi, Visual Composer, etc.) of people using
 them and you're going to make life very difficult for them by removing
 this 'Heading 1' option.

 Likewise, I think the idea to change what HTML tags are generated for each
 Heading is a really, really bad idea. Anyone who's been using WordPress
 for even a short amount of time, knows that when you use a 'Heading 2', it
 generates an h2, as an example. Changing this so that an 'Heading 2' now
 generates an h3 is ridiculously confusing. You don't need to be a
 developer to know what an h1 or h2 heading is used for. Anyone who knows
 anything about SEO knows when they should/shouldn't be using these
 headings. Having an 'Heading 2' generate an h3 is just so confusing.

 Likewise, changing the names of these titles would be equally confusing.
 There's no standard naming conventions for anything Heading (H2),
 Subheading (H3), Subsubheading (H4) or below. The nearest convention we
 have is what is specified in the html spec, which is the word 'heading',
 hence why 'Heading 1', 'Heading 2', 'Heading 3' etc. makes sense.

 Again, anyone who has even a mild interest in SEO isn't going to know or
 understand what a 'Subsubheading' is. Every SEO article out there is going
 to refer to your page titles as 'Heading 1', 'Heading 2' etc. When Google
 talks about "Dos & Dont's" for good page SEO, they're not going to use the
 terms 'Subheading' and 'Subsubheading', they'll use 'Header 2' (or 'h2')
 and 'Header 3' (or 'h3'). You're not make things easier by changing this
 convention, you're doing the exact opposite.

 I also think it's a huge mistake to remove 'Heading 5' & 'Heading 6'. I
 agree that these headings aren't used anywhere near as often as the
 others, but it's not up to you to say that people shouldn't be using them.
 The fact the they could be added back in using a filter is irrelevant. Why
 should we have to add another plugin or add a new filter just to get back
 functionality that should be there in the first place. How does removing
 these two Headings make WordPress any easier to use? It doesn't, simple as
 that.

 I'm all for simplifying things in the dashboard, but things shouldn't be
 removed or even renamed at the expense of making things more difficult for
 end users.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38049#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform