djot VS Zato

I know this doesn't solve your problem directly, but I recommend people to try out Djot[0], a markup language from the author of CommonMark.

Djot has a single well-defined spec, and most of the basic formatting has the same syntax as (a) Markdown, so switching is pretty painless. It has as a main goal to be legible and visually aesthetic as-is, just like Markdown.

What Djot adds is its _predictability_. Nested formatting, precedence order, line breaks behavior, nested blocks, mixed inline and block formatting, custom attributes are all laid out precisely in the spec in a thought-out manner. Till this day I still can't remember how to put line break within a list item in Markdown (and I'm sure there're more than one way).

[0]: https://djot.net/

Worth noting that the author has also created a markup language, djot.

https://github.com/jgm/djot

Every time I see people doing something with Markdown, I wish they just replace it with support for Djot[0] instead. It is a Markdown alternative by the creator of Pandoc and CommonMark that fixes all of the most egregious mistakes, while being legible and visually pleasant as-is. It is also syntactically similar to Markdown, which should ease adoption.

[0] https://github.com/jgm/djot

Are you using markdown? It might make sense to look at 'djot' as well: https://djot.net/; it's a new 'light' markup language conceived as a successor to commonmark; development is led by none other than John McFarlane (author of pandoc, & also led commonmark standardization) Djot makes it really easy to attach arbitrary attributes to block elements as well as inline elements; and the parser records source positions in the output -- all of which makes it really convenient keeping track of elements changing position or value.

I have a simple script that sends a djot buffer (https://github.com/jgm/djot) to the parser, if there's a change, on the CursorHold event.

Since you mentioned you were considering moving to CommonMark, have you had time to look into Djot (also by jpm)? Djot is meant to be easier to parse, and I'm planning to write a tree-sitter grammar for it.

Another recent development here is https://djot.net/ (by the pandoc author). It indeed thoroughly solves both:

Yes, the article is correct, there is a market for Markdown sites and related products.

Our Zato website is in Markdown: https://zato.io

We have a purpose-built static site generator, which makes sense in our case because:

* The resulting site is very fast, seeing as there is no need for runtime generation of any assets / HTML / any kind of resources

* It is easier for developers to work on documentation because they already know Markdown

* It is easy to statically apply filters such as spell checkers for multiple languages during the build

* Various optimizations can be applied, e.g. incremental builds or on-demand builds

The drawbacks are:

* Non-technical translators may have a difficult time working with anything but either their own specialized tools or MS Word and they consider Markdown to be "advanced"

* Sometimes you work with writers who are not technical at all and who will not understand what a build system is even if they are open to the idea of learning Markdown itself

Thus, there is a market for a lightweight CMS that would enable non-technical people to author Markdown in their browsers, without a need for any command line usage.