Skip to content
STAIGEGAMES
Help center
Start here · 5 min

Prepare your game repo (5-minute checklist)

What STAIGE needs from your GitHub repo before you hit Submit.

STAIGE hosts browser games: a folder of static files (an index.html plus JS, CSS, images, sounds) that runs without a server. If your game already opens in a browser from a folder, you're 90% done.

The checklist

  1. Your game is in a public GitHub repo (private repo support via the STAIGE GitHub App is coming).
  2. There's either an index.html at the root or a package.json with a build script (Vite, Parcel, Webpack, CRA, Next.js with output: 'export'…).
  3. The build output is static files — typically dist/, build/ or out/.
  4. Asset paths are relative (./assets/ship.png, not /assets/ship.png or C:\Users\…).
  5. No secrets in the repo. API keys in front-end code are public to everyone.
  6. Optional: a nice README.md — we show your repo link on the game page.

Not sure? Just paste your repo URL on the Submit page and click Check repo — we read your files (we never run them on our servers) and tell you exactly what's missing.

Ask your AI assistant to make the repo STAIGE-ready
I want to publish this browser game on STAIGE Games (games.staige.world). STAIGE builds my GitHub repo in a sandbox and hosts the static output.

Please check my project and make it ready:
1. Make sure there's a "build" script in package.json that outputs static files (e.g. Vite → dist/). If it's plain HTML/JS, make sure index.html is at the repo root.
2. Make all asset paths relative (for Vite set base: "./" in vite.config).
3. Remove any secrets/API keys from front-end code.
4. Make sure the game works when served from a sub-path (not only from "/").
5. Tell me the exact build command and output folder to enter on STAIGE.
Submit your gameMore guides