Starting from zero
Learn to code by building a workout log
The idea
A gym log where I write down each workout's exercises, sets and weights, and see my best lift for each exercise
This is the path the studio planned from the idea above. Yours is planned from your own words and from what you already know, so its steps will be your own.
Planned for: Complete beginner, never programmed · 10 hours a week · HTML, CSS and JavaScript, then Node and Express
Your first version
Lift Log
A simple workout log for recording exercises, sets, weights, and personal bests.
What the studio would build first, and what it sets aside, read from the idea the way your own project's would be.
What it keeps
- Log workoutsCreate a workout and record its name, date, and exercises.
- Record sets and weightsAdd every set for an exercise with its weight and number of reps.
- View workout historySee saved workouts and expand one workout to review its exercises and sets.
- Edit and delete log dataCorrect mistakes or remove exercises, sets, and workouts you no longer want.
- Show personal bestsSee the heaviest successful weight recorded for each exercise.
- Keep data in the browserSave the workout log in localStorage so it remains after closing or refreshing the page.
Later in your path
- Sync workouts with a serverMove saved workouts to a Node and Express server so the app can load the same data in another browser.With a server
- Use a private accountSign in and store each person's workouts in MongoDB so users only see their own data.With a database and accounts
What it leaves out, and why
- Timer between setsA rest timer is useful, but it adds extra timing behavior before the core log and personal-best features are solid.
- Exercise library and muscle groupsA built-in exercise list would need many seed records and extra management features.
- Progress chartsCharts are not needed for a first version, and personal bests already provide a useful summary.
- Body measurements and progress photosThese add file uploads and storage complexity that would distract from the beginner workflow.
- Friends, comments, and sharingSocial features are outside the goal of making a focused workout log and are much larger than the core app.
Your path
32 steps, about 46 hours
In the browser 7 steps · about 19 hours
- 1 Build the Lift Log form 1
- 2 Make the Lift Log page easy to read 1
- 3 Show a workout name on the page 1
- 4 Respond when you use the page 1
- 5 Read workout details from the form 1
- 6 Save and view workout history 1
- 7 Edit, delete, and explain your Lift Log 1
With a server 15 steps · about 17 hours
- 8 See why Lift Log needs a server 2
- 9 Prepare your Lift Log workbench 2
- 10 Add code to Lift Log's page 2
- 11 Add code to Lift Log's page, part 2 2
- 12 Make the Lift Log page use browser requests 2
- 13 Serve the Lift Log page from the server 2
- 14 Write the workout API contract 2
- 15 Save workouts in server memory 2
- 16 Manage workouts with a full API 2
- 17 Make the workout list use the server 2
- 18 Watch a restart clear server workouts 2
- 19 Keep workouts after a server restart 2
- 20 Protect the workout log from bad entries 2
- 21 Make the Lift Log server host-ready 2
- 22 Improve the workout entry flow 2
Database and accounts 10 steps · about 10 hours
- 23 Explain why Lift Log needs a real database 3
- 24 Keep workouts in MongoDB 3
- 25 Manage MongoDB workouts with full CRUD 3
- 26 Create a Lift Log account 3
- 27 Log in and keep an active session 3
- 28 Link workouts to accounts 3
- 29 Keep every member's workouts private 3
- 30 Run the Lift Log backend like production 3
- 31 Connect accounts and workouts end to end 3
- 32 Tell the story of your Lift Log project 3
Your app's map Lift Log
fetch
In the browser
Your server
Where data lives
What you will have proved
65 concepts
Every concept is one the path teaches, in the order it teaches them, after the ones it needs first.
In the browser
- Editor, preview, save
- Slice your idea into a first version
- HTML document and basic tags after Editor, preview, save
- Lists, sections and semantic tags after HTML document and basic tags
- Forms and inputs after HTML document and basic tags
- CSS selectors, colors, text after HTML document and basic tags
- Box model and spacing after CSS selectors, colors, text
- Layout with Flexbox after Box model and spacing
- Variables and values after Editor, preview, save
- Finding elements on the page after Variables and values, HTML document and basic tags
- Strings, numbers, booleans after Variables and values
- Decisions with if/else after Strings, numbers, booleans
- Functions after Decisions with if/else
- Reading errors and using the console after Functions
- Handling what can go wrong after Functions, Reading errors and using the console
- Responding to clicks and input after Finding elements on the page, Functions
- Reading and validating form input after Responding to clicks and input, Forms and inputs
- Arrays after Functions
- Loops after Arrays
- Objects after Arrays
- JSON after Objects
- Totals, sorting and grouping after Arrays, Objects
- Rendering a list from data after Objects, Finding elements on the page, Lists, sections and semantic tags
- Single source of truth after Rendering a list from data, Reading and validating form input
- Saving in the browser with localStorage after JSON, Single source of truth, Handling what can go wrong
- Create, read, update, delete after Saving in the browser with localStorage, Reading errors and using the console
- What a repo and a commit are after Editor, preview, save
- Write a README after What a repo and a commit are
- Explain your project out loud after Create, read, update, delete
With a server
- Why your app needs a server after Saving in the browser with localStorage, Create, read, update, delete
- Meet your workbench after What a repo and a commit are, Create, read, update, delete, Why your app needs a server
- Terminal basics after Meet your workbench
- npm and package.json after Terminal basics
- Splitting code into modules after npm and package.json, Create, read, update, delete, Why your app needs a server
- Asynchronous code after Functions, Reading errors and using the console, Why your app needs a server
- Git in your workbench after What a repo and a commit are, Terminal basics
- How HTTP works after JSON, Why your app needs a server
- Calling an API from the browser after Asynchronous code, How HTTP works
- What a REST API is after How HTTP works
- Node: JavaScript outside the browser after npm and package.json, Splitting code into modules
- Your first Express server after Node: JavaScript outside the browser, How HTTP works
- Configuration and secrets after Your first Express server, Git in your workbench
- Middleware, static files, errors after Your first Express server
- Serve the page you built, untouched after Middleware, static files, errors
- Write your API's contract and try it after What a REST API is, Your first Express server, Serve the page you built, untouched
- Keep data in memory and answer from it after Write your API's contract and try it, Middleware, static files, errors
- CRUD API for your resource after Middleware, static files, errors, Keep data in memory and answer from it, What a REST API is
- Move your app from localStorage to the API after CRUD API for your resource, Calling an API from the browser
- Keep data in memory and watch a restart wipe it after Move your app from localStorage to the API
- Reading and writing a JSON file after Node: JavaScript outside the browser, Asynchronous code, Handling what can go wrong, Keep data in memory and watch a restart wipe it
- Validate on the server after CRUD API for your resource, Reading and writing a JSON file
- What a host needs from your server after Move your app from localStorage to the API, Configuration and secrets, Validate on the server
- Ship, get feedback, adjust after Slice your idea into a first version, What a host needs from your server
Database and accounts
- Why a JSON file is not enough after CRUD API for your resource, Reading and writing a JSON file
- MongoDB: your first real database after Why a JSON file is not enough, Configuration and secrets
- Schemas and models with Mongoose after MongoDB: your first real database
- CRUD with MongoDB after Schemas and models with Mongoose, Validate on the server
- Signup with hashed passwords after Schemas and models with Mongoose
- Login and protected routes after Signup with hashed passwords, Middleware, static files, errors
- Relating documents after CRUD with MongoDB, Login and protected routes
- Users only see their own data after Login and protected routes, Relating documents
- Run it like production after CRUD with MongoDB, Configuration and secrets, Git in your workbench, What a host needs from your server
- Frontend and backend together after Run it like production, Move your app from localStorage to the API
- Portfolio and project story after Frontend and backend together, Write a README
- Interview on your full-stack project after Explain your project out loud, Users only see their own data, Frontend and backend together
What the checker will ask of you
Each step is checked when you press Check: in a real browser, or by starting your server and making requests. These are the first checks on this path.
1Step 1 · Build the Lift Log form
The preview shows a page with a Lift Log heading and a workout form.
1Step 2 · Make the Lift Log page easy to read
The form sits inside a visible card with a background color and a border.
1Step 3 · Show a workout name on the page
The preview shows a JavaScript-generated Lift Log message in the page.
What people ask
What does it cost to build this?
Your first build is on us: one project, the phase in the browser, with the AI to build it. To start it, your bank puts a ₹1 hold on a card; it is released and never charged. Studio access is ₹6,999 once and opens every phase for 6 projects; nothing renews.
What do I need?
A browser and a card for the ₹1 hold. Nothing to install: the browser steps run in a live preview, and the server steps run in a private workspace of your own, with a terminal and git and your own MongoDB.
How long does it take?
This path is 32 steps, about 46 hours: at 10 hours a week, about 5 weeks. Your own path is planned from your idea and sized to what you already know.
Do I keep the code?
Yes. Every step you pass is kept, and you can download the whole project as a git repository with one commit for each step, or publish it to your own GitHub. The code is yours.