How duck3mk/workout-mern works
Workout-MERN is a workout-tracking application with account signup/login and authenticated workout management. The frontend restores and shares auth state, routes signed-in users to the workout home, and provides workout UI; the backend exposes user and workout routes, applies JWT auth to workout routes, and persists users and workouts. The README gives no product details, and the excerpts do not show frontend-to-backend requests, so that connection is intentionally omitted.
Main entry points: useAuthContext.jsx Auth Hook · App.jsx App Routing · Home.jsx Workout Home · useContext.jsx Workout Hook
Components 23
Frontend
- App Routing
frontend/src/App.jsx - Navigation
frontend/src/components/Navbar.jsx - Workout Home
frontend/src/pages/Home.jsx - Signup Page
frontend/src/pages/SignUp.jsx - Login Page
frontend/src/pages/login.jsx - Workout Form
frontend/src/components/createWorkoutForm.jsx - Workout Details
frontend/src/components/workoutDetails.jsx
Identity
- Auth State
frontend/src/context/AuthContext.jsx - Auth Hook
frontend/src/hooks/useAuthContext.jsx - Login Action
frontend/src/hooks/useLogin.jsx - Signup Action
frontend/src/hooks/useSignup.jsx - Logout Action
frontend/src/hooks/useLogout.jsx
Workout Management
- Workout State
frontend/src/context/workoutContext.jsx - Workout Hook
frontend/src/hooks/useContext.jsx
Backend Runtime
- API Server
backend/server.js - User Routes
backend/routes/userRoutes.js - Workout Routes
backend/routes/workoutRoutes.js - Account Controller
backend/controllers/userController.js - Workout Controller
backend/controllers/workoutController.js - JWT Middleware
backend/middlewere/requiredAuth.js - User Model
backend/models/userSchema.js - Workout Model
backend/models/workoutSchema.js
Other components
- User
Connections 32
- User → App Routing: uses app
- App Routing → Navigation: renders
frontend/src/App.jsx - App Routing → Workout Home: routes to
frontend/src/App.jsx - App Routing → Signup Page: routes to
frontend/src/App.jsx - App Routing → Login Page: routes to
frontend/src/App.jsx - App Routing → Auth Hook: reads auth
frontend/src/App.jsx - Navigation → Logout Action: uses
frontend/src/components/Navbar.jsx - Navigation → Auth Hook: reads auth
frontend/src/components/Navbar.jsx - Workout Home → Workout Form: renders
frontend/src/pages/Home.jsx - Workout Home → Workout Details: renders
frontend/src/pages/Home.jsx - Workout Home → Workout Hook: reads workouts
frontend/src/pages/Home.jsx - Workout Home → Auth Hook: reads auth
frontend/src/pages/Home.jsx - Signup Page → Signup Action: uses
frontend/src/pages/SignUp.jsx - Login Page → Login Action: uses
frontend/src/pages/login.jsx - Workout Form → Workout Hook: uses
frontend/src/components/createWorkoutForm.jsx - Workout Form → Auth Hook: uses
frontend/src/components/createWorkoutForm.jsx - Workout Details → Workout Hook: uses
frontend/src/components/workoutDetails.jsx - Workout Details → Auth Hook: uses
frontend/src/components/workoutDetails.jsx - Auth Hook → Auth State: reads context
frontend/src/hooks/useAuthContext.jsx - Login Action → Auth Hook: uses
frontend/src/hooks/useLogin.jsx - Signup Action → Auth Hook: uses
frontend/src/hooks/useSignup.jsx - Logout Action → Auth Hook: uses
frontend/src/hooks/useLogout.jsx - Logout Action → Workout Hook: uses
frontend/src/hooks/useLogout.jsx - Workout Hook → Workout State: reads context
frontend/src/hooks/useContext.jsx - API Server → User Routes: mounts
backend/server.js - API Server → Workout Routes: mounts
backend/server.js - User Routes → Account Controller: routes to
backend/routes/userRoutes.js - Workout Routes → Workout Controller: routes to
backend/routes/workoutRoutes.js - Workout Routes → JWT Middleware: requires auth
backend/routes/workoutRoutes.js - Account Controller → User Model: calls
backend/controllers/userController.js - Workout Controller → Workout Model: queries
backend/controllers/workoutController.js - JWT Middleware → User Model: looks up user
backend/middlewere/requiredAuth.js