I think it would be useful to have a link to the CommonMark reference, or optionally a custom topic, to help people with editing that cannot be performed by means of the toolbar buttons. If a link to a custom topic can be configured, plugin-specific markup such as that for the checkmark plugin could also be documented.
A question mark button all the way on the right in the toolbar button seems like a good way to add this link.
I disagree. This would be a link to a reference to be consulted when you don’t remember some Markdown syntax you seldom use. It’s not something you read once and then never need to revisit.
You seem to labor under the illusion that users will read anything you put on the screen.
They won’t.
The best approaches involve giving the information to the user just in time, when they are in most need of it – not dumping a bunch of random permalinks on the screen “just in case” that will be ignored 99.999% of the time, and add to overall clutter for all users.
No, sorry to disappoint you. This is simply a selfish suggestion for something that I personally would find handy. It is inspired by the GitHub editor which includes a link to the GH Markdown spec which I consult every now and then.
Agreed, that would be the ideal solution. Of course, that is easier said than done. This varies wildly between individual users, so I’m skeptic about the effectiveness of such an approach without extensive trials. Otherwise it’s just based on assumptions.
I assume the “Have you tied the button” is an example of this approach? For some reason, Discourse assumes I agree with the post I am replying to when my message contains very few characters. When I first ran into this, that assumption was wrong and caused nothing more than confusion and frustration.
That said, I don’t think there is an easy solution to educating users. There is probably no solution at all when dealing with users with different backgrounds, so please don’t take this as criticism.
The types of people who would find this handy are able to self-medicate by proactively seeking out and finding the information they need. They are already students.
Furthermore … if users actually read anything (they don’t) they would have gotten to the formatting step of the interactive discobot welcome PM that all new users get. Which is best, since it’s dynamic and interactive using the actual editor and contains links to the help.
Check your PMs and you’ll see that very same welcome PM there too.
I have had many people ask me how to use markdown so I’m for this idea.
It personally took me a long time to even figure out that the composer used markdown and to source instructions on how to use it.
My suggestion as a solution for this is to add a blue box on the top of the composer to new users saying something like:
“Learn more about how to format your text using markdown here: [link]”
The blue box can have a cross on the top right, so that people who no longer want to see it can close it permanently.