gdominguez210/neverwait

A restaurant reservation application that is inspired by OpenTable.

neverwait's Issues

Issues 10/3

• While the content of the page is largely of a limited width, the header and image should span the entire width of the page.
• If you trigger errors for the signup page, they persist to when you look at the login page.
• Sign In and Sign Up buttons on splash page should dim slightly on hover.
• Login button on login page should dim on hover.
• I think it would be good if the demo-user button had similar effects to the "continue with ${OAUTH}" buttons on the auth modals of OpenTable. That is to say: hover effects and sizing.
• The character used to close the modal is inappropriately proportioned. Try using this character instead: ×
• The link on the login modal that takes you to signup page seems too small. On Opentable it is also left justified, but if you think it looks better to be on the right then I have no problem with it.

Issues 9/25

MVP's:

• Missing 7th MVP. The one described here has Reservations as the second non-boilerplate MVP.

Schema:

• Schema looks good, but it's always nice to check things off.

Issues 10/1

Backend Routes

• A route specifically to get reviews may be unnecessary, as you may want to package that information up with the show action of any given restaurant. However, if you're going to implement only showing a handful of reviews at once, then you will need that route.
• A review show route may be unnecessary, depending on if there's a separate page for editing a review (I've never made a reservation on OpenTable, which makes it difficult to test).
• PATCH, show, and DELETE requests don't need to be nested under restaurants, as if we have the id of a review we'll know what restaurant that review is associated with.

Frontend Routes

• It doesn't seem like reviews are a separate page from a restaurant's show page. Because of this, we probably don't need a separate route.
• There are two pages related to reservations: the page that shows all of your past and upcoming reservations, and the new reservation form. We'll need two routes, one for each component