Uncodemy Ghaziabad Campus MERN Stack Course Details

// Project 2: full-stack task manager (weeks 8–9)
// This is the structure students build at the Ghaziabad campus

// ─── backend/server.js ───────────────────────────────────────
const express = require("express");
const mongoose = require("mongoose");
const app = express();

app.use(express.json());

mongoose.connect(process.env.MONGO_URI);

app.use("/api/auth", require("./routes/auth"));
app.use("/api/tasks", require("./routes/tasks"));

app.listen(5000, () => console.log("Server running on port 5000"));

// ─── backend/routes/tasks.js ─────────────────────────────────
const router = require("express").Router();
const Task = require("../models/Task");
const { requireAuth } = require("../middleware/auth");

router.get("/", requireAuth, async (req, res) => {
  const tasks = await Task.find({ userId: req.user.id }).sort({ createdAt: -1 });
  res.json(tasks);
});

router.post("/", requireAuth, async (req, res) => {
  const { title, dueDate } = req.body;
  if (!title) return res.status(400).json({ error: "Title required" });

  const task = await Task.create({
    userId: req.user.id,
    title,
    dueDate,
  });
  res.status(201).json(task);
});

module.exports = router;

// ─── frontend/src/pages/Dashboard.jsx ────────────────────────
import { useEffect, useState } from "react";
import axios from "axios";

export default function Dashboard() {
  const [tasks, setTasks] = useState([]);

  useEffect(() => {
    const token = localStorage.getItem("token");
    axios.get(`${import.meta.env.VITE_API_URL}/api/tasks`, {
      headers: { Authorization: `Bearer ${token}` },
    }).then(res => setTasks(res.data));
  }, []);

  return (
    

      
My Tasks
      {tasks.map(t => (
        

          
{t.title}
          
Due: {t.dueDate || "Not set"}
        
      ))}
    
  );
}

// Skills demonstrated: Express + MongoDB + React + JWT + API integration.
// This is what Ghaziabad students present after week 9.

# Capstone project structure (weeks 13–14)
# Students choose from 3 project types — here's the expected deliverable

# ─── APPROVED CAPSTONE TYPES ────────────────────────────────
#
# 1. E-COMMERCE MINI-STORE
#    - Auth (JWT) + roles (customer, admin)
#    - Product catalog + search
#    - Cart + checkout (mock payment)
#    - Order history
#    - Tech: MERN + Stripe/Razorpay test mode + image upload (Cloudinary)
#
# 2. REAL-TIME CHAT APP
#    - Auth + user profiles
#    - Multiple chat rooms
#    - Real-time messaging (Socket.io)
#    - Message history (MongoDB)
#    - Tech: MERN + Socket.io + Redis for presence
#
# 3. JOB BOARD / FREELANCE MARKETPLACE
#    - Job posting (recruiter) + application (candidate)
#    - Search + filter
#    - Application tracking
#    - Tech: MERN + file upload + email notifications (Nodemailer)

# ─── REQUIRED DELIVERABLES ───────────────────────────────────
# 1. GitHub repo with:
#    - Clear README (project description, setup, screenshots)
#    - Well-organised folder structure
#    - Meaningful commit messages
#    - .env.example (not .env)
# 2. Live deployment:
#    - Frontend on Vercel (or Netlify)
#    - Backend on Render (or Railway)
#    - Database on MongoDB Atlas
# 3. 3-minute Loom walkthrough:
#    - Architecture overview
#    - Key features demo
#    - Trade-offs and decisions
# 4. 1-page architecture doc:
#    - System diagram (frontend ↔ API ↔ DB)
#    - Why these tools were chosen
#    - What you'd add with more time

# This is what gets reviewed by the trainer in week 14 (demo day) —
# and what hiring managers actually look at when shortlisting candidates.

# A deployed capstone is worth more than any certificate.