How isiahchoi2/group-work works
This is a web-based print-ordering service. Customers configure print jobs, choose a payment method, review and submit requests, then check order status; staff can log in to manage orders. The React app contains these workflows, while the Express server handles order APIs, uploads, and authentication, persisting orders in MongoDB. The excerpts show the frontend’s API calls and backend persistence, but omit some request-submission code and most admin UI, so those details are not expanded.
Main entry points: server.js Order API · App.jsx Admin tools · main.jsx React entry · Order.js Order model
Components 13
Customer and staff app
- React entry
client/src/main.jsx - Print request
client/src/App.jsx - Payment and review
client/src/App.jsx - Order status
client/src/App.jsx - Admin tools
client/src/App.jsx
Order service
- Order API
server/server.js - Admin authentication
server/server.js
Persistence and files
- Order model
server/Order.js - MongoDB
- Uploaded files
server/server.js - QR payment assets
client/public
Other components
- Customer
- Shop staff
Connections 12
- React entry → Print request: renders
client/src/main.jsx - Customer → Print request: configures
- Print request → Payment and review: continues to
client/src/App.jsx - Customer → Order status: checks
- Shop staff → Admin tools: manages
- Order status → Order API: fetches orders
client/src/App.jsx - Admin tools → Order API: updates orders
client/src/App.jsx - Admin tools → Admin authentication: requests login
client/src/App.jsx - Payment and review → QR payment assets: displays QR
client/src/App.jsx - Order API → MongoDB: reads and writes
server/server.js - Order API → Uploaded files: stores uploads
server/server.js - Order model → MongoDB