Vibe-coded my first Android app: #AOC which stands for Android #Orgdown Capture. 
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. 🤔
@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
@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/
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!
@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
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 
- "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! 😎
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
@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.
Karl Voit 
🌈 Lascapi ⁂
