chore: Backend for onboarding. Takes the user's email and set's their section, year, and campus.

[PixelHalide]

When the user signs up, A document will be created in the userData collection with the email as the primary key.

When the user completes onboarding, it finds their document via their email and updates it to store their data.

[PranavU-Coder]

try implementing redis api , can't have user rewrite their mail address again in on-boarding form

also we need the the data of the user from the db since cookies or local storage isn't permanent.

and just a simple boolean value is needed from the db if the user is on-boarded or not

[FirezTheGreat]

@PranavU-Coder @PixelHalide

After researching this a bit more, I think Redis would be overkill. This can be handled easily using JWT, Zustand, and a one-time fetch from the backend API.

We can create a user variable in the Zustand store to hold essential user details such as their avatar, name, email, and onboarding status. Then, we define a method in the store called refreshUser() that fetches user details from the /api/auth/me route and stores them in the user variable — but only when we explicitly call it.

We'll call refreshUser() once in App.jsx when the website initially renders. If the user’s details change later (e.g., after onboarding), we can call it again to refresh and cache the updated data in Zustand memory.

Does that sound good?

[FirezTheGreat]

can we use mongoose instead of mongodb, also where's the User Schema? we need to create that first before any further development @PixelHalide @PranavU-Coder

[FirezTheGreat]

Also, please use this file structure instead of writing everything in index.js for efficiency and readability @PixelHalide . Eg -

[FirezTheGreat]

Let me know, @PixelHalide, whether we'll go ahead with mongoose or MongoDB, and if there are any updates on the User Schema and file structure.