jdmiragliotta / relp

#RELP

##General Project Summary

RELP – Rutgers own version of Yelp. Users will be able to add things to do, eat, see and play at or around Rutgers University. Users will be able to view all the places that are uploaded. Users will also be able to leave comments and reviews. RELP will allow users to search for specific categories such as places to eat, things to do, sporting events, and etc. Users will be able to add all the information via a drop down form.

OUTLINE

###Git Repo – Add Contributors

• Jeremy Miragliotta
• DongHoon Kim
• Richenda Gould

###Heroku App – Add Contributors

• Jeremy Miragliotta
• DongHoon Kim
• Richenda Gould

###Require NPM

• Express
• Express Handlebars
• Express-Session
• Body Parser
• Sequelize
• BCryptJS
• Passport
• PassportLocal – will change after Heroku Database set up
• MySQL

###Set Up Handlebar code

• DefaultLayout Main – Into Layouts
  • Materialize
  • CSS
  • JS / jQuery
• Views
• Index
• Login/Registration
• Place Detail
• Place Listing – Search

###Database Connection Via Sequelize

###Create Cookie Session

###Passport Linkage

• User Info

  • FirstName
  • NotNull, Must Be STRING, validation:Can only accept letter is[ ]
  • LastName
  • NotNull, Must Be STRING, validation:Can only accept letter is[ ]
  • Username
  • NotNull, Must Be STRING, unique, validate 5 to 30
  • Password
  • NotNull, Must Be STRING, validate 8 to 25

• Place Info

  • Name
  • NotNull, Must Be STRING, validation:Can only accept letter is[ ] Unique Address
  • NotNull, Must Be STRING, validation:Can only accept letter is[ ] Unique Phone
  • NotNull, Must Be STRING, validation:Can only accept letter is[ ] Unique Comments
  • NotNull, Must Be STRING, Unique len 3 -500 Category
  • NotNull, dropdown form♣ Star Review

###LINK TABLES - relationship

• Place has many users
• User has many comments
• User has many entries

###Route SetUp

• APP.GET
• Index
• Login
• Logout
• Register
• Place LisT
• Place List Category
• Restaurants
• Activities
• Sites (Tourist – Sports)
• Entertainment
• Add Place
• APP.POST
• User LOGIN
• User Info from form
• Place info from form

relp's Issues

Set up app.post route / User registration

Complete typing routes for categories

Create model for user database

Create this inside the server.js file.

You will need a model for the User and also Places

reference readme file for further instructions.

NPM INIT

NPM init - with detailed JSON information

Connect database via Sequelize

Sync the database via sequelize

NavBar Template

design navbar template in main. allow template to edit nav buttons for different pages

Create main.handlebars

create main.handlebars inside views folder

link Materialize in main.handlebars

add materialize css in main.handlebars

add more ratings and comments

figure out how two different users and add additional information

add css and js folder to main.handlebars

add css and js folder to main.handlebars

add jQuery to main.handbars

code jQuery to main.handlebars

Create cookie session

code this inside server.js file

this will be referenced with passport.

Create table associations

create this in the server.js file

i.e.

places has many users
users has many comments
user has many entries

Install NPMs

• Express
• Express Handlebars
• Express-Session
• Body Parser
• Sequelize
• BCryptJS
• Passport
• PassportLocal – will change after Heroku Database set up
• MySQL

Passport

Add required passport code to verify login information

Database Create

Sequelize Connection to local Database until we add Heroku DB

user-dashboard. handlebars

user dashboard with options for them to:

review their added places
add a new place

Create index.handlebars

Basic layout of the home page will be coded here.

i.e.

navbar, brand image, buttons, links, etc...

Create handlebars for each route.

created.

Handlebar View

Add Views folder

Layouts Folder

Add layouts folder inside views folder

Set up app.get routes

1. Index page
2. Login page
3. Logout page
4. User page
5. List of places page
6. Categories of places page
7. Places to eat (Restaurant pages)
8. Things to do (Activities)
9. Things to see (Tourist attraction, sporting events & entertainment)
10. A page to upload "places"

create post route for user registration

Place detail - Handlebar

Create a place detail/information handlebar. This page will generate the information for all the places that user has uploaded.

Set up app.post routes

1. User registration information must be routed and stored to the database.
2. Place information must be routed and stored to the database.
3. Authenticate user log in via passport.

create user registration.handlebars

Handlebar Layout

Code Handlebar

app.engine(.....)
app.set(....)

Feedback - Week 16 Project

Hey @jdmiragliotta, @RolandoCosme, @donghoonkim1226. I cloned your repo and started looking through your app.

UX:
No error message if I try to log in as a non-registered user.
Responsiveness broken between regular window and mobile, remember to use %s or columns that will auto adjust placement for you.
There's a bar of list items under such as "Profile, Friends, etc" which isn't working. But by displaying those I was expecting more routes/views and relationships/column tables in mysql.

Code Technical:
Watch out when you leave your private/secret API keys published in public places. Use system environment variables to store important information whether it's locally or on your deployed platform (you can use .env, but here .env is public knowledge)

I may not be seeing it, but by looking over your CRUD routes, we rarely check if a user is authenticated before hitting routes. We check for req.user, but not much else. I'm looking for an if ( req.isAuthenticated() && req.user) or something along those lines.

I find it strange that there's a get route for deleting reviews. It seems to work, but if I "accidentally" hit a route and start messing with it, I feel like there should be some kind of "form" or gateway to confirm deleting reviews. Some kind of... post. ;)

Code Design:
We need to break out server.js into its individual pieces into their respective places/folder. models/user.js, models/places.js, config/connection, routes.js, etc. For the scale of this project this seems manageable to read through, but you will find in any "regular" size application that export.modules are everywhere. Try to refactor this and get used to incorporating that into your workflow.

You have incorporated two models and related them with hasMany, but your deployed version seems to error out when I want to add places. Try to add another model like reviews, you can create relationships, so now expand on it. See what trouble you can get into ;)

Overall, You've built a plesant, excelelnt Crud app which pulls data from an API for some reviews. However, is it possible to tie in a search for user inputted Places that grabs data from Yelp? It just seems like two separate products that could make sense to connect. You may also want to double check your deployment because I was able to get an application error pretty early on, so I'm basing my feedback on a local version and the code I can read.

If you wanna chat (probably on google hangouts we could schedule a 10-15 minute meeting) about the feedback or have questions.

Index.handlebars

mark up for landing page

• welcome
• examples of places

search feature

create search fields where users can search for various options

footer.handlebars - partial

code footer as a partial

Create login/registration handlebar

using materialize and css create a user friendly login and registration handlebar.

create model for places database

Create place listing search handlebar

this page will allow user to search and sort through all the place listings.

Registration Form

code registration form

remember routes and NAME in order to pull data

in user-dash

create new
view entries
edit entries
deletes entries