Putting this down as a marker for ways in which the markdown component of the lessons could be backed with interactive code executed using a pseudo-remote Jupyter kernel (by which I mean a kernel running in a container in the current users lab context; eg in a Jupyter server kernel launched via the lesson plan config) or where the md/html panel is being served more directly from a Jupyter server (I think scriptedforms serves HTML pages via a Jupyter server, erm maybe?)
This would allow Jupyter kernel backed code to be executed, and the code execution results displayed, from within the markdown scripted element of a lesson rather than a notebook.
There are several demonstrations in the wild of HTML based UIs fronting calls to remote Jupyter servers that process code in a Jupyer kernel environment and return results for display in the HTML page.
Putting this down as a marker for ways in which the markdown component of the lessons could be backed with interactive code executed using a pseudo-remote Jupyter kernel (by which I mean a kernel running in a container in the current users lab context; eg in a Jupyter server kernel launched via the lesson plan config) or where the md/html panel is being served more directly from a Jupyter server (I think
scriptedforms
serves HTML pages via a Jupyter server, erm maybe?)This would allow Jupyter kernel backed code to be executed, and the code execution results displayed, from within the markdown scripted element of a lesson rather than a notebook.
There are several demonstrations in the wild of HTML based UIs fronting calls to remote Jupyter servers that process code in a Jupyer kernel environment and return results for display in the HTML page.
For example: