• The necessary pattern can be found in the reset password form, add the same pattern in the signup form.
• Use the same icons to make password input visible as in the reset-password form.

fix the warning "This is the 10th instance of Prisma Client being started. Make sure this is intentional."

Sign-in with more than one provider with the same email is not supported, so let the user that another provider with the same email is already used.

I moved to SQL database using drizzle-orm. So, I'm building the new database structure. Here's first ER Diagram:

• use Nodemailer library to send resetting password links and let users to change their passwords.

• should have a page to add words to the database
• should have a page to list all words to delete or edit
• should have a page or modal for editing words

The button doesn't change the language or changes but resets the URL to /

• provide current languages which are tr and en

This is the template, implementation may change in time as I progress.

provide a user schema which will have following fields

• id
• name
• email
• username
• password (Optional since users can sign in with oAuth)
• avatarUrl (Optional)
• savedWords

• The search bar should stay on top of the screen even if a new page gets rendered by dynamic params.
• So, to do that:
• create new route group named search.
• add a layout.tsx which will include the search bar.
• add [word]/page.tsx to render word and their meanings

• for words
• for meanings
• for users

Here are the links that should be in the navbar

• Home
• Word List
• GitHub icon for the repo
• Signup button that navigates to the signup page

Navbar behaviors:

• hide it on scroll down
• animated opening and closing menu on mobile

• make sure that users can't submit empty values
• make sure that spaces removed
• make any other necessary changes about the validation

users should not be able to see the signup page when they are signed in

• navigate users to the "not found" page when there is no necessary query string
• show not found message when there is no matching word for the searched one

• Create next-auth options variable authOptions that can be used in getServerSession
• Create a new function that calls getServerSession(authOptions)
• Create a new folder structure server/api/routers/ and create separate routers for auth and word queries and mutations

• use the combined middleware

• navigate users to /signup
• add sign in with google button on the signup form
• add sign-in page where users can sign in using credentials or Google.

• add a save button on the top right to save the word.
• implement Optimistic approach.
• save the word id to the user's savedWords array.