#orgdown — Public Fediverse posts

@marlinz008 #PIM ist sogar auch eine etablierte wissenschaftliche Disziplin. War da ein paar Jahre auch akademisch unterwegs. Ist also nicht von mir, der Begriff - aber danke. 😉

Dir fehlt diese (IMO eher unnötige) #Visualisierung? Naja, warum dann nicht mit https://codeberg.org/publicvoit/orgheadingnetwork machen? Du nutzt Orgdown - da kann man sowas easy "nachrüsten".

#orgmode #orgdown

@marlinz008 #PIM ist sogar auch eine etablierte wissenschaftliche Disziplin. War da ein paar Jahre auch akademisch unterwegs. Ist also nicht von mir, der Begriff - aber danke. 😉

Dir fehlt diese (IMO eher unnötige) #Visualisierung? Naja, warum dann nicht mit https://codeberg.org/publicvoit/orgheadingnetwork machen? Du nutzt Orgdown - da kann man sowas easy "nachrüsten".

#orgmode #orgdown

@itskamrankhan In a free/libre and extremely capable software called #orgmode whose limits are only bound by the limits of your imagination. (1)

Through #FOSS and (in contrast to #Markdown (3)) well designed and easily re-used clear text data format #orgdown (2, 5), I do have many possibilities to generate input for it and re-use output in other tools. Orgdown is recognized without any manual conversion in lots of tools (4).

Let me cite Dominik's tenth rule: Any sufficiently complicated #PIM or note-taking program contains an ad hoc, informally specified, bug-ridden, slow implementation of half of Org mode.

1 https://karl-voit.at/orgmode/
2 https://karl-voit.at/2021/11/27/orgdown/
3 https://www.karl-voit.at/2025/08/17/Markdown-disaster/
4 https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org
5 https://gitlab.com/publicvoit/orgdown

#Emacs #PKM #Zettelkasten #Obsidian #MD #notion #logseq

@itskamrankhan In a free/libre and extremely capable software called #orgmode whose limits are only bound by the limits of your imagination. (1)

Through #FOSS and (in contrast to #Markdown (3)) well designed and easily re-used clear text data format #orgdown (2, 5), I do have many possibilities to generate input for it and re-use output in other tools. Orgdown is recognized without any manual conversion in lots of tools (4).

Let me cite Dominik's tenth rule: Any sufficiently complicated #PIM or note-taking program contains an ad hoc, informally specified, bug-ridden, slow implementation of half of Org mode.

1 https://karl-voit.at/orgmode/
2 https://karl-voit.at/2021/11/27/orgdown/
3 https://www.karl-voit.at/2025/08/17/Markdown-disaster/
4 https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org
5 https://gitlab.com/publicvoit/orgdown

#Emacs #PKM #Zettelkasten #Obsidian #MD #notion #logseq

@julien @taseroth You're right, it's not.

However they managed to tick all the other boxes of that definition which is the important part here from my point of view.

I've lost #Orgdown file sync for good (not coming back) and I need to convert all my data files to a different format even if I'd continue using #logseq.

What would you call that instead?

Therefore, I certainly migrate the data to a different solution where major breaking changes are less likely.

@julien @taseroth You're right, it's not.

However they managed to tick all the other boxes of that definition which is the important part here from my point of view.

I've lost #Orgdown file sync for good (not coming back) and I need to convert all my data files to a different format even if I'd continue using #logseq.

What would you call that instead?

Therefore, I certainly migrate the data to a different solution where major breaking changes are less likely.

@julien Well, with the major changes (discussed for a year or so), #logseq is dead to me and many other users: (temporary?) no file sync, database only, removed support for #Orgdown syntax, proprietary sync (a paid service?), ...

If you haven't migrated, you may do so now depending on your requirements: https://karl-voit.at/2021/01/18/tool-choices/

