@menelion n asterisks are n-th level headings (1 to 6).
Lists are specified using a hyphen
This would render perfectly well in Org:
* Eins
- list item inside eins
- something else
** Zwei
- list item 1 inside Zwei
- item 2
- item 3Honestly, #Orgmode is also easier than #Markdown. Just like Markdown, #LaTeX support is built into the language.
I've written scientific papers and whatnot using #Org mode. My static website is published using #Hugo, which supports Org OOTB (if not for this, I'd be using #Zola or #Astro)... With #orgroam I can organize my notes using the #zettelkasten method and view notes on a graph à la #Obsidian. Note that #OrgRoam is the objectively superior #Obsidian alternative, just as #Orgmode itself blows Markdown out of the water.
How could I forget literate configs? Computational notebooks are a GODSEND. Imagine a file that acts very much like a #Jupyter #Notebook (graph support etc is taken care of thanks to #Emacs). Imagine an entire Jupyter Notebook sent in a simple text-ready file.
It's totally possible to open an Org notebook in a plain text editor, make changes and send it to peers. If they have Emacs open they can also execute the notebook just like they would with a Jupyter Notebook. Results are displayed (by default) in-place too.
I invite @publicvoit to share his opinions 😉
