Chris Sewell

> so, how should people find those developer conventions? So if you open an issue now e.g. in https://github.com/executablebooks/sphinx-book-theme/issues 1. You will now see the community issue templates, then 2....

added the welcome bot 😁

Basically, cookiecutter is maybe slightly simpler for the end user, as you don't have to do any find/replacing, and so good e.g. for https://github.com/executablebooks/cookiecutter-jupyter-book, where it makes it nice and...

> so you're suggesting using "GitHub Repository Templates" rather than CookieCutter? I think at least initially yeh 👍

Yeh exactly, and all of the fixtures in markdown-it-py are similarly language independent; just text files defining the input markdown and expected HTML output

They all have the same format ``` Test title . Input text . Expected HTML . Next title ... ```

Ah no these are comparing to "pseudo" XML of the sphinx syntax tree, rather than the final HTML. There are some that compare to the HTML, but obviously in the...

Well you won't actually find the (initial) commonality in myst-parser, you will find it in markdown-it-py and mist-py-plugins. Everything in JavaScript (well actually I hope you are using typescript 😉)...

But yeh let me know if you need any help

Yep the first thing is that we have parity between the markdown-it extensions we use in python and typescript 👍