https://karl-voit.at/orgmode/ is the best solution out there by far but many people can't use it. For very simple use cases, #Silverbullet seems nice. However, it also has #Markdown which is a downer as well: https://www.karl-voit.at/2025/08/17/Markdown-disaster/ At least, they are aware of its downsides: https://silverbullet.md/Markdown

HTH
#publicvoit

@julien Well, with the major changes (discussed for a year or so), #logseq is dead to me and many other users: (temporary?) no file sync, database only, removed support for #Orgdown syntax, proprietary sync (a paid service?), ...

If you haven't migrated, you may do so now depending on your requirements: https://karl-voit.at/2021/01/18/tool-choices/

https://karl-voit.at/orgmode/ is the best solution out there by far but many people can't use it. For very simple use cases, #Silverbullet seems nice. However, it also has #Markdown which is a downer as well: https://www.karl-voit.at/2025/08/17/Markdown-disaster/ At least, they are aware of its downsides: https://silverbullet.md/Markdown

HTH
#publicvoit

@qbi @rainer Vorsicht: #logseq vernichtet sich gerade selbst: Einstellen vom #orgdown Format, Datenbank-only, Entwickler nutzen KI, kaum Qualitätssicherung (aktuelle Version stützt ab, wenn man "1. " eingibt, las ich kürzlich), ...

Finger weg von logseq. Ich muss Frau und Vater leider wegmigrieren. Wer #Orgmode nicht nutzen kann (das ist nach wie vor das Beste mit Abstand), der kann sich aktuell SilverBullet ansehen, ob sowas ausreicht.

https://karl-voit.at/orgmode/

#PIM #publicvoit

@qbi @rainer Vorsicht: #logseq vernichtet sich gerade selbst: Einstellen vom #orgdown Format, Datenbank-only, Entwickler nutzen KI, kaum Qualitätssicherung (aktuelle Version stützt ab, wenn man "1. " eingibt, las ich kürzlich), ...

Finger weg von logseq. Ich muss Frau und Vater leider wegmigrieren. Wer #Orgmode nicht nutzen kann (das ist nach wie vor das Beste mit Abstand), der kann sich aktuell SilverBullet ansehen, ob sowas ausreicht.

https://karl-voit.at/orgmode/

#PIM #publicvoit

#PlantUML #Mindmap does support #orgdown syntax for generating graphical #Mindmaps: https://plantuml.com/mindmap-diagram 👍

And you may include PlantUML diagrams directly into #Emacs #orgmode via https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html + https://plantuml.com/emacs

#PlantUML #Mindmap does support #orgdown syntax for generating graphical #Mindmaps: https://plantuml.com/mindmap-diagram 👍

And you may include PlantUML diagrams directly into #Emacs #orgmode via https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html + https://plantuml.com/emacs

Vibe-coded my first Android app: #AOC which stands for Android #Orgdown Capture. :orgmode:

It's a simple app that will only do #orgmode syntax capture tasks to text files.

I still need to think about publishing the source as it's AI slurp and I won't provide any support for it. 🤔

Edit: https://codeberg.org/publicvoit/AndroidOrgdownCapture

#PIM

Vibe-coded my first Android app: #AOC which stands for Android #Orgdown Capture. :orgmode:

It's a simple app that will only do #orgmode syntax capture tasks to text files.

I still need to think about publishing the source as it's AI slurp and I won't provide any support for it. 🤔

Edit: https://codeberg.org/publicvoit/AndroidOrgdownCapture

#PIM

@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

@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

@chiply @petrillic Unfortunately, the syntax #logseq is producing in Org-mode setting is far from being the same as how #Emacs is creating syntax elements: https://karl-voit.at/2024/01/28/logseq-from-org-pov/

Reading logseq files in Org-mode is probably fine. Modifying Org-mode generated/modified content in logseq most probably has some issues.

I've set up #logseq for my wife, now as logseq is going south (adding DB, losing org support, unclear future of file (sync) access,...) and I do have a medium-sized conversion problem with her data. 😞

It's better to start with #Orgmode right away: https://karl-voit.at/2020/01/20/start-using-orgmode/

