notebook VS djot

How about something like [`input`](magic-link)? I came up with this for https://codeberg.org/macchiato ( though it's not yet implemented in the new project, just in the predecessor, https://github.com/ResourcesCo/notebook ). The backquotes differentiate from non-magic links. (I tried badges, but they aligned weirdly.)

You could use [`data.mrr`](https://evidence.dev/md/value) or any other internal DSL you can come up with.

Another thing you could do is just decide against MDX the format and keep the style and transform inline codeblocks that match.

That you said Markdown to me says you aren't on board with using an incompatible syntax.

Markdown can literally be code. RMarkdown is this. Before I learned of RMarkdown I had written something to extract code blocks with filenames that are visible in the rendered page (since hiding it at the end of the first triple backquote codefence isn't great for visibility). I'm currently working on a notebook tool. https://github.com/ResourcesCo/macchiato/blob/main/scripts/m... https://github.com/ResourcesCo/notebook

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: