Switching careers

Learn to code by building a ward shift board

The idea

A shift board for our ward where a nurse posts a shift they cannot work and another nurse picks it up

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

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

Ward Shift Board

A simple shift board where ward nurses can post shifts they cannot work and other nurses can offer to cover 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

  • Post a shiftEnter the shift date, start and finish times, ward area, and a short note.
  • View the shift boardShow open shifts as a clear list with the date, time, area, and note.
  • Offer to cover a shiftSelect an open shift and add your name to show that you can cover it.
  • Update or remove a shiftChange an open shift to covered or delete a shift that was posted by mistake.
  • Save and filter shiftsKeep shifts after closing the page and filter the board by date or ward area.

Later in your path

  • Sync the board with a serverSave the shift board on a Node and Express server so nurses using different devices can see the same shifts.With a server
  • Add private nurse accountsLet nurses sign in and use MongoDB so each person only sees and manages shifts posted under their account.With a database and accounts

What it leaves out, and why

  • Manager approval and swap requestsThese rules need clear hospital policies and manager accounts, so they should wait until the basic board works.
  • Text and email alertsNotifications need server jobs and provider accounts, which would make the first version too large.
  • Automatic repeating shiftsRecurring schedules and exception dates add complexity before nurses can manage a simple one-off shift.
  • Staff rota and payroll integrationHospital systems use special rules and private formats that are outside a small first project.
  • Role-based permissionsThe first version can focus on one shared board before deciding what nurses, managers, and administrators may do.

Your path

29 steps, about 45 hours

In the browser 9 steps · about 18 hours
  1. 1 Open your first shift board 1
  2. 2 Build the shift board page 1
  3. 3 Make the board easy to use 1
  4. 4 Remember shift details 1
  5. 5 Check shift dates and times 1
  6. 6 Post a shift from the page 1
  7. 7 Show every posted shift 1
  8. 8 Save and manage shifts 1
  9. 9 Explain your shift board 1
With a server 14 steps · about 17 hours
  1. 10 Prepare the shift board workbench 2
  2. 11 Get the shift board code ready to connect 2
  3. 12 Call the shift board API from the page 2
  4. 13 Start the shift board server 2
  5. 14 Keep server settings and errors visible 2
  6. 15 Open the shift board from the server 2
  7. 16 Define the shift board API 2
  8. 17 Show shifts saved by the server 2
  9. 18 Post and manage shifts on the server 2
  10. 19 Keep the page and server in sync 2
  11. 20 See what a server restart removes 2
  12. 21 Keep shifts in a JSON file 2
  13. 22 Protect the shift board from bad shifts 2
  14. 23 Prepare the shift board for feedback 2
Database and accounts 6 steps · about 10 hours
  1. 24 Show shifts saved in MongoDB 3
  2. 25 Manage shifts in the database 3
  3. 26 Create a private nurse account 3
  4. 27 Sign in and protect the shift board 3
  5. 28 Keep each nurse's shifts private 3
  6. 29 Run and present the complete shift board 3
Your app's map Ward Shift Board
fetch /api/...

In the browser

Your server

Where data lives

What you will have proved

64 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. Variables and values after Editor, preview, save
  10. Finding elements on the page after Variables and values, HTML document and basic tags
  11. Strings, numbers, booleans after Variables and values
  12. Decisions with if/else after Strings, numbers, booleans
  13. Working with dates and times 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. Write a README after What a repo and a commit are
  28. 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. Relating documents after CRUD with MongoDB, Login and protected routes
  8. Users only see their own data after Login and protected routes, Relating documents
  9. Run it like production after CRUD with MongoDB, Configuration and secrets, Git in your workbench, What a host needs from your server
  10. Frontend and backend together after Run it like production, Move your app from localStorage to the API
  11. Portfolio and project story after Frontend and backend together, Write a README
  12. 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 · Open your first shift board

The editor contains an index.html file.

1Step 2 · Build the shift board page

The page has a main section for the shift board.

1Step 3 · Make the board easy to use

The shift board sits inside a clear main section.

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 45 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.

Plant watering reminder Both teach Editor, preview, save, Working with dates and times, Reading errors and using the consolePet health record Both teach Editor, preview, save, Working with dates and times, Reading errors and using the consoleTailoring order book Both teach Editor, preview, save, Working with dates and times, Reading errors and using the console

See all twenty ideas