derekgeorg / project2 Goto Github PK

I'm getting a 404 when I click the navbar lost and found links. I think this can be fixed by using /lost and /found instead of lost.html and found.html in the handlebars files. Then the htmlRoutes will handle where they go.

Create a good description and format well with markdown

If we decide to move away from drop downs, or add input fields, we need a way to parse input in a way that works well with the db

Get our pages directing correctly

Sends a 404

Uncaught SyntaxError: Unexpected token <

when a user tries to login but hasn't created an account

Use the req.user.id to connect our user to their saved data for example their saved searches

User has to sign in again if they go to the landing page.

I'm not sure what we should do about this, if we should do anything. It's kind of a minor detail. But something I noticed

I think we should think about how we're gonna take or describe the input. Right now the field is just a number. But it's not clear if the number is referring to weeks, months, years etc.

It's a string in the database, e.g. "4 years". We could probably keep it as is, and maybe add the weeks, months. years somewhere along with the age.

For new tech and saving user searches

Display results

The footer does not stay at the bottom on larger screens. It would be good to have it stick to the bottom with either position fixed or a bootstrap sticky footer class