@yantar92 @screwlisp I know.

However, I think you've got the Org point of view perspective and I want to promote Orgdown to people who will never hear of Emacs or are even opposing the use of Emacs. Totally different turf and hosting information at org or worg doesn't help here.

That's totally different perspective and the way non Org people stumble over information.

After all, the #Emacs community never differentiated the tool #Orgmode from the much more general lightweight #markup language #Orgdown. The focus of #OD is the latter and I want to promote that by mostly neglecting any connection to Emacs, Elisp and the communities involved. Not directing people to the mixup of information on Orgmode.org was a very deliberate decision of mine.

https://karl-voit.at/2021/11/27/orgdown/

I know that some org community people disagree with my approach for various reasons. Some of the arguments do have real substance, most rather not.

YMMV

#LML #publicvoit

@davemq @jameshowell @ericsfraga @mstempl @sacha

True.

However, you've switched from a very rich syntax (#LaTeX) to a very simplistic one (lightweight markup language - #LML). There's a difference in output: https://karl-voit.at/2015/07/26/LaTeX-typography/

Don't get me wrong: I, too, prefer writing documents in #Orgmode and exporting to PDF myself. It's a very good compromise.

Meanwhile, I'd not care if the process switched from org->(pdf)latex->PDF to org-> #typst ->PDF or anything similar.

However, I'm not so sure if I'd use Org for setting a document where I really want to get the maximum, like I tried with my PhD thesis: https://karl-voit.at/tagstore/en/papers.shtml

Edit: also related: https://karl-voit.at/2017/08/26/latex-fetish/

#publicvoit

@jarango Everything true.

However, I disagree with #Markdown: https://www.karl-voit.at/2025/08/17/Markdown-disaster/

It's way more open than, let's say, #OneNote & so forth. Unfortunately, it's far from being a #textformat that can be reused anywhere without problems. At least I need to convert MD all the time from one flavor to a different.

With more and more #Obsidian add-ons introducing their own syntax elements, you will end up with clear text files you still can't convert for a different tool without modifications. Good luck with finding out which elements are going to survive and which not. For a few files, that seems OK. If you have a decent #PKM like you describe in your awesome #DulyNoted book, it requires more effort.

For everything I need to use with #MD, I keep a syntax file with one example element so that I keep an overview & know what to convert how in case I need to reuse information stored in this MD flavor.

With org, I just push it through #pandoc & I'm done. 🤷

#publicvoit #LML #Zettelkasten

Like you, I use markdown to write notes in Joplin. And to write Fedi posts such as this one. (wafrn, the Fedi software I am using, supports writing posts in markdown.)

My only suggestion: do not get seduced by markdown's ease of use. Do not try to use it indiscriminately. Do not use it for documents that require complex markup (text with lots of subscripts/superscripts, mathematical equations, chemical formulae, nested sections, tables, columns, etc.), or even for simple but very long documents (long-form writing, books).

Basically, limit its use to short documents/notes that require very little markup.

This article is a good overview of the benefits and limitations of markdown.

As an aside, I hope djot replaces markdown as the most popular lightweight markup language in the near future.