How rotoforze/who-s-that-pokemon works
Project type and purpose
• This is a small, static front-end web application called “who-s-that-pokemon,” which implements the classic “Who’s that Pokémon?” game in the browser.
• There is no custom backend or database; the app relies on client-side JavaScript (src/js/*.js) to fetch data (e.g., Pokémon sprites and names) from an external API (likely the public PokéAPI or a similar service).
File structure
• Top-level:
• index.html – the single-page entry point
• LICENSE, README.md – metadata
• src/css/style.css – presentation layer
• src/js/api.js – encapsulates external API calls (fetching Pokémon data)
• src/js/main.js – game logic, DOM manipulation, event handling
• No backend folder, no server or database components—purely static hosting.
README for additional insights
• README only confirms the game’s title and concept; no explicit architecture details.
• We infer that the game uses the DOM, CSS styling, and fetch/vanilla-JS logic to implement game features.