Chris Sewell

This will also make it easier 😉: https://github.com/executablebooks/markdown-it-myst/pull/31

Before you do this, I think you need to think more closely about what it means to be a myst parser. I'm certainly not against it, but I think it...

Note, for the caveats already mentioned (only Markdown -> HTML, not considering roles/directives), a lot of this will come from https://github.com/executablebooks/markdown-it-py/tree/master/tests/test_port/fixtures and https://github.com/executablebooks/mdit-py-plugins/tree/master/tests/fixtures

Yhe absolutely, its not to say that a "partial spec" won't be useful and is something we can move forward on. But it should be clear what we are trying...

This should be implemented, but... not in this package. It would be a separate sphinxcontrib package, that you would use 'adjacent' to myst-parser/myst-nb. From a quick google, this is an...

Yeh go for it. If MyST-Parser is doing its job properly, you should be able to create/import any sphinx extension (and its roles/directives) that you care to think of 😁

My only issue with the rST/grid-style tables is that they look good for the "simple" examples, but when you come to actually write them, its a pain and then if...

Yeh just thought I'd see if anyone had any other good ideas. Well `list-table` is now part of: https://executablebooks.github.io/markdown-it-docutils/ (at the bottom of the example), and so you will be...

> The constraint of 1-1 correspondence to a notebook format is limiting or inconveniencing the content creators This is not an inconvenience, it is a design principle, that was agreed...

> How far from the original may the notebooks go? It simple really, you should be able to generate all the outputs from the notebook, and they should be ~identical...