You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MkDocs' Markdown has "admonitions" as a syntax extension.
While quoting the "title" seems a bit idiosyncratic, we could support something similar:
!!! keyword Inline content for title
4-space indented block contents...
Compare to the "fenced divs" syntax, it allows for something simpler for environments needing two arguments (where Markdown can be used in both). I mean, it's doable with fenced divs, but it looks a bit "clumsy" / less straightforward in my opinion, and also makes the task of the writer afterwards less obvious for identifying and extracting the necessary bits.
::: { .keyword }
block contents...
:::: { .title }
Content for title
::::
:::
I would tend to think it would bring a more natural way to typeset some things, with an immediate sensible use -- as shown in the PoC below.
I wonder what other writers using Markdown would have to say (or how they'd address that type of need with other means).
The text was updated successfully, but these errors were encountered:
And in addition to the above note on fenced dives, Pandoc also seems to have "some" of the same idea with fenced divs with just a class name: jgm/lunamark#58
(Though it doesn't address the "title" of such blocks.)
Too many possible ways, and now that we also have Djot support, we might need to think to a better approach that just adding our own syntax extension --> switching milestones.
MkDocs' Markdown has "admonitions" as a syntax extension.
While quoting the "title" seems a bit idiosyncratic, we could support something similar:
Compare to the "fenced divs" syntax, it allows for something simpler for environments needing two arguments (where Markdown can be used in both). I mean, it's doable with fenced divs, but it looks a bit "clumsy" / less straightforward in my opinion, and also makes the task of the writer afterwards less obvious for identifying and extracting the necessary bits.
I would tend to think it would bring a more natural way to typeset some things, with an immediate sensible use -- as shown in the PoC below.
I wonder what other writers using Markdown would have to say (or how they'd address that type of need with other means).
The text was updated successfully, but these errors were encountered: