Did the latest update remove some of the formatting options?
For instance… I use the big “page break” (solid, long bar) often in my posts… but i can’t seem to find it anywhere anymore?
AI-generated summary
A discussion has started regarding the removal of some formatting options in a recent update. 8BIT noticed that the “page break” (solid, long bar) option is no longer available. fefrei mentioned that this was a deliberate decision made by @codinghorror.
As an alternative, users can create horizontal rules by typing a few - in a separate line. 8BIT expressed disappointment about the removal of extra options and suggested implementing a “toggle toolbar” similar to WordPress.
@zogstrip mentioned that the company prefers a “less-is-better” approach but suggested creating a plugin for additional options. sam and @vinothkannans discussed the possibility of creating a theme component to add back header options.
@codinghorror expressed concerns about the current approach and plans to revisit the issue. sam believes that the changes can be lived with for now and that the header button is of limited use once users learn how to create headers manually.
@codinghorror mentioned that a help button is planned, which may cover the removed functionality and more. The composer is expected to undergo changes, including a possible reskin, which may include the help button.
Yes, it was @codinghorror‘s call that these could be removed.
You can still create horizontal rules by typing a few - in a separate line 
We’re more of a “less-is-better” rather than “more-is-better” company/product 
But feel free to add these “options” in a plugin.
I would actually prefer a theme component here, @vinothkannans can you create a theme component for adding back header options and post it in #plugin:theme ?
While removing it from core we also removed the label values from locales (like hr_title: "Horizontal Rule"). I guess we can’t add locale values back using theme component. So it is better to use plugin?
I still prefer a theme component, we can deal with localization in the component itself.
Just do it in English for now. If we use a plugin our hosted customers can not use it.
No, we need to revisit this. Not a fan of the current approach.
How about keeping the buttons but display:none them in the default theme?
We will revisit button customizability later, it is already doable in a theme component or a plugin if you must but think it is better just to live with the change for a bit.
The GIANT issue with the header button is that it is of zero use once you learned how to do headers. Typing # test is way easier than reaching to the mouse and clicking header. The only real purpose the button served in the past was discoverability.
Anyway we can talk about this again in a month or two after some real world use cases ideally of paying customers come our way that really demonstrate how this is needed on a regular basis.
We are also planning to add a help button which I personally think covers this and more. We need the flexboxing of the composer to get complete via @zogstrip (lots of regressions, it’s a hard area to change) then we have a minor reskin coming for the composer via @awesomerobot which may include a help button, etc.
So none of this is really necessary at the current time, things have to happen in order.