UX issue: "Headings" are called "Titles" #693
Description
For some reason this package and its UI consistently and erroneously refers to headings as titles.
I would like to make the case that this is a significant UX issue that should be fixed both in user-facing interfaces and in code.
Motivation (why is this an issue?)
The unfortunate naming choice is likely to cause confusion for users and developers alike.
The rest of the world uses the term "heading". If users want to learn markdown they will go to resources such as:
- https://markdownguide.offshoot.io/basic-syntax/ (this one is mentioned in the README)
- https://commonmark.org/help/
These resources consistently use the term heading.
Users are extremely likely to be familiar with modern word processors which also generally use the term heading for this concept.
In the context of HTML elements and attributes there is a also distinction between "heading" and "title" and this extends to tools & resources related to accessibility, search optimization, etc.
End users and developers alike may not be experts in the English language and therefore they may rely on keyword and pattern recognition to understand interfaces and make connections between what they read in documentation, markdown tutorials, etc. and what they see in @uiw/react-md-editor.
The toolbar's naming and icons are potentially confusing as well (as much as I appreciate the commitment required to produce a set of non-standard unfamiliar icons to reinforce use of the term "title" vs. using an existing open-source icon set with "heading" icons).
In the code, commands such as commands.title, commands.title3, etc. are potentially confusing to developers.
As a developer my automatic "there's a mistake!" "there's a bug!" neurons fire when I look at the code.
Thanks
I just tried this package for the first time and I appreciate the thought and work you've put in. It is refreshing to see a lighter weight option for markdown!
I also appreciate when it comes to the code this would be a breaking change to address.
One idea is you could always treat the old names as an alias to minimize impact and mark them in tsdoc comments with @deprecated.