acritelli/beertracker

Tracker for beer tasting events

beertracker's Issues

Add a navigation bar

This will be necessary as more features are added.

Local js object shouldn't update until 200 response received from AJAX

Submit and CSV buttons are too close together

Ideally this could be solved by adding a navbar, which may be part of adding the "must try" beers.

Use session to stay logged in

A simple client-side Python session should suffice to maintain a user's login.

Name of user should be displayed at top of Dashboard page

CSV file should be ordered alphabetically

Email link to user

Provide ability (but not requirement) to email link to user. Probably implement AWS SES. Additionally, implement ability to send email after event with CSV

Refactor "url" to "uuid"

Currently, the user document in mongo has a "url" attribute. This would be better phrased "uuid."

Add an admin interface

Interface should be able to edit beer list, add beers, change event info, etc.

Add "must try" beers

Add ability for users to create a list of beers that they really want to try before the event.

Refactor dashboard rendering

Currently, the Dashboard is "rendered" via Javascript that makes a request to /users//getBeers. May want to consider refactoring away from this so that a template is rendered instead.

May want to keep the /users//getBeers so that the app provides some RESTful API services, but at the very least the app should return a rendered page in this case. Maybe.

Add rating time stamps

Must Try button should auto submit

Toggling the must try button feels like it should automatically submit a change. User shouldn't have to also hit the submit button.

Navbar doesn't collapse on mobile

Dashboard page should return 404 if user is not in DB

Page will currently load, but without any beers in the list.

Change the DB name

Currently hardcoded as beerexpo

Provide a list of rated beers

There should be a way to see and pivot onto the beers that you have already rated.

Data structure refactor

Entire user document shouldn't be initialized with all beers on creation. Instead, breweries & beers should only be added to user document when they're needed (i.e. a user creates a rating, stars a beer, etc.)