Our old tutorials are already getting out of date with changing APIs (the Scikit-HEP one in particular). I think it's a high priority to have our tutorials regularly checked in CI. One way to do that, technically, is to write the tutorials in Jupytext and evaluate the notebooks when generating the pages in GitHub Actions. It would be hard to turn all of our old Jekyll markdown into Jupytext, but no extra effort to start new ones in a new format.
Has this already been fully written in Jekyll?
(Note: this is not only a static webpage markdown, but a version of the template that is no longer maintained by the Software Carpentries.)
Our old tutorials are already getting out of date with changing APIs (the Scikit-HEP one in particular). I think it's a high priority to have our tutorials regularly checked in CI. One way to do that, technically, is to write the tutorials in Jupytext and evaluate the notebooks when generating the pages in GitHub Actions. It would be hard to turn all of our old Jekyll markdown into Jupytext, but no extra effort to start new ones in a new format.
Has this already been fully written in Jekyll?
(Note: this is not only a static webpage markdown, but a version of the template that is no longer maintained by the Software Carpentries.)