Future Features

Add screenshots to readme.
Option to not use redis.
The scoreboard will use websockets.
- If websockets are fully implemented, lengthen the auto refresh.
Have an option to not use the score mechanism.
- In most of the javascript files, there is a teamSetup, a boolean will have to be saved logic must follow on page load.
  - buzzer (/)
    - Nothing changes
  - scoreboard (/scoreboard)
    - Cards do not display point values.
  - admin (/admin)
    - UI elements related to modify score values should be hidden.
In the future, the null team will auto select the teams who buzzed in and apply score changes to them.
- Teams with the state BUZZER_PRESSED_FAILED will have their score removed from them.
- The team with the state BUZZER_PRESSED will have their score increased.
Encode and decode team names properly so that whitespace can be within the team name.
Buzzer should change color when sucessfully buzzed in.

Completed

~~Some refactoring can be done with the class changes done with jQuery.~~
~~Security / Login features~~
- ~~Only relevent if the people I show this to are being jerks or if I use this in a more public setting.~~
~~Have an admin shortcut to select only one team. Currently the admin has to deselect any other team (may be more than one) then select the team they want to edit the score for.~~
- ~~Something like a quick double click, or a long click (for mobile).~~
- ~~Or have a config mode where this section is treated like a radio buttons (only one active) instead of a list.~~
~~Buzzer will get a reply from server they they have buzzed in.~~

Change how the team select dropdown works in mobile.
- On the admin page, the current team select can be buggy.
  - If possible, only on the mobile, make the dropdown turn in the scroll dropdown.
Remove dependency on redis.
- Convient when server crashes