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, Ruby and R 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. While its first WebAssembly core downloads, the page shows what go-notebook does: the landing kit's loading carousel (playground v0.3.0), never on a cached load. Each cell carries a Go or Ruby badge read from its fence (v0.4.0); cells can be added, edited, run one at a time, switched between Go, Ruby, Julia and Markdown, deleted with undo and moved, with Jupyter's keys (v0.6.0). R cells are parsed and checked in the browser, not run, with the5-rexample (v0.9.0): the CLI kernel has run them since go-notebook v0.10.0, but the WebAssembly cores do not link the evaluator; the default core no longer carries the Julia and R parsers (v0.10.0). C cells are parsed and checked the same way, with the6-cexample, once theplayground/go.modpin is a playground release that has them. -
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).