Markdown callouts are such a basic feature, yet I didn't find a single issue requesting this feature on GitHub.
I know there are plugins and stylesheets available, but I still think this is such a basic Markdown feature that it should be available by default.
#admonitions #callouts
When Joplin was first published it put forward as one of its main features that it aimed to adhere as closely as it could to the Commonmark spec. As well as the note data being non-proprietary and human-readable the idea was that you could take your markdown note and move the content to another markdown app with little to no editing.
Of course some people preferred a little more formatting choices than Commonmark offered and so optional additions to markdown were added. They can still be found in Tools > Options > Markdown (this section was originally called "Plugins").
Later Joplin added the ability to create and install actual plugins. So rather than everyone getting everything a user could add only the features they wanted. The fewer options you switched on and the fewer plugins you installed, the more you retained compatibility with actual markdown.
Admonitions are not part of the Commonmark spec and so I would suggest that they are not really a basic feature. Admonitions may be very useful to some, or even many, users and that is why there are plugins such as GitHub Alerts or Markdown Alerts and Formatting Commands to let them add them if they wish. Personally I don't use them as I prefer my notes to be closer to actual basic markdown.
I am not a dev and I am not arguing against your idea. It's just that I have been using Joplin for a long time and have seen how it has developed and this is possibly why they are not included by default.
Make sense.
Even Mermaid is supported by default and has an option in the Markdown section of the settings. I think Callouts/Admonitions are a reasonable option to add to that section, even if they are disabled by default.
I see what you mean but, thinking about it, I suppose that the difference is that keeping a plugin maintained is the responsibility of the plugin author. As soon as the functionality moves into Joplin itself it becomes more code for the Joplin devs to maintain, test and support.
I think part of the issue with alerts is there are various different implementations with differing syntax, though the basic GFM style alerts are arguably common enough these days that it could make sense to support them out of the box.
I'm pretty happy with my markdown alerts plugin in my biased opinion though 