How rohnroy0/summer_camp_website works
What this project is (type + purpose)
This is a full-stack event website for “Summer School 2026 – IEEE Student Branch” with:
• A public marketing site + registration flow (HTML/CSS/JS)
• Payments via Razorpay
• Automated verification + email notifications (Nodemailer/SMTP)
• An Admin Dashboard for participant management
• A backend service (Node.js + Express) and MongoDB Atlas per README
What the file tree tells you structurally
Top-level files:
• index.html, style.css, script.js: public landing/registration UI and client logic
• admin-dashboard.html, admin-dashboard.css: separate admin UI entry point
• assets/images/...: static assets (logos, speakers, etc.)
• render.yaml: deployment descriptor (strong hint: hosted on Render; could host static site and/or Node service)
This implies a static frontend that calls a backend API.
What the README adds (architecture + integrations)
The README defines core containers and integrations:
• Backend: Node.js + Express.js (REST endpoints)
• DB: MongoDB Atlas
• Payments: Razorpay SDK (server-side order creation, signature verification, webhooks)
• Email: Nodemailer via SMTP
• Admin auth: via ADMIN_EMAIL / ADMIN_PASSWORD env vars (suggests basic credential check; likely session/JWT)
This implies the backend is the orchestrator for:
• participant creation/update
• payment initiation and verification
• sending confirmation emails
• admin login and admin operations
Static Frontend (HTML/CSS/JS)
• Serves: index.html, admin-dashboard.html, CSS/JS/assets
• Runs in: Browser + static hosting (Render static site, or Render web service, etc.)
Backend API (Node.js/Express)
• Runs in: Render Web Service (inferred from render.yaml)
• Responsibilities:
• Registration endpoints
• Payment order creation + verification
• Admin authentication + admin endpoints
• Email sending orchestration
Database (MongoDB Atlas)
• Participants/Registrations
• Payments/Transactions
• Possibly Admin/Audit (or admin is env-based only)
External Services
• Razorpay (Payments)
• SMTP server (Nodemailer transport)
• Browser (Participant) → Backend: “Register”, “Create payment order”, “Verify payment”
• Browser (Admin) → Backend: “Admin login”, “List participants”, “Update status”, etc.
• Backend ↔ MongoDB Atlas: store registration + payment status
• Backend ↔ Razorpay: create order / verify signature; receive webhook callbacks
• Backend → SMTP: send confirmation/receipt/verification email
• API Router Layer (Express routes)
• /api/register
• /api/payment/create-order
• /api/payment/verify (or webhook endpoint)
• /api/admin/login
• /api/admin/participants (list/update)
• Registration Service
• validate inputs
• create participant record
• trigger email flow
• Payment Service (Razorpay SDK integration)
• create order
• verify payment signature
• update payment status in DB
• Webhook Handler
• receive Razorpay events
• reconcile payment state
• Email Service (Nodemailer)
• templates (even if inline)
• send verification/confirmation
• Auth Component
• admin credential check from env
• session/JWT issuance (unknown; mark as “Auth mechanism (TBD)”) if not specified
• Data Access Layer
This component-level view is where you “separate into as many components as possible” without claiming exact module structure.
Flow 3: Razorpay webhook (recommended even if optional)
• Razorpay → Backend /api/payment/webhook
• Backend verifies webhook signature
• Backend updates DB + triggers email if needed
• [ ] Every external dependency is shown: Razorpay, SMTP, MongoDB Atlas
• [ ] Admin is a distinct actor and has a distinct UI page
• [ ] Payment verification and/or webhook path is shown (signature verification boundary)
• [ ] Data store shows what it stores (participants + payment status)
• [ ] Render (or hosting) boundary is explicit if render.yaml is used