Chris Sewell

> Allow glueing of objects defined in other notebooks. IIRC this used to work with older myst-nb version Hey @rossbar, well the problem is that it didn't really "work" fully....

The main initial discussion of MySt Markdown is here: https://myst-nb.readthedocs.io/en/latest/use/myst.html#writing-myst-markdown, which provides a link to the "full" syntax guide: https://myst-parser.readthedocs.io/en/latest/using/syntax.html But yes if you think it would be helpful to...

As per ipypublish, we should we also support output level metadata precedence, and possibly even project/notebook level metadata, i.e. when choosing what metadata to use, precedence would be: output level...

Oh absolutely, we don't need to take it verbatim, but its useful as a guide for what I've found useful before

> e.g. that have regular markdown links instead of {ref} I’m not sure what you mean by this, can’t you already use regular links?

A figure doesn't have a "regular" markdown equivalent though, that's the main reason for using directives; to extend markdown. You can use an image ``, if you want to have...

@amueller I think I see your point-of-view 😬 but I think it would be best if you could provide a minimal example of a notebook, that you think is currently...

> If you open that in Jupyter, it will show two empty markdown cells, aka a white page. Are you sure about that? ````md ```{figure} https://miro.medium.com/max/512/1*d69DKqFDwBZn_23mizMWcQ.png This is my caption...

> there is no way for the user to execute the code while seeing the figures. BTW what you're talking about is also reminiscent of https://jupyterbook.org/interactive/launchbuttons.html?highlight=thebelab#live-interactive-pages-with-thebelab. I'm certainly not saying...

No we use it https://github.com/executablebooks/markdown-it-py