Chris Sewell

or probably better it could be associated with one of the existing CLI flags, i.e. the verbosity level (set to `True` if `verbose>1`, which equates to `jb build -vv`)

Well basically, why wouldn't you want the behaviour to be: show little output on `jb build`, show more output on `jb -v`, show even more output on `jb -vv`?

Which is exactly why it suggests in the documentation running with the standard sphinx flags: `jupyter-book build -W -n --keep-going mybookname/` https://jupyterbook.org/start/build.html

Ye, indeed, with the refactor as it stands, things like this will now "just work". This is because outputs are "glued" (converted to docutils nodes) directly at the document parsing...

See: https://github.com/executablebooks/meta/discussions/613#discussioncomment-1913981

Heya, yeh that is a strange one, that I don't have an obvious fix for. I'd note though that in https://github.com/executablebooks/MyST-NB/pull/380 I'm removing the dependency on nbconvert, so hopefully this...

Yeh thanks, I guess this would be best implemented in a separate sphinx extension. I would note though that opening the image in its own page is very useful for...

FYI, you know you can include your own JS/CSS: https://jupyterbook.org/advanced/sphinx.html#custom-css-or-javascript

> many Sphinx configurations begin with` {prefix}_option_name` (e.g. `nb_execution_mode`). It would simplify our configuration considerably if we could make assumptions Oh yeh, this is literally how the config is generated,...

Heya this will be fixed once jupyter-book is updated to myst-parser 0.16: https://myst-parser.readthedocs.io/en/latest/develop/_changelog.html#improvements-to-table-rendering