The go-notebook landing page, https://go-notebook.github.io/, built with Hugo
and the fleet's landing kit
(a Hugo module pinned in go.mod).
-
/playground/: notebooks in the browser, Go and Ruby cells, run in WebAssembly with no server. The deploy workflow builds it with go-notebook/playground's
cmd/build, at the versionplayground/go.modpins, from the notebooks inplayground/notebooks/(it runs each one first and fails if a cell fails). The red "Try it in your browser" button in the hero leads there. -
The hero is the kit's carousel: the README's notebook (
layouts/partials/hero-terminal.html), a notebook with a Ruby cell and what it printed (hero-terminal-ruby.html), and the playground. -
The Ruby card is a real run. It shows
example/waits.mdandexample/output.txt, read from the files. To refresh the output after a bump ofexample/go.mod:cd example go tool notebook run waits.md > /tmp/out.raw go run ./stable < /tmp/out.raw > output.txt
stableremoves the timings and "kept" markers, the only parts that change from run to run; the notebook prints rounded numbers, so the output does not depend on the architecture. Theciworkflow runs it again and fails if the output differs.
hugo server previews the page (Go is needed to resolve the kit).