IMPORTANT - Originally I (Will G) had this idea for the difference between "guest user" and "account holder". However Ife's idea is that the guest user can do everything an account holder can, but the only difference is that their countdowns aren't saved. It's likely we go with the latter, but leaving this issue here for now in case we decide to go with my original plan
On the log in page, the user has the option to log in (or sign up), or continue as guest. The idea of a guest is that they can use the default countdowns (things like Christmas), but they can't create their own (since they have no account to save it to).
Your task is to make it so that a user who isn't logged in doesn't see the whole "My Countdowns" section, and has no option to create new countdowns.
If the ability to sign in still hasn't been created, either put this issue off until it is or just create a front end solution to this for now (and then create a new issue for linking it up to the backend later).
IMPORTANT - Originally I (Will G) had this idea for the difference between "guest user" and "account holder". However Ife's idea is that the guest user can do everything an account holder can, but the only difference is that their countdowns aren't saved. It's likely we go with the latter, but leaving this issue here for now in case we decide to go with my original plan
On the log in page, the user has the option to log in (or sign up), or continue as guest. The idea of a guest is that they can use the default countdowns (things like Christmas), but they can't create their own (since they have no account to save it to).
Your task is to make it so that a user who isn't logged in doesn't see the whole "My Countdowns" section, and has no option to create new countdowns.
If the ability to sign in still hasn't been created, either put this issue off until it is or just create a front end solution to this for now (and then create a new issue for linking it up to the backend later).