delve VS orgdown

Don't think I've seen a package that you're referring to, but maybe delve could be a substitute?

I think maybe folks are misunderstanding what you mean by 5. I recall that notion automatically generates tables for you based on some content. If that's what you're looking for https://github.com/publicimageltd/delve might be the package for you.

When I see dashboards based on content I think delve.

If you're using org-roam already, might be worth looking into delve.

Not sure what you mean on the first one. The second one's easiest solution is probably org-transclusion as what you're asking is to translude notes. But other packages with a similar concept of collecting your notes and adding them in a separate buffer are things such as delve or (shameless self plug) zetteldesk. I got no clue how to do the third one. I agree with you on that todos should work in more places, but I also don't know how to fix it. For the one with the calendar, I am pretty sure calfw has an extension that does that. I think calfw-org?

Sounds useful! So I understand you let the user add notes to a special org mode buffer which you then call a ' desktop', right? I have written a similar package for collecting org roam nodes called Delve. It uses a special list view to collect the stuff, however. Your approach is more direct, right? I have considered that approach, too, but I thought it would be nice to have something to navigate from link to its back links to their back links etc... apart from that, I'd actually prefer your kind of approach since it seems more emacsy.

I think you might be looking for delve. It allows to create collections of notes and operate on them.

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.

I'm thinking of a screen that pops up when booting Emacs that only shows the files I was working on recently in large font (maybe as buttons to click on). The file extension should be hidden, so that I may use it with Orgdown files that have long, descriptive file names (most probably within the same directory).