[Feature Request] Export to Markdown

[iNoSec2]

Is it possible to have an export to markdown? Since there is export to HTML maybe it isnt an heavy task but im surely worng with that xD

And is it possible to have the markdown editor capacity? since we can make things like * to have a bullet list

Thank you for your hard work, and please stay safe

[datavectors]

I am looking at CherryTree as a front end editor / authoring tool which, as you request, pipes the exported HTML to pandoc script and thence outputs markdown.

[iNoSec2]

Thanks i will look into it

[datavectors]

I am actually working on this pipeline right now and it looks promising.
The key is to have in the pipeline a stage of parsing which knocks the exported HTML into shape, particularly where CodeBoxes are embedded.
My end goal is to create a Reveal.js slides deck (using Pandoc) where each node in CherryTree document is a slide. Also I am adding xAPI statements in CodeBoxes.

Thus CherryTree will be the front line authoring tool of eLearning modules.

Added note: After trying HTML export I experimented further and I was able to bypass the HTML stage. HTML is not needed.
I can embed markdown statements into any CherryTree rtf node (even though rich text format).
I can then export CherryTree document as .txt. Single file.
Then simply edit the exported .txt extension to ,md for markdown. Now I can continue previewing Markdown (I use Atom with Markdown Preview Enhanced package, but other editors can be used).

This workflow allows Cherrytree to be the front end editor, and nuggets of content (nodes) can be easily edited and moved around. The markdown statements are not processed in CherryTree of course, but they are when exported as pseudo markdown.

[galk-research]

So will this issue here deal with both using markdown as a valid native format (in addition to .ctd, .ctb, .xml, ...) as well as exporting? These of course are highly related issues, but the first subsumes the latter.

[m1k3s0]

This one seems to be more geared toward export only. Meaning converting from rich text to markdown and having an option in the export menu. Issue #218 can be for tracking the work needed to create another file format in addition to SQLite and XML. That would be a much bigger effort for Giuseppe.