The only supported plugins are the "fenced" plugins - those that wrap a section of text in triple backticks (for example, KaTeX, Mermaid, etc. If you open a Markdown note that makes use of such plugin in the Rich Text editor, it is likely you will lose the plugin special formatting. The catch is that since Markdown is used under the hood, it means the rich text editor has a number of limitations it inherits from that format:įor a start, most Markdown plugins will not be compatible. It is also good if you sync with the mobile application, which doesn't have a rich text editor. This is generally a good thing, because it means you can switch at any time between Markdown and Rich Text editor, and the note is still readable. However there is a catch: in Joplin, notes, even when edited with this Rich Text editor, are still Markdown under the hood. Bold text will "look like this" and tables will be more readable, among others. For that reason, Joplin also features a Rich Text editor, which allows you to edit notes with a WYSIWYG editing experience. Bold text will look **like this** for example, and tables might not be particularly readable. In some cases however, the extra markup format that appears in notes can be seen as a drawback. Markdown is a simple way to format text that looks great on any device and, while it's formatted text, it still looks perfectly readable in a plain text editor. TLDR: Avoid using Markdown plugins if you primarily intend to use the Rich Text editor, and be aware of the editor's limitations.Īt its core, Joplin stores notes in Markdown format.
0 kommentar(er)
