How stevenhao/set works
Project type and purpose
• This is a single‑page, browser‑based implementation of the Set card game.
• There is no dynamic backend or database—everything lives in the public/ directory and is served as static assets over HTTP(S).
File structure
• Top‑level files:
• README.md – project description, build and deploy instructions
• deploy.sh, dev.sh – scripts to push static files to a server via rsync
• public/ directory (the entire frontend):
• index.html – application entry point
• index.css – global stylesheet
• *.coffee – game logic split into model.coffee, view.coffee, controller.coffee (an MVC‑inspired layout)
• powerset.html, superset.html, hiddenset.html – variant entry points for different game modes
README for additional insights
• Describes a build step: compile .coffee → .js using the CoffeeScript compiler
• Deployment is done by running the shell scripts, which use rsync to sync the entire project to a remote set/ directory on the server
Elements
• Clear component labels: Developer, Build, Deploy Scripts, Static Server, Browser
• Code → Build → Artifacts → Deploy → Server → Browser
• Within the browser: user input → Controller → Model update → View rendering
• Rectangles for system components (Build Server, Static Server, Browser)
Final advice
• Be very detailed: capture every stage from development to user interaction
• Don’t overthink—since it’s a static site, simply enumerate the components (IDE, compiler, scripts, server, browser) and show how they connect