#orgdown #publicvoit #PKM #PIM

@chiply @petrillic Unfortunately, the syntax #logseq is producing in Org-mode setting is far from being the same as how #Emacs is creating syntax elements: https://karl-voit.at/2024/01/28/logseq-from-org-pov/

Reading logseq files in Org-mode is probably fine. Modifying Org-mode generated/modified content in logseq most probably has some issues.

I've set up #logseq for my wife, now as logseq is going south (adding DB, losing org support, unclear future of file (sync) access,...) and I do have a medium-sized conversion problem with her data. 😞

It's better to start with #Orgmode right away: https://karl-voit.at/2020/01/20/start-using-orgmode/

#orgdown #publicvoit #PKM #PIM

RE: https://lascapi.fr/blog/2026/03/02/create-a-local-first-wiki-an-html-editor-designed-for-personal-knowledge-management/

Hi there, I wrote a mini PoC to illustrate what I'm looking for to edit #HTML files as #markdown or #orgdown text.

I'm challenging every #developer to try to do better with your own stack!

#pkm #pim

RE: https://lascapi.fr/blog/2026/03/02/create-a-local-first-wiki-an-html-editor-designed-for-personal-knowledge-management/

Hi there, I wrote a mini PoC to illustrate what I'm looking for to edit #HTML files as #markdown or #orgdown text.

I'm challenging every #developer to try to do better with your own stack!

#pkm #pim

@mosu @hollma @marlinz Da habe ich eine gänzlich konträre Meinung.

Die Syntax von #orgmode ist #orgdown und wird von vielen Tools unterstützt: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org?ref_type=heads

Insofern ist Orgdown auch eine sehr gute Wahl, wenn man nie vor hätte, #Emacs zu benutzen: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/ + den von mir unten verlinkten MD-Artikel, der das ganz genau herleitet.

Wenn ich mal nicht mehr Emacs verwenden wollen würde, jage ich meine Org files durch pandoc und bin fertig mit der Migration bezüglich der Dateien (nicht Workflows). Leider geht das zu oft nicht so mit #Markdown.

Bitte https://www.karl-voit.at/2025/08/17/Markdown-disaster/ lesen, da die Sache komplexer ist, als man in einem Toot erklären kann.

@mosu @hollma @marlinz Da habe ich eine gänzlich konträre Meinung.

Die Syntax von #orgmode ist #orgdown und wird von vielen Tools unterstützt: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org?ref_type=heads

Insofern ist Orgdown auch eine sehr gute Wahl, wenn man nie vor hätte, #Emacs zu benutzen: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/ + den von mir unten verlinkten MD-Artikel, der das ganz genau herleitet.

Wenn ich mal nicht mehr Emacs verwenden wollen würde, jage ich meine Org files durch pandoc und bin fertig mit der Migration bezüglich der Dateien (nicht Workflows). Leider geht das zu oft nicht so mit #Markdown.

Bitte https://www.karl-voit.at/2025/08/17/Markdown-disaster/ lesen, da die Sache komplexer ist, als man in einem Toot erklären kann.

@konrad Du meinst nicht Markup sondern du kämpfst mit den Unzulänglichkeiten von #Markdown: https://www.karl-voit.at/2025/08/17/Markdown-disaster/

Und ja: es gibt wesentlich bessere Markup Sprachen, wenn man nicht unbedingt der Mehrheit hintennachlaufen muss.

Meine persönliche Empfehlung wäre #orgdown. YMMV

@konrad Du meinst nicht Markup sondern du kämpfst mit den Unzulänglichkeiten von #Markdown: https://www.karl-voit.at/2025/08/17/Markdown-disaster/

Und ja: es gibt wesentlich bessere Markup Sprachen, wenn man nicht unbedingt der Mehrheit hintennachlaufen muss.

Meine persönliche Empfehlung wäre #orgdown. YMMV

My #orgdown static website generator #lazyblorg learned lots of new tricks lately:

