Crates.io | yamd |
lib.rs | yamd |
version | 0.14.1 |
source | src |
created_at | 2023-04-04 18:37:29.36629 |
updated_at | 2024-11-20 20:54:32.612963 |
description | Yet Another Markdown Document (flavour) |
homepage | |
repository | https://github.com/Lurk/yamd |
max_upload_size | |
id | 830382 |
size | 141,362 |
YAMD - Yet Another Markdown Document (flavour)
Simplified version of CommonMark.
For formatting check YAMD struct documentation.
Simplified set of rules allows to have simpler, more efficient, parser and renderer. YAMD does not provide render functionality, instead it is a [serde] serializable structure that allows you to write any renderer for that structure. All HTML equivalents in this doc are provided as an example to what it can be rendered.
Escaping done on a [lexer] level. Every symbol following the \
symbol will be treated as a
literal.
Example:
YAMD | HTML equivalent |
---|---|
\**foo** |
<p>**foo**</p> |
To get \
- \\
must be used.
Example:
YAMD | HTML equivalent |
---|---|
\\**foo** |
<p>\<b>foo</b></p> |
CommonMark defines container blocks and leaf blocks. And that container block indicator has higher precedence. YAMD does not discriminate by block type, every node (block) is the same. In practice, there are no additional rules to encode and remember.
Example:
YAMD | HTML equivalent |
---|---|
- `one\n- two` |
<ol><li><code>one\n- two</code></li></ol> |
If you want to have two ListItem's use escaping:
YAMD | HTML equivalent |
---|---|
- \`one\n- two\` |
<ol><li>`one</li><li>two`</li><ol> |
The reasoning is that those kind issues can be caught with tooling like linters/lsp. That tooling does not exist yet.
List of supported nodes and their formatting slightly defers from CommonSpec.