Starting from zero

Learn to code by building a recipe box

The idea

A recipe box where I keep my recipes with their ingredients and steps, and find one by an ingredient I have

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

Change anything. Your path is planned from what you write, and from what you already know.

Your first build is on us. When you press Build, we check your card with a ₹1 hold that is never charged.

Your first version

Pantry Recipe Finder

A recipe box where home cooks can save recipes and find recipes using ingredients they already have.

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

  • Add a recipeAdd a recipe with a name, ingredients, preparation time, and step-by-step instructions.
  • Browse saved recipesSee every saved recipe as a clear list and open one to read all its ingredients and steps.
  • Find recipes by ingredientType an ingredient, such as tomato or egg, and see matching recipes with the matching ingredient highlighted.
  • Manage recipesCorrect recipe details or remove recipes you no longer want.
  • Keep recipes after closing the pageSave recipes in the browser so they are still there after a refresh or reopening the app.
  • Use the app on any screenUse the recipe box comfortably on a phone, tablet, or computer with clear buttons and readable spacing.

Later in your path

  • Sync recipes through a serverConnect the app to a Node and Express server so the same saved recipes can load on different browsers and devices.With a server
  • Sign in and keep recipes privateAdd accounts with MongoDB so each signed-in user can only see and manage their own recipes.With a database and accounts

What it leaves out, and why

  • Recipe photosImages and file uploads would make the project much larger before the core recipe and ingredient search work is reliable.
  • Ratings and commentsThese need extra users, extra rules, and more testing, so they should wait until basic accounts and private recipes work.
  • Meal plans and shopping listsA meal plan connects many recipes over several dates and should be a later project after the recipe box works well.

Your path

32 steps, about 46 hours

In the browser 8 steps · about 19 hours
  1. 1 Show the Pantry Recipe Finder 1
  2. 2 Set up the recipe list and form 1
  3. 3 Make the recipe box clear on every screen 1
  4. 4 Show the saved recipe count 1
  5. 5 Check recipe details before accepting them 1
  6. 6 Add recipes and find them by ingredient 1
  7. 7 Manage recipes that stay saved 1
  8. 8 Use every recipe control without a mouse 1
With a server 15 steps · about 17 hours
  1. 9 Show why recipes need a server 2
  2. 10 Set up your workbench 2
  3. 11 Split the recipe code into modules 2
  4. 12 Understand requests and responses 2
  5. 13 Start an Express server 2
  6. 14 Serve your page from the server 2
  7. 15 Write the recipe API contract 2
  8. 16 Answer recipe requests with memory 2
  9. 17 Add recipe actions to the server 2
  10. 18 Sync the recipe box with the server 2
  11. 19 See what a server restart forgets 2
  12. 20 Save recipes in a JSON file 2
  13. 21 Check recipes before saving them 2
  14. 22 Describe what your server needs 2
  15. 23 Improve your recipe box 2
Database and accounts 9 steps · about 11 hours
  1. 24 See where your recipes are stored 3
  2. 25 Connect the recipe box to MongoDB 3
  3. 26 Keep recipes in MongoDB 3
  4. 27 Create your recipe account 3
  5. 28 Sign in to your recipe account 3
  6. 29 Connect recipes to their cook 3
  7. 30 Keep every recipe box private 3
  8. 31 Run the complete recipe box 3
  9. 32 Share the story of your full-stack app 3
Your app's map Pantry Recipe Finder
fetch /api/...

In the browser

Your server

Where data lives

What you will have proved

66 concepts

Every concept is one the path teaches, in the order it teaches them, after the ones it needs first.

