-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion to Add Authentication Using Clerk.js #52
Labels
Comments
👋 Thank you for raising an issue! We appreciate your effort in helping us improve. Our team will review it shortly. Stay tuned! |
go ahead with this @PrayanshParmar |
jahnvisahni31
added
good first issue
Good for newcomers
gssoc-ext
hacktoberfest-accepted
level1
hacktoberfest
labels
Oct 7, 2024
@jahnvisahni31 Please marked it level 3, Adding auth is a hard task, also did you want a third party auth like google or github. |
This was referenced Oct 7, 2024
Closed
@jahnvisahni31 Please merge my PR. |
PrayanshParmar
added a commit
to PrayanshParmar/DesignDeck
that referenced
this issue
Oct 10, 2024
PrayanshParmar
added a commit
to PrayanshParmar/DesignDeck
that referenced
this issue
Oct 10, 2024
PrayanshParmar
added a commit
to PrayanshParmar/DesignDeck
that referenced
this issue
Oct 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Hello,
I noticed that the project currently lacks authentication, and I would like to contribute by adding authentication using Clerk.js, which integrates seamlessly with Next.js. Clerk.js provides a simple and secure way to manage user authentication, offering features like social logins, multi-factor authentication, and more.
To get started, it would be helpful if you could provide a list of the routes in the project. This will allow me to appropriately classify them as either public or protected.
Here is a brief outline of what I plan to do:
Set up Clerk.js for authentication.
Implement public and protected routes as per your guidance.
Ensure smooth integration with the existing architecture.
Please let me know if you're open to this contribution and provide the necessary information regarding the routes. I'm happy to discuss any specific requirements or constraints you might have.
The text was updated successfully, but these errors were encountered: