tomtom828 / bucketbuddiez Goto Github PK

Please create the sign up page using an HTML <form>.

We need the user's...

• First Name
• Last Name
• Email
• Password

Make it look cool and refer to the W3 schools if needed
http://www.w3schools.com/html/html_forms.asp

i want to put a environment variable on config.json

Closed Issues will demonstrate the project workflow.

I'm not sure if the Facebook API will be client side or sever-side. It's in client side, we can put your API calls into the public/assets/javascript folder. Otherwise, I guess we can make a custom server-side folder or put it in the controllers folder for now.

The same goes for the image API. I'm guessing we could take 2 paths...

1. a one time query to find an image link and save it to the database.
2. or search a country name in the api and append it to the right tile in the DOM

Not sure which will be simpler at this point.

Continue to work on the Tiles for the add Countries, States, and Cities pages.
Once these tiles are are done, you can apply them to the Profile page.
The profile page will have 3 divs... 1) countries, 2) states, 3) cities.

Edit DB migrations and routes if needed.

Work on AJAX calls on the portfolio page to query for all users who want to go to the same place.

Currently there is a global variable called USER_SESSION that stores the session in the server side code.
This is a work around to passport not saving the user session.

http://stackoverflow.com/questions/36486397/passport-login-and-persisting-session

Pending future updates.

Please look into user auth.
Refer to Ahmed's docs.

Maybe we will need to protect the add/delete AJAX routes?

There are plain HTML files inside the views/layouts folder, you can use those as a starting point for writing the basic HTML look of the site. For any custom CSS or pictures, put them in the public/assets/css or public/assets/img folders. The same applies for in-browser javascript public/assets/javascript.

After we get the look we want it plain HTML, we can migrate those html pages into the corresponding handlebars files and chop it all down to render with the database info.

Creating routes for all pages to be rendered.

• index
• add countries
• add states
• add cities
• user bucket list

Creating routes for CRUD actions.

• Create a new user (and new locations?)
• Updates on user (adding country, city, state)
• Delete an entry (country, city, state, whole account?)
• Read all states, cities, countries and render to DOM as tiles

May also needs to make an API call route? Unsure at this point.

Set up the Database with Sequelize migrations...
Thinking of multiple tables:

1. all users (IDs, names, Facebook id ?)
2. all countries (IDs, names, imageURL?)
3. all states (IDs, name, imageURL?, country_id?)
4. all cities (ID, name, imageURL?, state_id?)
5. have a "user-likes" table?

• (ID, user_id, likes_id)

6. have a "likes" table

• (ID, <type?country,city,state?>, foreign_key)

May also look into linking the countries? Not sure at this point (depends on user experience)