- ultracool #TagTree navigation 🏷️
- Atom feeds for single tags and combination of 2 #tags! 🔖
- share on Mastodon :mastolove:
- "random articles published on the same day" 🎲
- published on pypi 🐍
- popular articles recommendation 📈
- generates list of all external URLs for link-checker workflows 🔗
- fixed broken handling of WaybackMachine URLs ⏲️

Source: https://github.com/novoid/lazyblorg 💻

Try out its features on: https://karl-voit.at/ 🤩

It's still mostly a "works for me" solution (true geeks can make it run!) but a *really* fancy one! 😎

#Emacs #orgmode #publicvoit

My #orgdown static website generator #lazyblorg learned lots of new tricks lately:

- ultracool #TagTree navigation 🏷️
- Atom feeds for single tags and combination of 2 #tags! 🔖
- share on Mastodon :mastolove:
- "random articles published on the same day" 🎲
- published on pypi 🐍
- popular articles recommendation 📈
- generates list of all external URLs for link-checker workflows 🔗
- fixed broken handling of WaybackMachine URLs ⏲️

Source: https://github.com/novoid/lazyblorg 💻

Try out its features on: https://karl-voit.at/ 🤩

It's still mostly a "works for me" solution (true geeks can make it run!) but a *really* fancy one! 😎

#Emacs #orgmode #publicvoit

Has anybody ever written a conversion tool from the #orgmode syntax by #logseq to a cleaner version of #orgmode syntax for Emacs?

Background: logseq has a unique interpretation of the #orgdown syntax as each element is also a heading on its own (in order to allow element references):
https://karl-voit.at/2024/01/28/logseq-from-org-pov/

I'm happy to lose element references if they are replaced by "page references" instead somehow.

Has anybody ever written a conversion tool from the #orgmode syntax by #logseq to a cleaner version of #orgmode syntax for Emacs?

Background: logseq has a unique interpretation of the #orgdown syntax as each element is also a heading on its own (in order to allow element references):
https://karl-voit.at/2024/01/28/logseq-from-org-pov/

I'm happy to lose element references if they are replaced by "page references" instead somehow.

@oantolin Well, I haven't used any #staticwebpage generator except my own: #lazyblorg.

The reason why I programmed my own generator was that I could not get the features I wanted to have anywhere else:

- blog posts anywhere I like them: among my tasks/projects/contacts/...
- absolute minimal effort to write a post
- that includes also being able to include images with just mentioning their file name
- navigation via #tags and #TagTrees (combination of different tags - very cool!)
- different types of pages: temporal, persistent, ...
- different Atom #feeds for the users: all articles, just one tag, all articles that combine 2 tags

It just feels "home" to me.

More: https://github.com/novoid/lazyblorg

#orgmode #Emacs #orgdown #staticwebpagegenerator #publicvoit

@oantolin Well, I haven't used any #staticwebpage generator except my own: #lazyblorg.

The reason why I programmed my own generator was that I could not get the features I wanted to have anywhere else:

- blog posts anywhere I like them: among my tasks/projects/contacts/...
- absolute minimal effort to write a post
- that includes also being able to include images with just mentioning their file name
- navigation via #tags and #TagTrees (combination of different tags - very cool!)
- different types of pages: temporal, persistent, ...
- different Atom #feeds for the users: all articles, just one tag, all articles that combine 2 tags

It just feels "home" to me.

More: https://github.com/novoid/lazyblorg

#orgmode #Emacs #orgdown #staticwebpagegenerator #publicvoit

@miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: https://karl-voit.at/2025/08/17/Markdown-disaster/

Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: https://karl-voit.at/2024/01/28/logseq-from-org-pov/

Die DB-Version werden wir garantiert nicht mitmachen.

Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt https://karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: https://silverbullet.md/Markdown

Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔

Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.

#PKM #PIM

@miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: https://karl-voit.at/2025/08/17/Markdown-disaster/

Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: https://karl-voit.at/2024/01/28/logseq-from-org-pov/

