Game sites
With AI help for writing, your Claude Code builds the game's website in its repository and publishes it with one command. Tinderbox Works hosts it as static files at your-game.tinderboxworks-sites.com. Every version waits at a preview address until you approve and release it, and any release can be taken back. Without AI, the website guide stays.
New
Build my site with Claude Code.
Launch › Website asks your Claude Code for a one-page site: the Steam wishlist button first, a hero from your key art, three features. It builds the site in website/ in your repository, commits it and publishes it with tinderbox site publish website/.
Preview, Approve, Release.
Each published version waits at your-game--preview.tinderboxworks-sites.com, kept out of search engines, until you approve and release it. The site you released stays live meanwhile. Versions lists the last ten; Back to version N puts an earlier one back.
Static files only, checked first.
HTML, CSS, JavaScript, pictures, video, audio and fonts, up to 50 MB zipped, with index.html at the top. Anything else, a path out of the site's folder or a page that asks for a password is refused before a byte is written, with what to fix.
Changes by asking.
Update my site and Ask for changes send your words to Claude Code as a new AI Agent task; it changes website/ and publishes the next version for you to look at.
Your game's name.
The site lives at your game's name. Names that look like part of Tinderbox Works or a mail server (www, api, login and the like) can't be a game's name. Your own domain comes in a later release.