Making Markdown a first-class citizen of the Web

Дата публикации: 14-09-2026 12:08:56

I also somewhat agree with @notriddle’s point.
Every part of the web platform has a way to grow. HTML ignores tags it doesn’t know.
CSS drops rules it can’t parse. In both cases the old document still means what it
meant, and the new feature just doesn’t apply to it. Markdown has no such room. It
doesn’t ignore what it doesn’t know, it re-reads it. Plain text today can be syntax
tomorrow. Or least it would also need some versioning or alike.
GitHub’s alerts are a small example: > [!NOTE] used to render as a blockquote with
some literal text in it, and now it’s a callout box. Fine for a site that can decide
that for itself. Not fine for a parser in the browser, which either freezes forever or
changes what old documents mean, quietly and with no error.
@pugmire is right about CSS - Markdown being defined in terms of HTML is what makes styling easy, and it’s also why there’s not much to standardize. Two implementations give you two different trees. They only agree at the end.
The ADF mention is interesting for what’s missing. A schema’d tree is good for tools
and agents, but nobody writes it by hand. Markdown is the opposite: easy to write,
nothing agreed underneath. And the flavors You’d want both - a text syntax where the spec is the
document model, and syntax kept unused on purpose so new features don’t rewrite old
files.
I work on a Markdown-ish new language incl clear spec/AST that should also solve some of the issues above called Carve.
But still doesnt belong in a browser. Having this work out of the box easily due to WYSIWYG, TreeSitter, TipTap etc. seems still easy enough without the lock-in of the syntax for years to come.

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Using link reference definitions as invisible structural markers — sound, or a bad idea?	0	10	27-09-2026
2	A list of common mistakes that people make while writing Markdown	0	10.4	20-08-2026
3	MD Studio - a personal HTML-to-Markdown project	0	14.96	05-09-2026
4	Three things I decided not to parse, building a live-preview editor	0	12.69	27-08-2026
5	Transclusion or including sub-documents for reuse	0	11.72	26-09-2026
6	A (somewhat) formally verified implementation of Markdown	0	12.32	08-08-2026
7	Interesting trend of executable markdown readme projects (Syntax comparison)	0	11.72	28-08-2026
8	Markdific - A better tool to open, read, edit and export Markdown files	0	7.23	05-10-2026
9	Let table rows wrap over several lines	0	7.98	03-10-2026
10	Interoperable markers for automatic heading numbers	0	7.72	27-07-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 7.3. Источник: talk.commonmark.org.