Markdown Processors: Surprisingly Bad

Modern wiki software only fits other people's purposes - none seem designed for someone who has markdown notes and wants to interact with them. Switching wiki software demands changing the notes to adhere to the software's new standards.

Gitlab's wiki uses Gollum, which insists that links look like this:

1Golum is an awful wiki.  See my reviewhere](/wikis/golum_review/).

But while you're writing the file wikis/overview.md, then the natural way to link to wikis/golum_review.md should be a link to that file:

1Golum is an awful wiki.  See my reviewhere](golum_review.md).

The link to another markdown file should say where that markdown file it. The linking system here clearly thinks in terms of a website address, so the user needs to stop thinking in terms of links to notes and start thinking in terms of published web addresses.

The Gitea wiki has no such limit, but somehow manages to find a worse one: it cannot show files inside a directory and they don't plan to change that limitation. This basic directory structure is impossible:

writing/
├── ed.md
├── emacs.md
├── helix.md
└── vim.md
wikis/
├── gitea.md
├── golum.md
├── links.md
└── vim.md

Instead, everything must remain in the root directory.