CodeQuest

UKM Coding at Cyber University runs learning programs for members across widely differing skill levels: some have never written code before, while others already ship side projects. Study material lived in scattered documents, submissions arrived over chat, and progress existed only in informal memory.

The community needed a single platform where a member could see what to learn next, submit code, and track verified milestones.

The obvious version of this product is a course website. That would have failed for the same reason the documents failed: nothing made members return.

The real bottleneck was retention and visibility: members dropping off after week two, and mentors having no way to identify who was stuck without polling everyone individually.

• Modelled progress before designing screens. Courses, modules, submissions, and attempts became first-class tables in Prisma. Every interface followed the underlying schema, avoiding database migrations later.
• Role-based access from day one. Member, mentor, and admin roles were structured directly into the auth layer through NextAuth rather than added as an afterthought.
• Made progress visible, not just stored. Completion state surfaces on every entry point, so returning members pick up where they stopped without searching.
• Server components by default. Course and module pages render on the server so initial load stays fast on campus networks. Client interactivity is scoped strictly to interactive editors.

CodeQuest is in production and serves as the primary system for the community's learning tracks. Material, submissions, and progress tracking now operate in one place, allowing mentors to unblock students promptly.

The initial database schema has handled all feature additions without requiring breaking rewrites.

The platform manages programming milestones across multiple tracks for UKM Coding at Cyber University.