Eric Larson

> If I'm missing something, and if anybody knows a way to keep compatibility, please let me know! Could you instead override the CSS changes in a `.css` file that...

Another idea is to decide how to structure your HTML elements (or whatever else you need to update for latest SG) based on the SG version. Then after a year...

Looks like a reasonable start to me, @choldgraf can you look / comment?

I'm not sure we want this, to propertly identify an image you'd need to know the examples dir, example filename, and image number. The only thing you currently need on...

AFAIK nobody has tried documenting a package inside a namespace. It's likely some fixes are required at the sphinx-gallery end for this. Do you want to try making a PR?

One path forward is to nest any `nbconvert` imports in functions that need it. Then projects that don't need to use it (i.e., all existing projects) don't need to change...

> I'm still in doubt if I should do a PR to this repo, or if is should be a new package. This new proposal looks like a generalization of...

(This would allow SG to stay relatively lean and backward compatible, and s-g-e could have the heavier CI dependencies needed to test and build the docs for the `nbconvert`-based extensions.)

> My focus is to get something lightweight working, with minimal code and effort. Unfortunately this will probably conflict with the refactoring idea, since I think it would be a...

@maartenbreddels not sure if you are still working on this or have new ideas, but basically I lay out a plan in https://github.com/sphinx-gallery/sphinx-gallery/issues/441#issuecomment-493782430 about how we can support other modules....