What I like: +++ no need to switch between writing and preview + buttons for linking content (image or URL) since getting [] and () in markdown wrong is pretty common

What I don't like: - visual clutter: do we really need buttons for headings, bold, italic, indentation, quotes?

I get that some people may not be familiar with markdown, but showing a popup with the syntax (as others have mentioned here, I think a popup is better than linking to a different page) should get anyone up to speed fairly quickly. But I had a discussion with my girlfriend about this, she doesn't seem to agree and thinks buttons are necessary for most people so maybe I am biased haha

-- looks less "lean". Maybe buttons are too big? --- Why render markdown in text field when there is preview? What use is this:

- as you said yourself: it's buggy / error-prone / less obvious -- as others mentioned: I don't get how important this was/is. Are people really intimidated / not contributing because "markdown is too hard"? Did you maybe overshoot the goal with this since I think only posting images was not easy to understand?

Recommendations:

-- #118111

This would be far better than rendering markdown in the text field imo. With this, I can live with the buttons lol

When you mark a text and you press CTRL+K, it immediately formats the text to link to something.

For example, if I write test, mark it and then press CTRL+K, it gets replaced with [test](url) with the cursor having marked "url" (thus it will get replaced by what you type next)

Don't know if you were already aware of this feature. Gitlab has the same feature.