How raulsr92/tallejavascript-videojuegos works
Project type and purpose
• This is a small, static, browser-based video game built purely with HTML, CSS and JavaScript.
• There is no backend service—everything runs in the client’s browser, using files: HTML for views, CSS for styles, JS for game logic, DOM updates and local storage for high-score records.
• Purpose: deliver an interactive “collect bombs” game with levels, timers, animations, start & end screens, and record keeping.
File structure
• index.html – the main entry point that loads the game.
• game.js & gameProfe.js – core game logic; two versions or modules containing movement, collision, fire effect, level progression.
• maps.js – definition of level layouts (maps, coordinates of bombs, walls, player start).
• records.html & records.js & records-style.css – separate “high scores” page showing saved times.
• styles.css & records-style.css – global and record-page styling.
• assets/ – images, sprites, sound effects used by the game.
• .gitignore, LICENSE, README, config folders are standard but not part of runtime.
README for additional insights
• Confirms it’s a Platzi workshop project, highlights features: fire on collision, timer with two decimal places, interactive cards, start screen, win animation.
• No external data services—records likely persisted in localStorage.
Elements
• Blue for “UI/HTML/CSS components”
• Green for “Game Logic modules”
• Orange for “Data stores (maps, localStorage)”
• Gray for “Assets”
Final advice
• Be detailed: break out each JS module into its role (timer, collision, UI overlay).
• Lifecycle: Start Screen → Game Loop → Win/Lose → Record Save → Records Page.
• Interactive elements (keyboard input, timers, animations), even though there’s no server.
• This level of detail ensures any engineer sees exactly how the front-end static game is structured and plays.