In the browser
  1. Editor, preview, save
  2. Slice your idea into a first version
  3. HTML document and basic tags after Editor, preview, save
  4. Lists, sections and semantic tags after HTML document and basic tags
  5. Forms and inputs after HTML document and basic tags
  6. CSS selectors, colors, text after HTML document and basic tags
  7. Box model and spacing after CSS selectors, colors, text
  8. Layout with Flexbox after Box model and spacing
  9. Responsive basics after Layout with Flexbox
  10. Variables and values after Editor, preview, save
  11. Finding elements on the page after Variables and values, HTML document and basic tags
  12. Strings, numbers, booleans after Variables and values
  13. Decisions with if/else after Strings, numbers, booleans
  14. Functions after Decisions with if/else
  15. Reading errors and using the console after Functions
  16. Handling what can go wrong after Functions, Reading errors and using the console
  17. Responding to clicks and input after Finding elements on the page, Functions
  18. Reading and validating form input after Responding to clicks and input, Forms and inputs
  19. Arrays after Functions
  20. Objects after Arrays
  21. JSON after Objects
  22. Rendering a list from data after Objects, Finding elements on the page, Lists, sections and semantic tags
  23. Single source of truth after Rendering a list from data, Reading and validating form input
  24. Saving in the browser with localStorage after JSON, Single source of truth, Handling what can go wrong
  25. Create, read, update, delete after Saving in the browser with localStorage, Reading errors and using the console
  26. What a repo and a commit are after Editor, preview, save
  27. Accessible by default after Forms and inputs, CSS selectors, colors, text
  28. Write a README after What a repo and a commit are
  29. Explain your project out loud after Create, read, update, delete
With a server
  1. Why your app needs a server after Saving in the browser with localStorage, Create, read, update, delete
  2. Meet your workbench after What a repo and a commit are, Create, read, update, delete, Why your app needs a server
  3. Terminal basics after Meet your workbench
  4. npm and package.json after Terminal basics
  5. Splitting code into modules after npm and package.json, Create, read, update, delete, Why your app needs a server
  6. Asynchronous code after Functions, Reading errors and using the console, Why your app needs a server
  7. Git in your workbench after What a repo and a commit are, Terminal basics
  8. How HTTP works after JSON, Why your app needs a server
  9. Calling an API from the browser after Asynchronous code, How HTTP works
  10. What a REST API is after How HTTP works
  11. Node: JavaScript outside the browser after npm and package.json, Splitting code into modules
  12. Your first Express server after Node: JavaScript outside the browser, How HTTP works
  13. Configuration and secrets after Your first Express server, Git in your workbench
  14. Middleware, static files, errors after Your first Express server
  15. Serve the page you built, untouched after Middleware, static files, errors
  16. Write your API's contract and try it after What a REST API is, Your first Express server, Serve the page you built, untouched
  17. Keep data in memory and answer from it after Write your API's contract and try it, Middleware, static files, errors
  18. CRUD API for your resource after Middleware, static files, errors, Keep data in memory and answer from it, What a REST API is
  19. Move your app from localStorage to the API after CRUD API for your resource, Calling an API from the browser
  20. Keep data in memory and watch a restart wipe it after Move your app from localStorage to the API
  21. 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
  22. Validate on the server after CRUD API for your resource, Reading and writing a JSON file
  23. What a host needs from your server after Move your app from localStorage to the API, Configuration and secrets, Validate on the server
  24. Ship, get feedback, adjust after Slice your idea into a first version, What a host needs from your server
Database and accounts
  1. Why a JSON file is not enough after CRUD API for your resource, Reading and writing a JSON file
  2. MongoDB: your first real database after Why a JSON file is not enough, Configuration and secrets
  3. Schemas and models with Mongoose after MongoDB: your first real database
  4. CRUD with MongoDB after Schemas and models with Mongoose, Validate on the server
  5. Signup with hashed passwords after Schemas and models with Mongoose
  6. Login and protected routes after Signup with hashed passwords, Middleware, static files, errors
  7. Security basics after Login and protected routes
  8. Relating documents after CRUD with MongoDB, Login and protected routes
  9. Users only see their own data after Login and protected routes, Relating documents
  10. Run it like production after CRUD with MongoDB, Configuration and secrets, Git in your workbench, What a host needs from your server
  11. Frontend and backend together after Run it like production, Move your app from localStorage to the API
  12. Portfolio and project story after Frontend and backend together, Write a README
  13. 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 · Show the Pantry Recipe Finder

index.html contains a document with a visible Pantry Recipe Finder heading.

1Step 2 · Set up the recipe list and form

The page has a semantic list for saved recipes.

1Step 3 · Make the recipe box clear on every screen

The recipe form and recipes area are spaced apart with visible padding and borders.

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.

Reading list Both teach Accessible by default, Responsive basics, Editor, preview, saveClassroom quiz maker Both teach Responsive basics, Editor, preview, save, Reading errors and using the consoleConstruction site diary Both teach Responsive basics, Editor, preview, save, Reading errors and using the console

See all twenty ideas