-
Notifications
You must be signed in to change notification settings - Fork 0
Demo Script
Gage Bays edited this page Oct 17, 2025
·
4 revisions
This walkthrough shows how our Joblist app connects from GitHub repo → running app → backend code → database → and back.
It demonstrates how the frontend, API, backend, and database all work together.
- Go to our GitHub repository: show main files (
/client,/server,/models,/routes). - Explain that the project is split into:
-
Frontend (React) inside
/client -
Backend/API (Node.js + Express) inside
/server -
Database models (Mongoose) inside
/server/models
-
Frontend (React) inside
- Open the deployed app or
npm startlocally. - Show the main dashboard with job listings.
- Explain:
- Users can log in or register.
- Once logged in, they can add, edit, or delete job applications.
- Each entry tracks company name, job title, application date, contact info, and status.
- UI shows progress (like applied, interview, offer, etc.).
- Open browser dev tools → Network tab → perform an action (like adding a job).
- Point out the API call being made (
POST /api/jobs). - Explain that the frontend communicates with our backend API using REST routes.
- Show backend code (open
/server/routes/jobs.jsor/controllers/jobsController.js). - Explain route flow:
- Express receives the request (like
POST /api/jobs). - It validates data.
- It uses Mongoose to save or fetch data from MongoDB.
- Express receives the request (like
- Show how errors are handled and responses are returned.
- Show MongoDB Atlas dashboard or local database viewer.
- Open the
jobscollection. - Highlight that each document stores all job details and is linked to a user.
- Go back to the app and refresh.
- The new job should appear in the list immediately (showing successful data round trip).
End with a short summary:
“Joblist brings everything together — a React frontend, Express backend, and MongoDB database — all connected and deployed through GitHub for teamwork and version control.”
- Make demo 10 minutes or more in length.
- Make sure each team member covers one piece (repo, frontend, backend, database).
- Test all actions before presenting.
- Have your database running (MongoDB Atlas or local) before starting.