How nandan-108/resume-submission-portal works
This is a resume-submission portal: an applicant completes a browser form, uploads a PDF, and receives a generated application ID on the success page. The browser validates fields and sends multipart data; the API validates the upload, checks application details, stores the resume and applicant record, and returns the ID. The graph distinguishes browser behavior, HTTP routing, submission handling, and persistence. Source excerpts support the main submission path; page markup and database schema details were not sampled, so their internal wiring is not expanded.
Main entry points: script.js Form behavior · server.js Express server · applicantController.js Application handling · applicantRoutes.js Applicant routes
Components 11
Browser experience
- Application form
views/index.html - Form behavior
public/js/script.js - Success page
views/success.html
HTTP server
- Express server
server.js - Applicant routes
routes/applicantRoutes.js
Submission handling
- PDF upload
middleware/upload.js - Application handling
controllers/applicantController.js
Persistence
- Resume files
uploads/.gitkeep - MySQL pool
config/db.js - MySQL database
Other components
- Applicant
Connections 15
- Applicant → Application form: fills form
- Application form → Form behavior: loads behavior
- Form behavior → Express server: requests pages
- Express server → Application form: serves form
- Express server → Success page: serves success
- Form behavior → Applicant routes: posts multipart
- Express server → Applicant routes: mounts API
- Applicant routes → PDF upload: accepts PDF
- PDF upload → Resume files: writes resume
- Applicant routes → Application handling: dispatches submission
- Application handling → Resume files: removes invalid upload
- Application handling → MySQL pool: executes queries
- MySQL pool → MySQL database: connects
- Application handling → Form behavior: returns application ID
- Form behavior → Success page: redirects with ID