Chris Sewell

Note this has some overlap with #28

Would something as simple as having multiple `!` be ok? ``` ! ```

+1, I feel most Markdown users don't know about / understand this syntax feature, and thus it leads to surprising results

Could you expand on this a bit. What's the physical setup you envisage for the repo/workflow?

Is there a way to hook into setuptools/distutils etc, to run arbitrary pre-build code (to create the compiled CSS files)? It looks like you can maybe use the [cmdclass option...

Ah brilliant thanks @akhmerov, have you found any drawbacks/gotchas with this approach?

perfect ok ta, I can give a go at setting this up for sphinx-panels. If that goes well can then try rolling out to sphinx-book-theme, which is a little trickier,...

Yeh quite possibly. For simplicity, I'm initially just going to put all the code in sphinx-panels. Then we can look to extract the repo independent stuff into a separate package.

No I haven't really used them before, but would be +1 for using them where appropriate. In general, in the parser, using `self.reporter.error`/`self.reporter.critical` already handles the error correctly I think,...

Yeh this is a tricky one. MyST does not currently support field-lists, outside of front-matter, and so you would need to e.g. "tell" myst that you want these fields shown...