Die DB-Version werden wir garantiert nicht mitmachen.

Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt https://karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: https://silverbullet.md/Markdown

Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔

Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.

#PKM #PIM

@publicvoit @sysedit As for the markup syntax itself, I prefer #Orgdown over #Markdown, mostly from habit. But Org wipes its feet on Markdown in terms of functionality, and that's even before the nightmare of Geschmacksvermehrung ("flavor proliferation," if you will permit it).

As long as you're forgiving me: do you really draw your Roman majuscule O with a clockwise stroke of the pen? Because my neurodivergent day has irrevocably been ruined

@publicvoit @sysedit As for the markup syntax itself, I prefer #Orgdown over #Markdown, mostly from habit. But Org wipes its feet on Markdown in terms of functionality, and that's even before the nightmare of Geschmacksvermehrung ("flavor proliferation," if you will permit it).

As long as you're forgiving me: do you really draw your Roman majuscule O with a clockwise stroke of the pen? Because my neurodivergent day has irrevocably been ruined

@sysedit As the president of #orgdown, I can only do so much.

It's dependency on the Org-mode community is obvious - so the community should be president. And this is mixed up with the tooling side of the topic.

Related to the syntax side, my wishes are summarized on https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Contribute.org

Also https://karl-voit.at/2025/08/17/Markdown-disaster/ where I tried not only to explain the issues with #Markdown but also suggest that the syntax of #Orgmode should be used more often to avoid all the current issues with #MD. My suggestion.

I'd urge #pypi to support orgdown for README files.

I'd urge the AI bubble to adapt orgdown for their tool chains instead of MD. There are many cool tools that freshly start with the MD blind alley.

I'd generally urge all the people to prefer orgdown-based workflows in general in particular for current non-text-based workflows. It empowers them. It enables people to adapt workflows and control what happens to their data and it's necessary to avoid #lockin situations.

@sysedit As the president of #orgdown, I can only do so much.

It's dependency on the Org-mode community is obvious - so the community should be president. And this is mixed up with the tooling side of the topic.

Related to the syntax side, my wishes are summarized on https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Contribute.org

Also https://karl-voit.at/2025/08/17/Markdown-disaster/ where I tried not only to explain the issues with #Markdown but also suggest that the syntax of #Orgmode should be used more often to avoid all the current issues with #MD. My suggestion.

I'd urge #pypi to support orgdown for README files.

I'd urge the AI bubble to adapt orgdown for their tool chains instead of MD. There are many cool tools that freshly start with the MD blind alley.

I'd generally urge all the people to prefer orgdown-based workflows in general in particular for current non-text-based workflows. It empowers them. It enables people to adapt workflows and control what happens to their data and it's necessary to avoid #lockin situations.

Here's a screenshot of a business project of mine using that tool.

#Emacs #orgdown #orgmode #visualization

Here's a screenshot of a business project of mine using that tool.

#Emacs #orgdown #orgmode #visualization

RE: https://graz.social/@publicvoit/116075103794827102

#Emacs: After successfully testing it a few times, I just released an extension of the code which visualizes the current #orgdown sub-hierarchy only.

I've added both (visualize sub-hierarchy + whole file) to my #orgmode hydra.

I think the idea of using that #visualization in my daily business grows on me. 🤔

#PIM #PKM

RE: https://graz.social/@publicvoit/116075103794827102

#Emacs: After successfully testing it a few times, I just released an extension of the code which visualizes the current #orgdown sub-hierarchy only.

I've added both (visualize sub-hierarchy + whole file) to my #orgmode hydra.

I think the idea of using that #visualization in my daily business grows on me. 🤔

#PIM #PKM

I just published my newest project that visualizes #orgdown (#Emacs #orgmode syntax) files in a web browser:

https://codeberg.org/publicvoit/orgheadingnetwork

Similar functionality is included in all sorts of tools like #logseq or #obsidian. I personally haven't found a spot for it in my daily workflows but with that project, I may decide to play around with such visualizations any time.

Have fun

#PIM #visualization #visualizations #PKM

