Another item missing from Markdown is a standard syntax for cross-references and citations: https://talk.commonmark.org/t/cross-references-and-citations/4013 h

Another item missing from Markdown is a standard syntax for cross-references and citations: https://talk.commonmark.org/t/cross-references-and-citations/4013 https://talk.commonmark.org/t/cross-references-and-citations... Is the tweeted list a little outdated now? > no id's in headers A natural ID is derived by changing the header to lowercase and replacing spaces with hyphens, such as: https://github.com/DaveJarvis/keenwrite/blob/master/docs/screenshots.md#pdf-themes https://github.com/DaveJarvis/keenwrite/blob/master/docs/scr... > no syntax for adding classes Pandoc introduced ::: annotation blocks that produce div tags with classes. I discuss this length: https://dave.autonoma.ca/blog/2020/04/28/typesetting-markdown-part-8/#annotations https://dave.autonoma.ca/blog/2020/04/28/typesetting-markdow... My editor, KeenWrite[0], also supports annotation syntax: https://user-images.githubusercontent.com/2131950/161400266-e84cff56-f05c-4e29-a81d-69b10f97907c.png https://user-images.githubusercontent.com/2131950/161400266-... > any number will do in ordered lists Isn't that either a presentation issue or a feature? I prefer numbering lists with a sequence of 1., 1., 1., 1., to let the computer automatically increment the number. Makes adding/removing items easier. Being able to arbitrarily change the numbering seems weird, though potentially useful. > code blocks (4 spaces) over code fences (```) Not sure why this is a design mistake. When reading technical documentation, indented stands out more. IMO, it improves readability for short snippets (where syntax highlighting doesn't matter). > can't nest Markdown in HTML in Markdown Depends on the Markdown flavour, doesn't it? [0]: https://github.com/DaveJarvis/keenwrite#download https://github.com/DaveJarvis/keenwrite#download