Replying to Avatar fiatjaf

The original Markdown idea didn't have the []() URLs, the URLs were exclusively referenced at the bottom, it was much more readable, see https://daringfireball.net/projects/markdown/index.text

That reminds me of another bad property of Markdown: multiple ways of doing the same thing (a bug that likely was not present in the original idea -- but also I'm not saying the original was perfect or anything): there are 3 ways of doing links, 2 ways of doing each level of heading, at least 2 ways of doing ordered and unordered lists, 2 ways of doing bold and 2 ways of doing italic, and 2 ways of doing code blocks, arguably also 2 ways of doing quote blocks.

have you looked at asciidoc?

i am using it on my docs in my repos now, for one major reason being that it has an actual working built-in table of contents, and its tables are sane and readable without being rendered, the links are simple to understand: link:http://example.com[display text] and it lets you do a bunch of other cool stuff, the quoted preformated text is just two spaces indent though also you can use many of the more familiar things like backtick fences and single backticks `like this`

we will be using it as a standard for #alexandria because that is a book oriented application, also, so, it will happen

long form nostr posts have kinda not really caught on because the clients are crappy and actually without a reward people are not that interested in doing anything other than short notes

but it would be nice to be able to at least do sections, headings, quoted source code type blocks, and similar, for discussions

Reply to this note

Please Login to reply.

Discussion

i should also point out, we are using it with #alexandria because it allows the creation of composite documents, with asciidoc it's possible to compose a series of separate documents together to become a composite document