Here we are using a JSON file full of beer(:beers:) information to act as a substitute database.
EJS is being used as the templating language for its server side capabilities and because I like it, however that can also be changed to suit the users preference.
- Fork repo
- Pull to local machine
- Download dependencies
- Start server (npm start or npm run dev_start)
It's THAT easy
1: forms to:
- add beer object
- edit beer object
- delete beer object
- display beer object
- show all beers
- filter all beers
2: Improve and maintain app stability through development
3: Ensure appropriate test coverage