Making room for Godot in a static site

The portfolio is static HTML, but the games do not need to be treated like awkward attachments. Each project page can own a stable play surface and load a Godot web export from the same origin.

The boundary

Astro owns the page chrome, project metadata, and writing. Godot owns the canvas, input loop, audio, and game state. Keeping that boundary clear means the rest of the site stays fast even when one project needs a larger WebAssembly payload.

The eventual build path is intentionally simple:

1. export the game for the web;
2. place the exported files under the project’s public game directory;
3. set the project’s browserBuild.src;
4. rebuild the site.

This sample note will become a deployment checklist after the first real browser build lands.