FYI: I released includes functionality that is quite powerful syntax and could be ported to CommonMark IMO.
{{ path }}
{{ path #section }}
{{ path @key:value }}
{{ path #section @key:value }}
{{ path @shift:N }}
Especially @shift:auto is useful to shift the headers down to the next level automatically on include.
It is online with demo apps (e.g. this) to check out and a nice side-effect: You can also in websites include (DB driven) snippets inside documents, so it is like mini-templating the safe way (including the same markup only). I didn’t find any measurable issue here.
Do you see any concerns? Or could this be ported in some capacity?
For MD specifically once has to disable HTML probably when using it in online context - or sanitize extra, since user input should not be trusted.
Locally, it should be fine to allow any and all syntax.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Using link reference definitions as invisible structural markers — sound, or a bad idea? | 0 | 10 | 27-09-2026 |
| 2 | Making Markdown a first-class citizen of the Web | 0 | 7.3 | 14-09-2026 |
| 3 | Three things I decided not to parse, building a live-preview editor | 0 | 12.69 | 27-08-2026 |
| 4 | A list of common mistakes that people make while writing Markdown | 0 | 10.4 | 20-08-2026 |
| 5 | MD Studio - a personal HTML-to-Markdown project | 0 | 14.96 | 05-09-2026 |
| 6 | A (somewhat) formally verified implementation of Markdown | 0 | 12.32 | 08-08-2026 |
| 7 | Interoperable markers for automatic heading numbers | 0 | 7.72 | 27-07-2026 |
| 8 | Interesting trend of executable markdown readme projects (Syntax comparison) | 0 | 11.72 | 28-08-2026 |
| 9 | Should fenced code blocks always remain visible as source? | 0 | 15.26 | 03-10-2026 |
| 10 | Markdific - A better tool to open, read, edit and export Markdown files | 0 | 7.23 | 05-10-2026 |