Version tags, known issues, and scars that still convert. Fourth wall stays load-bearing.
// featured case study · studio system · 2026
A front door for the games.
Not the consultancy in a novelty hat.
A second Netlify site in the same monorepo, built so contract visitors can cross into the games shelf without hunting individual title domains, and so the games can speak in a louder voice.
- Product problem
- Titles had sites. The studio did not.
- Architecture
- Separate host, same monorepo, shared art where it helps.
- Brand
- Patch notes as marketing. Loud on purpose.
- Catalogue
- Coverflow, Big Box, and orbit views over real storefronts.
// the product problem
The consultancy homepage is the wrong costume for a games roster.
Individual titles already had destinations. Visitors who landed on threesided.com for contract work had no clean path into the party-game and browser-RPG shelf. The shelf had no place that admitted it was a marketing surface.
// product decision
Two sites. One repo. Different volumes.
Root stays the studio consultancy. apps/games deploys as its own Netlify project on games.threesided.com. Shared favicons and art where they help. Separate CSS, copy, and tone where they should not. The homepage is a build log. The showcase owns deep catalogue browsing.
Cinematic CSS coverflow, Big Box theatre, and collector orbit. Every title opens a full storefront.
Product pages keep one interactive Three.js case each. The multi-title shelf uses lighter CSS depth so the art stays in charge.
// the system
A marketing site that documents like release notes.
Astro 7, hand-written CSS, and Three.js where a title earns it. Games and tools keep separate doors. The DND Suite gets a family storefront of its own.
- 01 Stage
Homepage hot-build, roster, principles, and a live changelog panel.
- 02 Storefront
Each /games/<slug> page carries gallery, platforms, stack, features, and patches.
- 03 Shelf
Showcase routes switch between coverflow, Big Box, and orbit without a second codebase.
- 04 Handoff
Portfolio case studies explain machinery. The games site sells the experience.
// the product, in frames
Screens from the shipped surface.
// what it holds
Proof, not adjectives.
The useful bits: what changed for the people using it, and what the stack actually is.
Same mark and accent system, turned up. Related, not identical.
Roster, sheets, changelog, and family pages without scattering domains.
threesided.com explains how it was built. games.threesided.com sells the night.
- Astro 7
- TypeScript
- Vanilla CSS
- Three.js
- WebGL
- Netlify