A few notes about the reference page: * The ordered list isn't the best way to write numbered lists. Numbered lists can be: 1. 1. 1., etc. The computer will au

A few notes about the reference page: * The ordered list isn't the best way to write numbered lists. Numbered lists can be: 1. 1. 1., etc. The computer will auto-increment. * Typographic quotes are an extension. I wrote KeenQuotes[0] to solve the quote curling problem and integrated it into KeenWrite[1]. * Document header. I fundamentally disagree with putting formatting instructions into plain text documents, in either AsciiDoc or Markdown. I wrote KeenWrite to completely separate the two. Documents are typeset using ConTeXt[2] and a theme[3]. * Admonitions. Pandoc (and KeenWrite) supports annotations in Markdown. I used them on page 5 of my Impacts Project[4] to insert the spectra. I'd say that annotations are more flexible than admonitions because admonitions are often canned (TIP, WARNING, etc.); whereas, annotations are user-defined. * Sidebars and block titles imply presentation. These are also handled by annotations. * Includes. You can use R Markdown to get includes. Or write an extension. Fair point that it isn't bundled, though. * Custom CSS. Again, avoid mixing presentation and content. Specific presentation logic can be applied by annotating the content, rather than trying to format plain text as though it was HTML. * Definition lists. Supported by Markdown, I use them for a glossary in a novel I'm writing. * Tables. While perhaps not CommonMark, basic tables are widely supported by almost all Markdown implementations. There's a fair amount of incorrect, biased, or outdated information on that page. Here's an example page written in Markdown and made into a PDF: https://ibb.co/mX11vZt https://ibb.co/mX11vZt That's a blockquote (story within a story) with nested annotations (the four simultaneous calls). The bigger picture is this: Why have plain text format wars? Here's an architecture I developed for my text editor: https://gitlab.com/DaveJarvis/KeenWrite/-/raw/main/docs/images/architecture/architecture.png https://gitlab.com/DaveJarvis/KeenWrite/-/raw/main/docs/imag... With that architecture, the source document format doesn't matter. Take any input document, transform it into a structured document format (such as XML), and then typeset it. Pandoc has a similar architecture. [0]: https://whitemagicsoftware.com/keenquotes/ https://whitemagicsoftware.com/keenquotes/ [1]: https://keenwrite.com/ https://keenwrite.com/ [2]: https://wiki.contextgarden.net/ https://wiki.contextgarden.net/ [3]: https://gitlab.com/DaveJarvis/keenwrite-themes/ https://gitlab.com/DaveJarvis/keenwrite-themes/ [4]: https://impacts.to/downloads/lowres/impacts.pdf?page=5 https://impacts.to/downloads/lowres/impacts.pdf?page=5