knees4bees / overlook Goto Github PK

As a customer:

• I should see a dashboard page that shows me:
  • Any room bookings I have made (past or present/upcoming)
  • The total amount I have spent on rooms

• ▪ id
• ▪ name
• 🌟 getFirstName()
• 🌟 calculateTotalSpent() method moved to BookingsRepo

• ▪ number
• ▪ roomType
• ▪ bidet
• ▪ bedSize
• ▪ numBeds
• ▪ costPerNight
• 🌟 formatCost

If you are finished with the functionality and testing of your project, then you can consider deploying your project to the web! This way anyone can play it without cloning down your repo.

GitHub Pages (https://pages.github.com/) is a great way to deploy your project to the web. Don't worry about this until your project is free of bugs and well tested!

If you are done, you can follow this procedure to get your project live on GitHub Pages.

https://github.com/turingschool-examples/webpack-starter-kit/blob/main/gh-pages-procedure.md

(and also as comments, what data from which API endpoints will be needed to satisfy the user story) -- user-story-test.js or something like that

probably make User class and then have Customer inherit from that (so that later Manager can also easily inherit from User)

• ▪ bookings (holds array of Booking instances)
• 🌟 filterByCustomer(customerId) -- return another instance of BookingsRepo so that it can be filtered again and/or so that other BookingsRepo methods can be run on the result
• 🌟 calculateTotalSpent(customerId)

As a customer:

• I should be able to select a date for which I’d like to book a room for myself
• Upon selecting a date, I should be shown a list of room details for only rooms that are available on that date
• I should be able to filter the list of available rooms by their roomType property
• I should be able to select a room for booking
• In the event that no rooms are available for the date/roomType selected, display a message fiercely apologizing to the user and asking them to adjust their room search

Refer to the “Add new booking” section from the endpoints table above!

Note!
If you haven’t already, focus on accessibility at this point. Before moving to iteration 3, please create a branch and push it up to GH so instructors can run Lighthouse and check your dashboard for it’s accessibility audit.

Your app should now support two different types of users. In addition to having a customer, you will now add a manager.

As a manager:

• I should be able to login
  • I will see a login page when I first visit the site
  • I can log in with the following credentials:

username: manager
password: overlook2021

As a manager, upon logging in:

• I should see a dashboard page that shows me:
  • Total Rooms Available for today’s date
  • Total revenue for today’s date
  • Percentage of rooms occupied for today’s date

As a manager:

• I should be able to search for any user by name and:
  • View their name, a list of all of their bookings, and the total amount they’ve spent
  • Add a room booking for that user
  • Delete any upcoming room bookings for that user (they cannot delete a booking from the past)

Refer to the endpoints table above for deleting a single booking

When first arriving at the site, a user should be able to log in with a username and password.

As a customer:

• I should be able to login
  • I will see a login page when I first visit the site
  • I can log in with the following credentials:

username: customer50 (where 50 is the ID of the user)
password: overlook2021

• Upon successfully loggin in, I should see my dashboard.

Refer to the “Get single user” section from the endpoints table above!

• ▪ id
• ▪ guest (holds instance of Customer)
• ▪ date
• ▪ room (holds instance of Room)

• see inspo on Dribbble https://dribbble.com/shots/11283865-Tripper-online-booking-app

• see my starter wireframe https://balsamiq.cloud/ssnyzwu/p9isest/r2278

• and past project wireframes https://balsamiq.cloud/s76d3gm/pr1wc9d/r2278

• ▪ allRooms (holds array of Room instances)
• 🌟 filterByAvailability(dateInput)
• 🌟 filterByType(roomType)