Preliminaries

<aside> 📖

Overview

Welcome to the VibeFlow Hackathon! In this challenge, your team members will build EduVibe, an AI-powered EdTech platform connecting students with mentors for personalized learning.

Your goal is to leverage AI to develop core features, address real-world challenges, and evaluate AI’s effectiveness in managing time, planning, brainstorming, performance, and performing front-end state management.

This case study revolves around two personas Maya (student), and Dr. Patel (mentor), to guide your development.

</aside>

EduVibe must include:

• A multi-part form based student onboarding system.
• A mentor recommendation system based on student goals.
• An interactive Mentor Session booking system.
• A student dashboard for viewing all booked sessions.
• A mentor dashboard for session management.

Important Notes:

1. Please go through the entire case study before starting the implementation to get a better idea of all the requirements mentioned. Solving each task sequentially is not mandatory, but would be beneficial at later stages where multiple complex logic is present.
2. As there are two user groups, it’s advisable to create a dedicated Register page which contains the options to “Login/Register as Student” or “Login/Register as Mentor”. Depending on the role selected, the appropriate user flow could continue.
3. There should be one button called “Get Started” in the Home page NavBar. Once this button is clicked:
   1. A sign up modal will popup for them to sign in/sign up for the platform
   2. If it’s a first time registering user, then they should be redirected to the intermediate page where they can select either student or mentor signup.
   3. For the student flow, you can have an onboarding form which asks for student related information, while for the mentor flow you can have an onboarding form which asks for mentor related information. (More details discussed in Task 2 & 3)
   4. Once onboarded, the user should be directed to their relevant dashboard based on their role.
   5. If a particular user who has already onboarded once clicks on the “Get Started” button
4. If the login session still exist, they should be redirected to the user relevant dashboard
5. If login session doesn’t exist, make the user login first, and based on the user role detected via auth, redirect them to relevant dashboard

A bit of context, where your focus should be on:

• Deliverables will be judged based on the report quality (50%), development quality (30%), and presentation quality (20%).
• Developing all the features by completing the whole case study is nice to have. But your focus should not only be on completing all the features, but experimenting in development with AI