Front-End

• Discuss with team: Either
  A) write a component that is a form that inputs Admin into the database
  B) write a special login page where a user can make themselves a user.
  **Possibly with a secret key.
  **for this requirement note User model contains userType with “admin” and “user” available to be toggled
• This should make an AJAX request that changes userType in db

Backend

• write routes to update user to admin

view a single product so I can see more details.

For Frontend:

• Display the appropriate book when the url matches the books name or id# (could be something like ‘/:book-name’)
• Write a component to display a single book. This can include things like img, name, author description ect.
• clicking a specific book from the many book view leads to that specific book
• Add products to cart ← button

For Backend:

• Write a route to serve a single book from db
• Send somebody to single page view of the book

Frontend

• Discuss with team: In terms of admin modifying data
  A)Write a component for a separate admin page that had book stock and user data an Admin can modify
  B)Once a user becomes an admin, toggle the regular product viewing page to edit
  **we could use both for different instances.
• have full rights to make backend requests to add, edit, and remove products.
• submitting a form or clicking on the button should make an ajax request that updates db
• This might include writing a component to display a list of all users with whatever information you pick

Backend

• Write a route to update an existing book
• Write a route to update/delete an existing student

Auth

• ensure only username and hashed password attributes of user profile are contained in json objects (this was already built into boilerplate)
• ensure no 3rd parties can make themselves an admin via postman or insomnia
• ensure no one/only admins can view user data by navigating to bookshopper/api/users

• get book data: using book dataset from https://zenodo.org/record/4265096#.Yd5SsFjML0q
• write book model
• seed database
• write express route for getting all books
• write redux store component for all books
• create allBooks React component

Frontend

• create an admin home page where books (products) can be edited, added, and removed ***these routes will be separate issues

Backend

• create an admin route to all books

***This would be extremely similar to the edit page, because it's pretty much the same form, but may contain the official checkout button.

Frontend:

• Write a component that displays a form with data to input for the user to purchase (address, cc, phone number)
• if the user has an account with that data, the appropriate fields should be pre-populated
• Should make an ajax request to get user data to pre-populate the form
• if the client is a user and does not have this data saved this should make an ajax request to save their data
• Should contain a ‘checkout’ button

Backend:

• write a route to update an existing user

Subtasks

• React view component
• Cart API

Frontend:

• Login Form created already, can possibly edit

• Submitting the form should add the user to the db

• Create User/Profile component for user to enter associated shopping info (ie address)

• User/Profile updating page should persist changed data to the database

• Logged-in-user across multiple devices: I'm logged in on my mobile device and add some items to my cart. When I open the browser on my laptop and log in, I want to see those items in my cart.
  //if user<--->carts/profiles are associated properly this should work

Backend:

• Write a route to add a user /profile to the db

• Should be able to make changes to DB

• model includes:
  firstName
  id
  lastName
  Email
  Password
  {Buyer info -> address, cc, phone number}
  cartId?
  Association-wise, a cart belongs to a user(then books would belong to the cart)

Login

• generate login token
• see a welcome/profile page

Logout

• create logout button on home page
• successfully log out user

view all available products so I can pick from a variety.

Frontend:

• Write a component to display a list of many books
• Write a book sub-reducer to manage book in your store
• display the homepage component when the url matches /homepage

Backend:

• Write a route to serve up many books
• Book Model (may be created at this point)

Single User view is not absolutely necessary. The only necessary thing for a user is to have a persistent cart across multiple devices, edit their cart, and make purchases.

Tier Two will require a purchase history and an edit functionality

Frontend

• Display the student when url matches something like ‘/users/:id’ or ‘/:username’
• page should display basic user details
  -[ ] write a component to display a single user
• Link to the page with the edit functionality when one clicks an edit button
• ??Possible past orders displayed??

Backend

• write a route to serve up single user

• write models
• write associations
• seed database