🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻

🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻

The user is someone who is a beer fanatic or someone who is just curious about different types of beers in the world. The user would see on the first page a list of all beers and from there they can view a certain beer. When they are viewing the one beer they can then see certain facts about the beer like, name, description & the ABV. The user can also go ahead and add a beer to their favorites list. Other functionalities that come along are the fact that the user can also delete beers.

🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻

The database will consist of a table of beer that the user will consider their favorites. When the user clicks on a listed beer style then they will see some details about that beer. For instance, when a user clicks on IPA style beer then it will show all of the IPA beers. The user will then be able to add a beer to their favorites, which is the database. Which they can also delete(from the DB). We are only adding favorite beers into the database everthing else is pulled from the API.

🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻

Lauren - Backend/Readme/Logo Design/wireframe 💻

Syed - Backend/Frontend 💻

Abrian - Frontend 💻

🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻

🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻 🍻

We have incoperated a third part API:

• http://www.brewerydb.com/
• Each key for users with standard access has a request limit of 400 requests per day on the read methods.
• Endpoint for Styles Displays the styles that are assigned to beers GET: /styles GET: /style/:styleId

Our dependencies include:

"dependencies": {
    "body-parser": "^1.18.2",
    "express": "^4.16.2",
    "morgan": "^1.9.0",
    "pg-promise": "^7.3.2",
    "react-router-dom": "^4.2.2"
  }