orgdown VS github-orgmode-tests

Unfortunately, "Org-mode" (or Orgmode) means two different things: (1) the lightweight markup syntax and (2) the Elisp implementation of a PIM/PKM tool within GNU Emacs.

This seems to be subtle but it results in many misunderstandings and unnecessary discussion issues.

To "solve" this situation, I tried to coin the term "Orgdown" for the syntax alone: https://gitlab.com/publicvoit/orgdown/ and https://karl-voit.at/2021/11/27/orgdown/

There are many use-cases to use Orgdown outside of Emacs and there are many tools that support Orgdown already: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool...

Although I'm using Orgdown and Org-mode for over a decade, I do think that even with an objective point of view, Orgdown does have its benefits from a syntax definition point of view in comparison to Markdown and other lightweight markup languages (LML): https://karl-voit.at/2017/09/23/orgmode-as-markup-only/

Oh and btw, the linked cheat-sheet covers only the most basic Orgdown syntax elements. Within the Orgdown concept, I defined misc "levels" of syntax elements, starting with OD1: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Orgd... This also serves as some sort of cheat sheet I guess.

HTH

There are two reasons why I call Org mode standardized.

> I imagine there aren't really various flavors of Org Mode, but that doesn't make it standardized.

All the implementations that call themselves org-mode follow the conventions set by the canonical implementation - the Emacs org-mode. While this may not sound like a good reason to call it standardized, the practical implication is a vast difference from what you get with various markdown flavors. In the latter case, the only way to make sure that your markdown is correct, is to test it with the target implementation.

The second reason is that there is an actual effort to standardize org-mode - called Orgdown [1]. Org-mode is already more or less uniform across implementations. This effort tries to write it down as a reference. Markdown has a similar effort called CommonMark. But if you want to know why it's different, you have to look at the history of why it isn't called 'Standard Markdown'.

[1] https://gitlab.com/publicvoit/orgdown

And yes, at least my setup fulfills all of your requirements and much more. For starters, I can add tags, date- and timestamps everywhere, generate "agenda" views for days/weeks/months/... which collects all those time-related items and visualizes them, I can link emails/urls/... and links to files which I tag as well, I can search through search strings or regex to find meta-data on files/notes/events/... and it's all in the most versatile file format possible: plain UTF-8 text files containing simple orgdown syntax, the most beautifully designed lightweight markup language (LML) there is IMHO.

Are you aware of orgdown?

If you want to parse Orgdown files yourself, expect to invest some time in setting up a testing environment.

I think we've got a misunderstanding here. Text files (in this case in orgdown syntax format) are files that contain the information in its original form: characters, words, sentences. So you only need a software that lets you open a text file to view it. If you want to modify the information stored in the text files, you need an application that lets you modify text files. In case of orgdown, you can find options on https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org or choose any non-syntax-specific editor of your choice.

So the links are working in Markdown? So Markdown-export is working and your issue starts with the conversion from Markdown to Orgdown?

Well, the difference is that Orgdown, the syntax of Org mode for GNU Emacs is a Lightweight markup language while HTML is a more complex markup language.

Since your notes are in orgdown format, you may use any compatible app that understands to read and probably write orgdown. One of them is GNU Emacs with its org-mode.

Each code block could be evaluated in place, with results appearing inline. Want to test JSON parsing? Write a block, execute it, see the output. Need to try different data structures? Compare approaches side-by-side with immediate feedback. This resembles the classic Lisp REPL workflow but with all the organizational benefits of org-mode. The development document became a living laboratory.

I'm a fan of Org Mode with Emacs [0] and using the app BeOrg [1] on my iPhone.

I have 3 main task files:

- todo.org for things I need to do

- backlog.org for things that I don't have to do now but should do in the future

- inbox.org for any random ideas or notes

The concept of an Inbox was taken straight from Getting Things Done [2].

I have different searches set up in BeOrg so that it is easy to view tasks from each different file.

This is definitely more complicated than a single file, but I like it mainly because it keeps my main task file (todo.org) organized. I also don't go through organizing my files that much either.

inbox.org is just a great place to dump anything, so I usually do a quick scan and either delete everything or refine it to the backlog.org.

For backlog.org, I'll usually just let things sit there and build up. After a while I'll realize that if something has been there for a long time, it probably isn't worth doing - or I already did it, so I delete it.

[0]: https://orgmode.org/

[1]: https://www.beorgapp.com/

[2]: https://hamberg.no/gtd

TIP: When asking for advice in relation to knowledge management, note-taking, etc., be sure to ask for precise details regarding commenters' solutions. There are many people who participate in these discussions who don't seem to take a lot of notes (e.g., one file or paper notepad for all of their notes!).

I have a personal knowledge base that currently includes almost 7,000 files in which I store my notes. I take notes on everything. Every technology. Every product. Every meeting. EVERYTHING.

My notes are stored in Org files that I edit with Emacs and Org mode[1]. Org files are written using a feature-rich lightweight markup language[2] that is much more powerful than Markdown (which is used by alternative note-taking tools like Obsidian). For example, Org supports plain text spreadsheets[3], a feature I love.

Too many people will disqualify Org and say, "I don't use Emacs," while assuming that Emacs users choose Org because we already use Emacs. But I started using Emacs specifically to use Org, not for programming.

But regardless of which tool you end up using, consider organizing your note files using hierarchical tagging. I started using hierarchical tagging for my notes right after Wikipedia was first launched and I saw how effectively hierarchical tagging was being used there. Each Wikipedia article can belong to multiple categories, and each category can belong to multiple categories. This is hierarchical tagging, and it's worked great for my notes. At the bottom of every one of my Org files, there is a list of "parent topics", and each parent topic has a list of parent topics (excluding the "main topics", which have no parents).

[1] https://orgmode.org/

[2] https://orgmode.org/features.html

[3] https://orgmode.org/manual/The-Spreadsheet.html

My favorite static site generator is Org mode[1] for Emacs. Org files are written using a feature-rich lightweight markup language[2] that is much more powerful than Markdown (e.g., plain text spreadsheets). Org files can be exported to HTML[3].

The reason I prefer Org for static site generation is not because I already use Emacs. I actually started using Emacs about 20 years ago specifically to use Org mode.

[1] https://orgmode.org/

[2] https://orgmode.org/features.html

[3] https://orgmode.org/manual/HTML-Export.html

"until recently, Jupyter notebooks were the only programming environment that let you see your data while you worked on it."

This is false. Org-mode has had this functionality for over two decades.

https://orgmode.org/

Work - I use org-mode heavily for my personal project management and note keeping.

While embracing analog tools, I've also refined my digital organization using ORG mode in Emacs. The system has evolved to become more structured and efficient.

Org mode. Org mode is just great for taking notes and organizing tasks. I might write a post on it one day. If you're interested, check out Org Mode in the mean time.

orgmode seems to be a big change after using Notion. However, I fell in love with Emacs, so I wanted to use all the best things. It was easy to set up org-agenda, org-roam, etc. Unfortunately, after a while, I noticed that using a non-standard system(not Markdown) could impact my note-sharing capabilities, as well my ~work~ docs were mostly built with Markdown. So, a note system that uses Markdown. Also, I switched to VIM :)