I just published my newest project that visualizes #orgdown (#Emacs #orgmode syntax) files in a web browser:

https://codeberg.org/publicvoit/orgheadingnetwork

Similar functionality is included in all sorts of tools like #logseq or #obsidian. I personally haven't found a spot for it in my daily workflows but with that project, I may decide to play around with such visualizations any time.

Have fun

#PIM #visualization #visualizations #PKM

My article about "#Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.

It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.

And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.

🤷

My article about "#Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.

It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.

And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.

🤷

If you're using #lazyblorg as your static website generator: I've updated the project today.

It now used "uv" for dependency management, script invocation and unit test execution. Furthermore, I adapted the code to match the #pandoc version of Debian 13 Trixie.

Although you need to adapt a few things (mainly path settings in a shell script), this update should actually improve and simplify things for you as well.

https://karl-voit.at/tags/lazyblorg/
https://github.com/novoid/lazyblorg

HTH 🙇

#publicvoit #Emacs #Orgmode #orgdown

If you're using #lazyblorg as your static website generator: I've updated the project today.

It now used "uv" for dependency management, script invocation and unit test execution. Furthermore, I adapted the code to match the #pandoc version of Debian 13 Trixie.

Although you need to adapt a few things (mainly path settings in a shell script), this update should actually improve and simplify things for you as well.

https://karl-voit.at/tags/lazyblorg/
https://github.com/novoid/lazyblorg

HTH 🙇

#publicvoit #Emacs #Orgmode #orgdown

@paninid @foone That's why I made https://github.com/novoid/Memacs so that my #PKM is automatically extended by most of my service feeds I'm using.

Shouldn't be that hard to add Mastodon and others. Not sure if my Twitter module is still working because I've left that platform years ago.

#PIM #publicvoit #Emacs #Orgmode #Memacs #orgdown

@paninid @foone That's why I made https://github.com/novoid/Memacs so that my #PKM is automatically extended by most of my service feeds I'm using.

Shouldn't be that hard to add Mastodon and others. Not sure if my Twitter module is still working because I've left that platform years ago.

#PIM #publicvoit #Emacs #Orgmode #Memacs #orgdown

@randomgeek If this helps in your case, I do have an Elisp function called "my-convert-region-from-markdown-to-orgdown()" in my config https://github.com/novoid/dot-emacs/blob/master/config.org which I use to convert #Markdown to #orgdown frequently.

Related: https://karl-voit.at/2025/08/17/Markdown-disaster/

#publicvoit #orgmode #LLM

@randomgeek If this helps in your case, I do have an Elisp function called "my-convert-region-from-markdown-to-orgdown()" in my config https://github.com/novoid/dot-emacs/blob/master/config.org which I use to convert #Markdown to #orgdown frequently.

Related: https://karl-voit.at/2025/08/17/Markdown-disaster/

#publicvoit #orgmode #LLM

@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/

However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.

This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.

#PIM #LML #indirectprofitability #markup #publicvoit #orgmode

@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/

However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.

This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.

#PIM #LML #indirectprofitability #markup #publicvoit #orgmode

@oantolin If that would actually be the reason, then the #orgmode community would have changed its name but embraced the idea. Didn't happen.

I personally do find the name helpful because the main target group is not Org users but normal users, who do know what "Markdown" is and they get some idea transfer to "Orgdown" because of "down".

Nobody I've came across ever said that "Markdown" is negative because of "down". 🤷

To me, "down" symbolizes a "simpler version syntax" according to Lightweight Markup Language (LML) in contrast to complex markup languages like HTML, tex, ...

That said: as long as the org community does not even start to embrace the idea, its name choice is more than irrelevant.

I started #orgdown not as a personal project in the sense that it stays this way. I was hoping for the community to take it away from me and follow the basic idea such that OD is becoming a tool-independent and much better alternative to #Markdown as explained on https://karl-voit.at/2025/08/17/Markdown-disaster/

@oantolin If that would actually be the reason, then the #orgmode community would have changed its name but embraced the idea. Didn't happen.

