US – User Authentication

Value proposition

As a user I want to be able to have my own account In order to create, update and delete my own (secret) Outivities

Outivities–Login

[x] There is a log-in/log-out-button in the header, so the user can sign in/out at any time.
[x] The user can login either with their Github account or by creating an "Outivity account".
[ ] The user has to sign in to create a new Outivity. The "plus" icon in the footer will be visible in both cases but when logged out there will be a notification that this option is only available for authenticated users.
[ ] There will be a small collection of Outivity examples on the Homepage for logged out users to get some inspiration. Users can edit and delete those Outivities when logged-in. When logged out the edit and delete buttons are hidden on the details page.
[ ] The user can only modify his/her own Outivities. So every user has its own secret collection. The idea is not to share Outivities, but to save individual memories.

[x] Create Auth Feature Branch.
[x] Setup next-auth and login.
[ ] Develop Login and Register Components.
[ ] Create Login and Register Pages.
[x] Create login/logout button.
[ ] Hide edit/delete buttons in the frontend so that only logged-in users see them.
[ ] Implement login with Github account / email and password fields and sign-in button.