Web demo · 2026
demo-2026
A small collection of browser demos, served as static files. Pick one below.
Archive Not maintained
Earlier demos. They still open, but get no new work.
FAQ
Do I need to install anything to view it?
No, a browser is enough. Two demos have a build step: the Diagrams editor bundles CodeMirror 6 with esbuild, and Tower defense is built with Vite on PixiJS. The site's container image runs both builds and serves the results as static files, together with the Mermaid and PlantUML engines, which ship as committed browser bundles.
How do I run it locally?
The simplest way is the container image, which runs every build:
docker build -t demo-2026 ., then
docker run --rm -p 8080:8080 demo-2026, and open
http://localhost:8080.
To serve the source tree instead, build the Diagrams editor first
(npm ci && npm run build in diagrams/),
then run python3 -m http.server 8000 from the site root
and open http://localhost:8000. The hub uses absolute links, so
opening the files directly does not work. Tower defense is not built
this way, so its card leads nowhere there: it runs from its own dev
server, npm ci && npm run dev in
tower-defense/, which bakes the sprite atlas and starts
Vite. The bake needs Chrome or Chromium; on a Mac point
PUPPETEER_EXECUTABLE_PATH at the Chrome binary.
Does the page make any network calls?
No. Everything a page needs, including the Mermaid and PlantUML engines, is served from this site, so the pages make no requests to other servers. A shared diagram travels inside the link itself, and the Diagrams editor keeps working offline after the first visit.