This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend
What I Built
I built Campus Care, a transparent, real-time issue-tracking and resolution platform designed to bridge the gap between students and maintenance staff at my University.
The Problem:
On a busy campus, issues like broken projectors, flickering library lights, and plumbing problems can easily go unnoticed or get buried in endless WhatsApp groups. Students often have no way to know whether their complaints have been received or addressed, while maintenance staff lack a centralized system to organize tasks, track progress, and showcase the work they complete.
Campus Care aims to make reporting, tracking, and resolving campus issues simpler, faster, and more transparent for everyone.
Demo
Code
🏫 Campus Care
Report • Resolve • A Better Campus
A transparent, real-time campus issue tracking and resolution platform built for students and maintenance staff
About • Features • Tech Stack • Structure
📌 About the Project
Campus Care is a transparent, real-time issue-tracking platform designed to simplify the way campus maintenance problems are reported, tracked, and resolved.
Built specifically with Parul University's Goa campus in mind, Campus Care bridges the communication gap between students and maintenance staff.
Instead of complaints getting lost in WhatsApp groups or informal conversations, students can report issues such as:
- 💡 Flickering or broken lights
- 📽️ Faulty projectors
- 🚰 Plumbing and water-related issues
- ⚡ Electrical problems
- 🪑 Damaged furniture
- 🏫 Other campus maintenance concerns
Students can track the complete lifecycle of their complaints, while caretakers get a centralized dashboard to manage, prioritize, and resolve issues efficiently.
…Report an issue. Track its progress. See it resolved.
How I Built It
To build a scalable, responsive, and production-ready platform within a single weekend, I leveraged modern web technologies and powerful backend-as-a-service tools.
- Frontend: Built using Next.js (App Router) and React, with dedicated routes such as /pending, /working, /completed, and /admin to provide focused dashboards for each stage of the issue-resolution lifecycle.
- UI & Styling: Used Tailwind CSS to create a clean, responsive interface while Lucide React provided lightweight, scalable icons throughout the platform.
- Backend & Database: Powered by Supabase and PostgreSQL, which handles the core application data and real-time workflow.
- The issues and notifications tables manage issue status, updates, and user notifications.
- Supabase Storage handles image uploads, including photos submitted with student complaints and resolution-proof images uploaded by maintenance staff.
- The Next.js frontend communicates directly with Supabase, while Row Level Security (RLS) policies help ensure that data can only be accessed or modified by authorized users.
- Authentication & Access Control: Integrated Supabase Auth for secure student registration and login. Role-based redirection ensures that maintenance staff can access their protected admin dashboard, while students are directed to the appropriate user interface.
This stack allowed me to move quickly from idea → functional prototype → deployable platform, while keeping the architecture flexible enough to scale as campus usage grows.
Why Does Open Innovation Matter?
Open innovation made it possible to build Campus Care as a solo student developer within a day, using modern, accessible technologies that make powerful development tools available to individuals.
The project is designed to be open and extensible, allowing future developers to build upon it, contribute features such as AI-powered issue triage, or adapt the platform for their own campuses. What starts as a solution for one campus can grow into a resource for institutions everywhere.
Top comments (0)