How adrianhajdin/project_fitness_app works
Project type and purpose
• This is a client-only React Single Page Application (SPA) called “React Fitness Application.”
• Purpose: allow users to browse, search, and view details of fitness exercises and related videos by consuming a third-party exercise API.
File structure
• Top-level:
• public/ – static HTML + manifest + favicon + robots.txt for hosting
• src/ – React application code
• .env, package.json, build/config files
• src breakdown:
• src/index.js + src/App.js – application entrypoint and router setup
• src/components/ – reusable UI bits (Navbar, Loader, ExerciseCard, etc.)
• src/pages/ – top-level screens (Home, ExerciseDetail)
• src/utils/fetchData.js – abstraction over fetch/axios calls to external API
README for additional insights
• README shows a screenshot and marketing links but no internal architecture.
• We know the app fetches exercise data/videos from a remote API (likely via fetchData.js).
Detail without over-splitting
• Folder’s role (assets vs. components vs. pages vs. utils).
• Data flow for search and detail views separately if desired.
• Avoid diving into every small helper; focus on components that manage UI and data fetch.