High level discussion on allowing different flavors of markdown

Features
1

Hi community,
this is a spin-off from High level discussion on plug-in architecture & template library.
This is a collection topic on how different flavors of markdown could be allowed.
There has been many discussion about to add this or that mini feature, what would break with the rule to follow standard strictly to ensure cross-platform and cross-3rd-party-application compatibility.
An idea what came up was to allow different flavors as additional language pack, what can be easily activated / deactivated but Joplin core still follows markdown specification.

Inputs and opinions are welcome.
I start by listening topics of which I can still remember wherein suggestions towards this direction were made:

1 Like
2

a good summery is here
https://tools.ietf.org/html/rfc7764 / https://en.wikipedia.org/wiki/Markdown

https://commonmark.org/

3

For those who easily suffer from information overflow, this (pruned) family tree may be sufficient to get a first impression of the current state of MD affairs.

Joplin currently aims to comply with CommonMarkdown, a broadly accepted standard in spite of John Gruber. On top of that, Joplin gives access to some extra features in the form of plug-ins.

I also mentioned two other lightweight markup languages in that post, AsciiDoc and reST. I don’t want to advocate those, because I have no experience with them. But it’s not a bad idea to have your eyes open in all directions.

1 Like