Jupyter/SWAN was ruled out as the primary authoring format for this tutorial (it
might be too complicated with FCCAnalyses), but a one-way export of markdown
material to .ipynb — e.g. via jupytext — could
still be useful for students who'd rather work in a notebook.
Would need some markup convention to mark which fenced code blocks are meant to
be executable Python cells versus illustrative shell/Sindarin/Pythia8-card
snippets, since jupytext doesn't know the difference on its own.
Jupyter/SWAN was ruled out as the primary authoring format for this tutorial (it
might be too complicated with FCCAnalyses), but a one-way export of markdown
material to
.ipynb— e.g. via jupytext — couldstill be useful for students who'd rather work in a notebook.
Would need some markup convention to mark which fenced code blocks are meant to
be executable Python cells versus illustrative shell/Sindarin/Pythia8-card
snippets, since jupytext doesn't know the difference on its own.