How iamdef/marvel-react-app works
Project type and purpose
• This is a small full-stack web application: a React single‐page application for browsing Marvel characters/comics, backed by a simple PHP proxy that hides your Marvel API keys.
File structure
• Top level:
• public/index.html → the SPA host page
• src/index.js → React entry point
• src/components → all UI components (App, pages, lists, banners, headers, etc.)
• src/hooks → custom hooks (http.hook.js for fetch logic)
• src/services →
– MarvelService.js (client‐side calls directly to Marvel API)
– MarvelServerService.js (calls your local PHP proxy)
• src/backend/marvel-access.php → simple PHP script forwarding requests to Marvel API
• src/utils, src/style, src/resources → supporting modules, styles, assets
• No database or other microservices—just front end + PHP proxy + external Marvel API.
README
• Confirms: “Marvel React app—training project on React using Marvel API.”
Essential details to capture
• Where API keys live (in PHP proxy).
• Environments (development vs. production) if needed—for example, local webpack dev server vs. deployed PHP host.