I personally do find the name helpful because the main target group is not Org users but normal users, who do know what "Markdown" is and they get some idea transfer to "Orgdown" because of "down".

Nobody I've came across ever said that "Markdown" is negative because of "down". 🤷

To me, "down" symbolizes a "simpler version syntax" according to Lightweight Markup Language (LML) in contrast to complex markup languages like HTML, tex, ...

That said: as long as the org community does not even start to embrace the idea, its name choice is more than irrelevant.

I started #orgdown not as a personal project in the sense that it stays this way. I was hoping for the community to take it away from me and follow the basic idea such that OD is becoming a tool-independent and much better alternative to #Markdown as explained on https://karl-voit.at/2025/08/17/Markdown-disaster/

@mattiabunel @SReyCoyrehourcq @mc2 @lukascbossert @raphaellek Thanks for mentioning #orgdown. 🙇

However, the org community still lacks a formal definition of the (whole) syntax.

From orgdown perspective, #od1 specification would be a promising low hanging fruit but as long as the #orgmode community does not embrace the "syntax separate from implementation" idea I tried to coin, this isn't going to happen, I'm afraid.

Maybe from outside of the #Emacs/org community because orgdown as a syntax has many advantages IMO: https://karl-voit.at/2025/08/17/Markdown-disaster/

@mattiabunel @SReyCoyrehourcq @mc2 @lukascbossert @raphaellek Thanks for mentioning #orgdown. 🙇

However, the org community still lacks a formal definition of the (whole) syntax.

From orgdown perspective, #od1 specification would be a promising low hanging fruit but as long as the #orgmode community does not embrace the "syntax separate from implementation" idea I tried to coin, this isn't going to happen, I'm afraid.

Maybe from outside of the #Emacs/org community because orgdown as a syntax has many advantages IMO: https://karl-voit.at/2025/08/17/Markdown-disaster/

Besides not using a better #LML syntax such as #Orgdown, I really do like the way how @silverbulletmd is transparent about its #Markdown downsides.

That's why I extended my article on the downsides of Markdown with it as an example: https://karl-voit.at/2025/08/17/Markdown-disaster/

#SilverBullet #publicvoit #PIM #MD

Besides not using a better #LML syntax such as #Orgdown, I really do like the way how @silverbulletmd is transparent about its #Markdown downsides.

That's why I extended my article on the downsides of Markdown with it as an example: https://karl-voit.at/2025/08/17/Markdown-disaster/

#SilverBullet #publicvoit #PIM #MD

#SilverBullet is a self-hosted, free/open #PIM tool. You could see it as an replacement for other tools like #Obsidian or #Logseq.

I haven't tested it myself yet. One of the downsides from my perspective is the use of #Markdown as its syntax: https://karl-voit.at/2025/08/17/Markdown-disaster/

However, in contrast to anything I've stumbled upon so far, SilverBullet is fully aware of the most important #MD downsides: https://silverbullet.md/Markdown

It even lists its own MD syntax extensions on https://silverbullet.md/Markdown/Extensions 👍

If you're using a MD tool, this is the way to deal with the MD #lockin situation. (Or choose #Orgdown instead.)

Well done, @silverbulletmd 🙇

#FOSS #publicvoit

#SilverBullet is a self-hosted, free/open #PIM tool. You could see it as an replacement for other tools like #Obsidian or #Logseq.

I haven't tested it myself yet. One of the downsides from my perspective is the use of #Markdown as its syntax: https://karl-voit.at/2025/08/17/Markdown-disaster/

However, in contrast to anything I've stumbled upon so far, SilverBullet is fully aware of the most important #MD downsides: https://silverbullet.md/Markdown

It even lists its own MD syntax extensions on https://silverbullet.md/Markdown/Extensions 👍

If you're using a MD tool, this is the way to deal with the MD #lockin situation. (Or choose #Orgdown instead.)

Well done, @silverbulletmd 🙇

#FOSS #publicvoit