IPE-24 Classroom
The first real product I built: a class operating system designed to become the daily source of truth for IPE-24 students.
Product context
IPE-24 Classroom is the first product I built, starting in June 2025 for my university batch. The problem was not the absence of another website; it was fragmented coordination across chat threads, drive links, schedules, notices, and repeated questions.
What I built
The system centralizes class information, resources, routine changes, and student-facing workflows. It also connects selected publishing and notification paths so an operator can update the source of truth without repeating the same work across every channel.
Engineering decisions
- Next.js and TypeScript provide the application and typed product logic.
- PostgreSQL and Prisma model relationships such as courses, schedules, announcements, and submissions.
- Redis supports caching and rate-limiting needs.
- Telegram automation extends the publishing workflow beyond the web UI.
- FastAPI supports selected AI or automation workflows.
Evidence and limits
The product is used by 60+ students as a shared academic source of truth. The strongest evidence is the ownership loop: I found the workflow, built the first usable system, deployed it, supported real usage, and kept refining it.
This is a focused academic product for one community, not evidence that I have built a general-purpose LMS at institutional scale. The case study is intentionally about the workflow and decisions rather than inflated platform claims.