[andrewthomaslee]

Requested by Andrew · project thread

Before: the docs site and the slide deck are two unrelated builds, and nothing publishes them.

After: nix build .#documentation also contains the built deck at /slides/, and a new Presentation page embeds it. The deck still builds on its own with nix build .#slides, and the built index.html now also opens straight from disk. A GitHub Actions workflow runs nix flake check, builds the site and deploys it to GitHub Pages on every push to main. Pull requests run the check and the build without deploying.

Pages has to be enabled once: Settings → Pages → Source: GitHub Actions.

How:

• Inlined Markdown: packages.slides folds each data-markdown="x.md" deck into its HTML as a <textarea data-template>, using flake-parts/scripts/inline-markdown.py. This means the copy inside the docs carries no .md file for MkDocs to render as a page.
• Docs build: documentation.mkdocs-preBuildHook copies the built deck into docs/slides.
• Presentation page: the embed uses plain HTML links. MkDocs checks Markdown links in strict mode, and the deck doesn't exist during watch-documentation, so a Markdown link would break the live preview.
• Workflow: .github/workflows/pages.yml runs on ubuntu-latest with cachix/install-nix-action, upload-pages-artifact and deploy-pages.

Verified locally:

• nix flake check passes.
• In headless Chromium, the iframe on /presentation/ renders all 9 slides.
• The built deck renders from file:// with no console errors.
• watch-documentation starts cleanly.

🤖 Generated with Claude Code

https://claude.ai/code/session_0134mfNgkokU4oenUnqXigQz

---

Generated by Claude Code