John MacFarlane

No, this is about creating the figure itself: an environment that may contain one or more images, or perhaps other things, plus a caption and a label that can be...

In pandoc's markdown that will produce a figure (`implicit_figures` extension), but we haven't implemented that here. I think I'd prefer to have something more explicit for generating figures.

I don't much like TOML for this purpose; it requires you to quote strings, and it makes it very inconvenient to represent e.g. an array of references.

reStructuredText does something interesting here. They re-use definition list syntax; when a definition list occurs right after the document title, it is interpreted as metadata (IIRC). Nice thing is that...

I'd like to avoid English command words. On the other hand, if the alternative is Perl-like line noise, then it's a hard call.

Unlike with commonmark, compatibility isn't a major goal for this project. I'm trying to imagine something clean and principled, unburdened by compatibility requirements.

djot does already have syntax for marking insertions, deletions, and comments.

Critic markup syntax for substitution: ``` {~~isn't~>is~~} ``` I don't know. To me, this seems just as readable, if not more so: ``` {-isn't-}{+is+} ``` It's also shorter.

It's not really necessary, but in heavily-interlinked systems of documents, like notes, it is more convenient to write `see [[Tigers]]` than `see [Tigers](tigers.html)`.

> [[page]] seems inconsistent with djot principles Which principles?