[wp-trac] [WordPress Trac] #27159: Removing TinyMCE buttons to improve user experience

[WordPress Trac]

#27159: Removing TinyMCE buttons to improve user experience
-------------------------+---------------------------------
 Reporter:  hugobaeta    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  TinyMCE      |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui, administration
-------------------------+---------------------------------

Comment (by hugobaeta):

 Replying to [comment:6 celloexpressions]:
 > Can we get stats on usage of each TinyMCE button from wp.com? There may
 be other candidates for removal based on usage.

 I mentioned this on the skype group chat, but it's good to reiterate here.
 My whole idea is based on the concept of semantic markup. Stats are good,
 but just careful with how you use them: they should provide clarity, but
 not be decisive in this matter.

 As I said, I'd rather think in terms of what generates semantic markup
 lives in the base editor. What extends that (and is supported by a theme -
 aka anything that adds spans and classes to the markup) should be an
 extension (probably coming from a theme, like the image alignment classes)

 Semantic markup includes:
 * bold - <strong>
 * italic/emphasis <em>
 * strikethrough/delete - <del>
 * etc

 Non-semantic inlcude:
 * Alignment - <p style="text-align: right;">
 * Text Color - <span style="color: #ff99cc;">
 * Underline - <span style="text-decoration: underline;">

 We should help the user avoid having these non-semantic ones in the
 database entries. It defeats the purpose of our goal of letting users
 switch themes and still have a beautiful site...

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