Eat Up (tm) is a scrumptious social site for scheduling your snacking shindigs!! No more missing out on carnitas because your calendar was too cluttered, no more missing spaghetti due to scheduling snafus - get your designated dining done right with the app that helps you find and manage food related events you’ll want to attend!
Anyone can browse Eat Up and view food related events, but to really harness the power, sign up and then sign in. Being a registered user will allow you to create your own events that you’d like to draw the public to. As a registered user you’ll also be able to RSVP to events of interest to you so you don’t miss a chance to attend those exciting edible endeavors!
A user can now add groups!
- HTML
- CSS
- JAVASCRIPT
- JQUERY
- AJAX
- HEROKU
- HANDLEBARS
- GITHUB VERSION CONTROL
- AWS CLOUD HOSTING
- SCSS
- EXPRESS
- MONGOOSE
- MONGO DB
- As an unregistered user, I would like to sign up with email and password.
- As a registered user, I would like to sign in with email and password.
- As a signed in user, I would like to change password.
- As a signed in user, I would like to sign out.
- As an unregistered user, I would like to see all events.
- As a signed in user, I would like to RSVP to an event.
- As a signed in user, I would like to create my own event.
- As a signed in user, I would like to update my own events.
- As a signed in user, I would like to delete my own events.
- https://i.imgur.com/jVGhplm.png
- https://i.imgur.com/ITX55mJ.png
- https://i.imgur.com/guyRDKx.png
- https://i.imgur.com/v9Wegan.png
- https://i.imgur.com/KBiekoC.png
- https://i.imgur.com/JXLZCky.png
| HTTP Verb | Paths |
|---|---|
| POST | /sign-up |
| POST | /sign-in |
| PATCH | /change-password |
| DELETE | /sign-out |
| GET | /events |
| GET | /events/:id |
| POST | /events |
| PATCH | /events/:id |
| DELETE | /events/:id |
| GET | /groups |
| GET | /groups/:id |
| POST | /groups |
| PATCH | /groups/:id |
| DELETE | /groups/:id |
The team met together to discuss our project and broke it down into the major elements. We the examined those elements to break them down into small tasks. We created a Trello tracking board for these small tasks which were coded by color labels according to the major element they applied to. We decided that our sprints would be every half day so day one started with sprint planning and a quick stand up and we wrapped at lunchtime with a srpint retrospective where we discussed what worked well and what could be improved about our processes.
After lunch we did another stand up and our second sprint planning to determie what tickets were still in progress and what was next in the queue to complete in order to achieve MVP. Any problems encountered were first researched by the developer facing it, and then discussed among the group as an escalation. If we weren’t able to solve the issue via quorum, it went to the issue queue. Problems in process or with the group were otherwise highlighted in the sprints retrospective and addressed by the scrum master.