Markup for writing

Abuse of markup (markdown)

The original Markdown write up reads
Readability, however, is emphasized above all else. A
Markdown-formatted document should be publishable as-is, as
plain text, without looking like it's been marked up with tags or
formatting instructions.

Github: ''hold my beer''

Hyper's README reads
> ![](
> <p align="center">
>   <a aria-label="Vercel logo" href="">
>     <img src="">
>   </a>
>  </p>
> [![Node CI](](
> [![macOS CI Status](](
> [![Windows CI status](](
> [![Linux CI status](](
> [![Changelog #213](](
> [![Join the community on Spectrum](](
(Had to escape the HTML.)

Inline links suck for readability


This isn't a jab at anyone. You can't expect to drop 50 character
URLs in the middle of a paragraph and not have it worsen readability

The common alternative are reference links which, in turn, suck
for editability. The href moves far from the anchor, and you have
a referencing system to manage. Thanks but no thanks.

Another way to solve this problem is to just not. Gemini's Gemtext
markup deliberately ommits syntax for mid-paragraph links.

	=> Anchor

The stupid-simple markup that powers this wiki goes one step further:
it deliberate ommits syntax for anchors too. The href doubles as
the anchor. Link anchors don't belong in body text anyway.

Matters of naming
A lightweight markup language (LML), also termed a simple or humane
markup language, is a markup language with simple, unobtrusive
syntax. It is designed to be easy to write using any generic
text editor and easy to read in its raw form. Lightweight markup
languages are used in applications where it may be necessary to
read the raw document as well as the final rendered output.

These are all bad terms.
Lightweight? Just like YAML and TOML.
Humane? vague and wishy-washy.
Simple? parsing Markdown gets stupidly complex when you actually address the edge cases.
Let's call it what it is: markup for writing. Let's call it Prose Markup.


Gemini's ''gemtext'' markup

Gemtext is almost too simple to justify existing. The few formatting
niceties it provides are not worth losing the 1to1 WYSIWYGness of
serving the same plain text files you edit.