Endpoint: /api/workouts/plans/create
Description: Create a new workout plan.

Endpoint: /api/programs/{programID}
Description: Retrieve details of a specific workout plan.

Modify routes to go from
http://localhost:3000/api

to

${apiUrl}/workouts/all

or whatever for respective endpoint

Endpoint: /api/workouts/{workoutId}/exercises/{exerciseId}
Description: Retrieve details of a specific exercise within a workout.

Endpoint: /api/workouts/{userId}/records/update
Description: Update personal records for a specific user.

Endpoint: /api/workouts/community/plans
Description: Retrieve a list of top community workout plans.

Possible implementation:

• Gather all workout plans
• Order by rating
• return top 10(?)

Endpoint: /api/workouts/user/{userId}/plans
Description: Retrieve a list of workout plans associated with a specific user.

Important steps:

1. Update Database Schema to add users
2. Create association between users and their workout plans
3. Create API Endpoint
4. Add auth/users to app
5. Modify workout plan rendering to use new endpoint

Endpoint: /api/workouts/user/{userId}/history
Description: Retrieve historical workout data for a specific user. Similar to myfitnesspal food diary but with workouts.

Workouts

|--My Routines
|--|--Button to create new routine
|--|--List of Routines
|--Past Workouts
|--|--Diary of Past workouts

API Endpoints needed:
GET - all workout routines associated with user - Need to implement users first
GET - details of each exercise associated with routine

POST - create new workout routine
POST - create set of program exercises associated with new workout routine

Currently, the modal is following a workflow of
Make plan details -> Add exercises to each day of the program -> Program created

Users should be given the option to decide whether they want to manually add each exercise and workout like so or if they want to add some of their already existing workouts to the program so it then becomes a "collection" of their workouts