org-pandoc-import VS orgdown

You can try to use https://github.com/tecosaur/org-pandoc-import

Ooh, org-pandoc-imoort would be perfect for this! It'll convert your markdown files to org on import, provided you have pandoc installed, and then back when you save!

Orgmode's page about tools about import & export actually includes both to an entry about export to pandoc (ox-pandoc) as well as import from pandoc (org-pandoc-import).

It's always nice to see someone from the humanities interested in Emacs. I suspect that you'll find the best experience by using Org mode + Pandoc. This will let you write in a rather nice plaintext environment, and then export that to a .docx file. I don't think the styling will be great (could well be wrong though), but it should work fairly well :) Importing (from .docx to .org) is likely to be less smooth, but still decent.

The use case is: I maintain a little blog of my own and I use org mode for writing. I previously used Hakyll and Pandoc, but switched to Gatsby a while ago. Because Gatsby doesn't (didn't?) support using Pandoc in the pipeline, I switched to Orga, which provides a transformer for Gatsby. However, I've had a number of issues with Orga, so I'm looking for a replacement. I considered using org-pandoc-import and storing the documents as markdown instead, but I couldn't make it work properly. I'd also like to be able to utilize features such as (sequential) code block line numbering and links to code lines, which I haven't been able to find any support for outside of pure HTML export.

https://github.com/tecosaur/org-pandoc-import might help?

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).