I was checking more last night, and there is a newer editor cherry-markdown (see demo) that seems better and most updated.
xxxxx settings for markdown to be editable/view-only then if view-only > rendered as raw | html would be great. it would enable users to create nice looking notes
This would normally use Files existing allow_edit option that applies for any text-based files. If editable, we would use split-view example as in the demo above. If not editable, I think I would still use the same plugin, preferably with a button to toggle between raw markdown and html ... It seems pointless to include a separate markdown renderer, just to render markdown in non-edit mode, and this plugin seems to have some nice view features.
xxxxx a toggle on the to switch between edit/preview would be neat. it seems easy-markdown-editor and toast ui offer this by default
Yes. Personally, I enjoy the default split-view in these markdown editors.
xxxxx also toast-ui has full wysiwyg editing but it's quite big (minified > 500kb I think)
Like a HTML editor? All the plugins seem to have wysiwyg options for editing markdown. As for the topic of HTML specifically, we could have added options for this also, but it seems like a bad idea ... While markdown will render consistently in a preview, there is no reason to believe HTML will render properly in a preview, and it could easily break Files gallery also (orphan tags), unless contained inside an <iframe>
. Since there is already a CodeMirror raw HTML editor, and a button to view the html document in a new window, I think that is sufficient.
A potential problem in markdown previews, is relative links (for example links or images). Relative links would be relative to the Files gallery url of course, which could be wrong. There is probably a config option to assign relative path for markdown links, but this would be a global option of course.
Thanks for your input.