How guilhermerm-a1/sacidex works
Project type and purpose
• This is a purely front-end, static web application (“Pokedex”) that runs entirely in the user’s browser.
• It consumes the external PokeAPI to list Pokémon and show their details, applying HTML5, CSS3, and ES6+ JavaScript.
File structure
• Top-level:
• README.md, LICENSE (documentation)
• assets/ (images, design prototypes)
• modules/ (all the code and pages)
• Under modules/:
• index.html (entry point)
• style.css + modules/css/*.css (global & component styles)
• modules/js/ (logic split into api.js, data.js, ui.js, details.js)
• main.js (initial bootstrap)
• modules/pages/pokemon.html (detail page template)
README
• Static front-end, no server or database.
• Architecture revolves around modular JS layers: API access, data modeling, UI rendering.
Detailed coverage
• Client-side routing component in main.js
• How modules/pages/pokemon.html is loaded or injected
• Assets folder as a supporting repository for images and CSS
• User interactions (click → navigation → fetch → render)