Switching careers
Learn to code by building a classroom quiz maker
A quiz maker where I write multiple-choice questions for my class, students take the quiz, and see their score
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 · 8 hours a week · HTML, CSS and JavaScript, then Node and Express
Your first version
Classroom Quiz Maker
A quiz maker for maths teachers who want to create multiple-choice quizzes and let students take them.
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
- Create maths questionsEnter a question, choose answer choices, and mark the correct answer.
- Build and edit a quizCombine questions into a quiz, edit them, and remove questions you do not want.
- Take a quiz as a studentShow one question at a time and let the student choose an answer before submitting the quiz.
- See the scoreCalculate the number of correct answers and show the student a score out of the total.
- Save quizzes and review resultsKeep the quiz list in the browser and let the teacher review the latest results.
- Make it easy to useCreate a clear layout with buttons, spacing, error messages, and a design that works on phones.
Later in your path
- Sync quizzes and results with a serverStore quizzes and student results on a server so the teacher and students can use the same copy.With a server
- Protect each teacher's classroom dataAdd teacher and student accounts so each user can securely access only their own quizzes and results.With a database and accounts
What it leaves out, and why
- Student names, classes, and multiple teachersThey add account and class management before the first working quiz is finished.
- Explanations and worked solutions after each answerThey are useful, but the first version should focus on answering and scoring.
- Timed quizzes and question limitsTiming rules and attempt limits need extra state and careful testing.
- Question images and file uploadsFile uploads add a separate storage system to the beginner version.
- Teacher-created quizzes with automated feedback reportsA full reporting system can come after the quiz-taking flow works.
Your path
29 steps, about 47 hours
- 1 Show the first Classroom Quiz Maker page 1
- 2 Add a question form 1
- 3 Make the question form easy to use 1
- 4 Arrange the teacher and student areas 1
- 5 Read and check a new question 1
- 6 Show the question bank 1
- 7 Save and manage questions 1
- 8 Finish and explain your project 1
- 9 Plan for a quiz server 2
- 10 Set up your workbench 2
- 11 Prepare the browser for server data 2
- 12 Run your first server 2
- 13 Open the quiz page from your server 2
- 14 Define the quiz API 2
- 15 Keep quizzes in memory 2
- 16 Change and remove quizzes 2
- 17 Use server data in the quiz page 2
- 18 See what a restart clears 2
- 19 Keep quizzes in a JSON file 2
- 20 Protect the quiz server 2
- 21 Prepare your server to run 2
- 22 Improve the quiz maker 2
- 23 Keep quizzes in MongoDB 3
- 24 Manage saved quizzes and results 3
- 25 Let teachers create an account 3
- 26 Sign teachers in safely 3
- 27 Connect each result to its quiz 3
- 28 Keep each teacher's classroom private 3
- 29 Run and present the finished quiz maker 3
In the browser
Your server
Where data lives
What you will have proved
68 concepts
Every concept is one the path teaches, in the order it teaches them, after the ones it needs first.
- 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
- Hover, focus, disabled and error states after CSS selectors, colors, text, Forms and inputs
- Layout with Flexbox after Box model and spacing
- Responsive basics after Layout with Flexbox
- 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
- 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
- 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
- Security basics after Login and protected routes
- 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.
index.html contains a title for Classroom Quiz Maker.
index.html uses headings and sections to organise the page.
The form fields and submit button have visible text and background colours.
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 29 steps, about 47 hours: at 8 hours a week, about 6 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.