It would be very useful to have something like this. I'm as yet undecided if this should be very bare-bones text only, or if it should be done in a notebook with the opportunity to create plots to help explain.
If we don't want all the code visible, then this might be doable in the current nbsphinx workflow. Otherwise, we could always experiment with a quarto document (specifying to hide code cells) to build a markdown file which is then included in the docs.
This is now well underway, so closing this. Further additions and improvements will happen over time, but I don't think we need an issue for this any more.
It would be very useful to have something like this. I'm as yet undecided if this should be very bare-bones text only, or if it should be done in a notebook with the opportunity to create plots to help explain.
If we don't want all the code visible, then this might be doable in the current nbsphinx workflow. Otherwise, we could always experiment with a quarto document (specifying to hide code cells) to build a markdown file which is then included in the docs.