Markup for writing #abuse Abuse of markup (markdown) The original Markdown write up reads https://daringfireball.net/projects/markdown/syntax#philosophy 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 https://github.com/vercel/hyper/blob/canary/README.md >  > > <p align="center"> > <a aria-label="Vercel logo" href="https://vercel.com"> > <img src="https://img.shields.io/badge/MADE%20BY%20Vercel-000000.svg?style=for-the-badge&logo=ZEIT&labelColor=000000&logoWidth=20"> > </a> > </p> > > [](https://github.com/vercel/hyper/actions?query=workflow%3A%22Node+CI%22+branch%3Acanary+event%3Apush) > [](https://circleci.com/gh/vercel/hyper) > [](https://ci.appveyor.com/project/zeit/hyper) > [](https://travis-ci.org/vercel/hyper) > [](https://changelog.com/213) > [](https://spectrum.chat/zeit/hyper) ... (Had to escape the HTML.) #links Inline links suck for readability [Anchor](https://linked.website) [[https://linked.website][Anchor]] https://linked.website[Anchor] <https://linked.website|Anchor> 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 somewhat. 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. => https://linked.website 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. #name Matters of naming https://en.wikipedia.org/wiki/Lightweight_markup_language 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. *** #gmi 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.