How druzhba-specifications/shape-jump works
Project type and purpose
• This is a single‐page, browser‐based HTML/JavaScript game. There is no backend or database—everything runs in the client’s browser.
• Assets are organized under a project/ folder: index.html, css/main.css, and js/main.js. There is also a main.js at the repository root (likely a build script or legacy entry point).
File structure
• Top level:
• README.MD – project description.
• main.js – possibly a bootstrap or build orchestrator.
• project/ – contains all code and assets needed by the browser.
• Under project/:
• index.html – the entry point served to the browser.
• css/main.css – styling rules for the game.
• js/main.js – core game logic, event handlers, rendering code.
README for additional insights
• Confirms it’s a “very cheap” HTML/JavaScript game with no mention of servers or external APIs.
• No external services except static hosting (e.g., GitHub Pages, S3, Netlify).
Elements
• Browser → Static Host (GET index.html)
• Browser ← Static Host (index.html)
• Browser loads CSS/JS assets.
• Another for “Client‐side assets”.
Detailed focus
• End‐to‐end flow: from browser request to asset loading to game execution.