How golrol/pokedex works
Project type and purpose
• This is a lightweight full-stack web application (“Pokedex”) built with Node.js and Express that serves static HTML/CSS/JS pages and JSON-based data about Pokémon.
• Purpose: Allow users to browse all Pokémon, view details of a specific Pokémon, and see “most viewed” statistics using a simple file-based data store.
File structure
• Top level
• server.js – the Express HTTP server entry point
• package.json / package-lock.json – node dependencies (Express, etc.) and scripts
• README.md – project overview and run instructions
• data/ – file-based data store and assets
• pokemon-data/pokemons.json – core JSON data
• pokemon-data/images/ – Pokémon images
• scripts/helperFuncs.js – shared JS logic (e.g., view-count logic)
• styles/*.css – styling for pages
• pages/ – static HTML templates
• index.html – homepage
• allPokemons.html – list view
• specificPokemon.html – detail view
• No external databases or third-party services
README for additional insights
• Running instructions emphasize npm start ⇒ server.js listens on port 3000
• Screenshots suggest three main UI states: homepage, list, detail
Essential details
• Filename(s) used by each component (e.g. pokemons.json, index.html)
• Both dynamic operations (template rendering) and static asset serving