-
-
Notifications
You must be signed in to change notification settings - Fork 121
[FEATURE] <Better sign up flow> #51
Comments
I would like to take this one on aswell. Little Idea: Maybe make a section with all the current pages in the README with all their corresponding .tsx files, aslong as we don't have a navbar? |
Sounds good! Having a navbar (or any other way of navigation) might be a good solution, also. |
I think we should use a package called 'nodemailer', for confirming the mail of users. What do you think? |
We're using Supabase right now, but that could definitely be an option maybe with NextAuth. What would be the pros and cons of that approach? |
As of I didn't worked much with supabase. But if I talk about nodemailer, then I think it's a great library to send emails with ease. Where you can send emails with just some lines of code like 15 - 20 and its fast as well. The fall back is you can only authenticate the user by email. If you want to add other authentication options like google, GitHub then you have to add them by another method. |
@ykdojo I'd like to give this a try if it hasn't been assigned to anyone yet |
I'm not sure what you mean by the main app dashboard by supabase here? |
Supabase allows us to define the url a user gets redirected to on email confirmation. We can use that to redirect the user back to the part a user sees after signing in. for now it can just redirect to the |
You meant index (/), right? |
yea |
FYI, for the navbar, I created this separate issue. I think I'm going to work on that one next. |
Description
When a user signs up at /signup, confirming the email is required. I think we should make that clear.
Also, we should probably add some info about how to find the signup page (/signup) and the signin page (/signin) either on the site itself or in README.
The text was updated successfully, but these errors were encountered: