← Back to all builds

Placeholder build

You are looking at a build

This page is a stand-in for your game. It lives at builds/2026-08-20/index.html, and the link you followed to get here was generated automatically from that folder's name. Replace it with a real build and the list on the front page updates itself.

Setting up your copy

1. Generate a repository from this template

   On GitHub, use Use this template → Create a new repository. You get your own copy with none of this repo's history.

2. Turn on Pages

   In your new repo: Settings → Pages → Source, and choose GitHub Actions. Every push to main then rebuilds and republishes the site on its own.

3. Write your own copy

   Edit config.json at the root of the repo:

   {
     "name": "Your game's title",
     "author": "Your name",
     "description": "A sentence or two about the project."
   }

   name and author are required. description is optional — leave it out and the paragraph simply doesn't appear.

4. Add your first build

   Drop the folder into builds/, named for the day the build was made:

   builds/
     2026-09-14/
       index.html
       css/
       js/

   Commit and push. That's the whole process — you never edit the front page by hand.

5. Delete this placeholder

   Remove the builds/2026-08-20/ folder once you have a build of your own, and this page disappears from the list.

Naming build folders

A folder is only picked up if its name is a date. Add a 24-hour time when more than one build lands on the same day.

Folder name	Shows up as
2026-09-14	September 14, 2026
2026-09-14-0930	September 14, 2026 · 09:30
2026-09-14-1745	September 14, 2026 · 17:45
2026-09-14-174530	September 14, 2026 · 17:45:30
2026-09-14-1, 2026-09-14-2	September 14, 2026 · #1, #2

That last form is for when you know the order but not the clock time. Four or six digits is read as a time, one or two as a sequence number.

All of these mix freely — a folder with neither time nor number counts as that day's earliest build. Anything that isn't a valid date is skipped, so you can keep notes or working files in builds/ without them showing up.

What makes a build work here

• The folder must contain an index.html. That's the file the front page links to.
• Every path inside it has to be relative — css/style.css, not /css/style.css. The site is served from a subfolder, so a leading slash points at the wrong place and the build loads blank.
• Keep each build self-contained. Nothing outside its own folder, so a snapshot from 2026 still runs years later even as the rest of the repo changes.
• Don't edit builds after the fact. The point is what the game actually was on that day.

Working on it locally

To see your changes before pushing:

node scripts/generate-index.mjs
python3 -m http.server 4321

Then open http://localhost:4321. The first command rebuilds the front page from your builds/ folders; the second serves the site the way GitHub Pages will. Opening index.html straight from disk works too, but a server matches the real thing more closely.