And now for something completely different…
In our demo scenario, we deploy the notebook-like RetroLab to a Git(La|Hu)b pages branch in CI. Other approaches include ReadTheDocs (used by the main repo).
We’re very close to being able to host everything (including wheels for the python kernel) offline, so no external CDN calls would be made… unless the user asks for it, e.g. fetch('http://malicio.us')… but they could have done that anyway with a real kernel.
User code is actually executed within the user’s browser. There aren’t a lot of guardrails (as always, very easy to call custom JS) so it’s important Lite sites are served from a separate domain than the main Git(La|Hu)b API… or not, if that’s the whole point of the thing.
We don’t have a solid assessment story at the end, however: one could imagine any number of approaches, from redirecting to existing stores of opportunity e.g. issues, pull requests, mailto links, etc.