Chris Sewell

> I am wondering also whether it is a desirable feature in the context of building a book/documentation Well I'm not necessarily as bothered about the numbering, its more to...

Also, in the latter example, it would not be clear what is executed code and what is static code, e.g. ````markdown ```python a = 1 ``` ```{jupyter-execute} b = 2...

Or here I just use `In:` and `Out:` https://aiida-crystal17.readthedocs.io/en/develop/user_guide/calc_main.html

I could even envisage referencing these cells, e.g. ```rst In :cell:in:`1` we calculated something, now in :cell:in:`5` we calculate something else. ```` where the reference would link to the prefix...

This is the configuration that nbsphinx uses: https://nbsphinx.readthedocs.io/en/0.5.1/usage.html#nbsphinx_output_prompt

> Ah, that's neat, although I'd be concerned about unnamed references Yeh more robust would be labelling cells in their metadata (for notebooks) / a label option on the `jupter-execute`...

Actually, for a more subtle approach, I quite like: ```css div.cell div.cell_input { border-left-color: green; border-left-width: medium; } ```

I've added this now in https://jupyter-cache.readthedocs.io/en/latest/using/api.html, IMO it looks nicer and is easy to read through

Heya, I would be hesitant to tie myst-parser/myst-nb to markdown-it-py: the use of markdown-it-py is a design implementation that could change in the future and, as such, is not exposed...

I would be reticent to start trying to accommodate for every theme here, of course people can already overload the CSS with their own via sphinx. I did already notice...