Isaac Muse

I will be releasing a prerelease hopefully sometime soon. The syntax could change for the final release, but I would need a strong majority. I'm personally indifferent to which form...

One thing that will need a decision is whether block specific options should require yaml fencing or have it optional. Optional means we must require a new line between the...

It's not the new line between config and content that's the problem, it's that it isn't easy to tell config from content, so even if you have no config, you...

The "title" does not span multiple lines. That string can be used for anything though, it is dependent on the block: ``` /// tag | div Div content /// ```...

Yeah, that's why I'm making it configurable via the prerelease just to get feedback. I think it may be hard to tell what you'll like or hate until you try...

> The idea is to bypass having to write demonstrations of MD syntax in duplicates. Currently, the [Material theme has to do](https://github.com/squidfunk/mkdocs-material/blob/13655d68f5c3514f1a03733ef7b2ecb96bc0d2fe/docs/reference/admonitions.md?plain=1#L116-L137) It'll probably be possible to some extent: ```...

Yep, I keep forgetting, but https://pawamoy.github.io/markdown-exec/ does probably already offers what you need in an already-packaged way. There is quite a lot you can do with custom fences. For example,...

Both `:::` vs `///` syntax and mandatory vs optional YAML config fences will be configurable during the alpha/beta stage so that people can try both and help give feedback as...

The first alpha will be focused on syntax feedback. I'm not going to bother documenting the API or anything initially. It will be more to give people a chance to...

Potential fix for this issue: ```python >>> import markdown >>> markdown.markdown('*(i.e. **Tools** > **Board** > **ESP32 Arduino** > ``).*', extensions=['pymdownx.betterem']) '(i.e. Tools > Board > ESP32 Arduino > <board>).' ```...