S & A Games

Five browser games in one repo. None has a build step, a package manager, or a single dependency — every game is plain HTML, CSS and JavaScript, and runs by opening a file.

Game	What it is
Gravity Golf	Slingshot mini-golf played through real gravity. Planets pull, suns burn, repulsors push. 9 hand-made holes in three sections.
Castle Defense	Pixel-art tower defense. Four upgradable turret types, a boss every tenth wave, 100 waves to survive.
Pentakeover	Turn-based territory conquest. Five unit types, five factions, five citadels on a procedural map. Computer opponents or hotseat.
Tank Duel	Two-player artillery for one keyboard. Set an angle and a power, fire over the hill, and crater the ground you are both standing on.
Delve	Cave roguelite platformer. Five depths of winding tunnels and tall shafts, one life, mouse-aimed shots, crystal powerups, relics between depths and a Warden at the bottom.

Each game has its own README with full instructions: Gravity Golf · Castle Defense · Pentakeover · Tank Duel · Delve.

Playing

Open any game's index.html in a browser — double-click it, or:

start gravity-golf/index.html    # Windows
open  gravity-golf/index.html    # macOS
xdg-open gravity-golf/index.html # Linux

To serve every game from one place, the way GitHub Pages does, run a static server at the repo root and use the landing page:

npx serve .    # then open the printed URL

Serving over HTTP is also the more reliable way to play Gravity Golf, since some browsers refuse localStorage to file:// pages and its saved progress depends on it. See its README for the details.

Deploying

The site is static, so hosting it is just a matter of serving the repo root — index.html is the landing page and each game lives at /<game>/.

It is deployed on Vercel at https://s-and-a-gam.vercel.app, built from main. Every push to main publishes; every pull request gets its own preview URL.

Nothing is built on the way there — vercel.json sets the framework, build command and install command to none and the output directory to the repo root, so the dashboard serves the tree as it stands rather than inferring a preset and attaching a build to a project that has nothing to build.

Layout

.
├─ index.html         landing page linking to every game
├─ gravity-golf/      Gravity Golf, self-contained
├─ tower-defense/     Castle Defense, self-contained
├─ pentakeover/       Pentakeover, self-contained
├─ tank-duel/         Tank Duel, self-contained
└─ delve/             Delve, self-contained

Each game owns its folder completely and shares no code with the others. That is deliberate: they all happen to draw to a canvas and track a score, but they are free to diverge, and a shared helper only earns its place once the same thing has actually been written twice.

The repo root holds the config the games share:

• .gitattributes pins every text file to LF in the repository and on checkout, so the tree looks identical on Windows, macOS and Linux.
• .gitignore covers every game folder at any depth.

Working on it

Gravity Golf's and Castle Defense's full histories are preserved here. Gravity Golf's is the trunk; Castle Defense's was grafted in with git subtree, every commit keeping its original author.

One wrinkle worth knowing: git subtree grafts the imported tree under a new prefix, but the imported commits still refer to the paths they had in their own repo (game.js, not tower-defense/game.js). So a path-filtered log does not reach Castle Defense's pre-merge commits:

git log --oneline -- tower-defense/       # only changes made since the merge
git log --oneline castle-defense-import   # its 7 original commits

The castle-defense-import tag marks that history as it stood when it came in.

Changes land on a branch and go in through a pull request.