One possibility could be to integrate with sphinx-gallery (cf this example gallery, for instance). A number of projects are using it and it currently allows to export a Jupyter notebook (or launch it in Binder). Adding another button with the Iodide notebook, might be useful.

Though the issue is that it often in project CIs, so it means that the CI would also have to build the pyodide package for the project in question. If we provide a docker image with pyodide, that might simplify things, but I still wonder if this is the right use case...

There is some work afoot to make the Jupyter / Binder buttons configurable, so adding pyodide support would be as simple as adding an option to the sphinx conf.py

I don't think there would need to be a docker image -- it could just link to the pyodide served at https://iodide.io/pyodide-demo. At worst, we'd just need to provide a directory of built files if someone wanted to serve it locally, since there is no server-side component.

@mdboom @rth Can I be assigned this perhaps? Moreover, Can I get some details on what is to be done exactly along with some starter tips as well? Lastly, the above discussion refers to a docker image, is it the same one that we use by running ./run_docker ?

I don't think the docker approach is necessary -- we just need to serve a prebuilt pyodide somewhere (which we already do).

This probably will require coordination with the sphinx-gallery and matplotlib projects. The sphinx-gallery would need to be updated to provide "run in pyodide" as one of the options for the bottom of each example page (or a generic way to add additional links there). For an example, look at the bottom of this page. There are two buttons there generated by sphinx-gallery -- we want to add a third.

Then we'd need to coordinate with matplotlib to update to that new version / configuration of sphinx-gallery.

Thanks for offering to take this on, but just a heads up: large parts of this are community cat herding, more than coding... :)

Just saw this issue come up on Gitter ...

The sphinx-gallery would need to be updated to provide "run in pyodide" as one of the options for the bottom of each example page (or a generic way to add additional links there). For an example, look at the bottom of this page. There are two buttons there generated by sphinx-gallery -- we want to add a third.

As a maintainer of sphinx-gallery I'm sure we could figure out an API. We have opt-in support for optional Binder integration, adding another opt-in integration would be fine. To really make it general, we could easily (at our end) add something like:

sphinx_gallery_conf = {
    ...
    'extra_button_rst': None,
}

where you can have None (default) or a callable that takes a few arguments to say what example is being built (the binder code uses the example filename, gallery_conf of sphinx-gallery info, and a related binder_conf), and returns RST to insert to the sphinx-gallery button RST (e.g., via one more format arg). Then all configuration, etc. can be done at the extra-button-implementer's end, knowing that your RST will be inserted in the right place / the same place as the binder RST.

Then we'd need to coordinate with matplotlib to update to that new version / configuration of sphinx-gallery.

FWIW I added animations support to sphinx-gallery and it was fairly easy to then get it added to matplotlib. Adding pyodide seems like a bigger step, though, so someone might want to check to see if matplotlib folks are on board before putting too much work into it.