HangOut README: Front End

Important Links:

Deployed Client
Deployed API

BackEnd Reop

Hangout Application Description

This application is designed to track potential event opportunities that a person wants to attend.

It's broken down by event: location, name, date.

The front end is hosted on github pages, and the backend API is hosted on heroku.

Technologies Used

Front-end:
1. HTML5
2. CSS3
3. JavaScript (ES6)
4. SASS
5. Bootstrap
6. jQuery
7. AJAX
8. Git/GitHub
9. Handlebars
10. Moment

Back-end:
11. Mongoose
12. Mongo DB
13. Express.js

Wire Frames

Project 3 - Hangout Tracker - Wireframe

User Stories

1. As an unregistered user, I would like to sign up with email and password.
2. As a registered user, I would like to sign in with email and password.
3. As a signed in user, I would like to change password.
4. As a signed in user, I would like to sign out.
5. As an unregistered user, I would like to see all events.
6. As a signed in user, I would like to RSVP to an event.
7. As a signed in user, I would like to create my own event.
8. As a signed in user, I would like to update my own events.
9. As a signed in user, I would like to delete my own events.


Development Process

Verison 1:

The MVP has a single user creating events that belong to them and can be viewed by them alone.

After our initial planning meeting where we outlined how we wanted to function as a group/distribute roles and assignment, we created the forms for the desired functions and the CRUD operations.

Events for the submit actions were created and linked to the API calls

Decided that we would do a Many-to-Many between events and users.

Unsolved Issues & Future Goals

• We did not allow users to send out messages to all RSVPd users.
• 3rd party APi would like to be implemented

Authors

Brendan M. , Drew M, Kevin O, Steven H.