add abstraction around expecting content on scoreboard
use _page instead of _path for navigation helper

I think @iamvery was right here, too.
add skeleton route/action/view for voting
add link to vote
users can only score each team once, says the db
enforce db constraint at model level
create a simple scoring form

I hate forms.  Hopefully this time it will be different.

Hahahahaha
add a route/action/view for scorecard form

At this point this does nothing...
handle the happy case (with mocks) for saving form
add a scope to find teams in same year
add by_user scope to Score
add a dead-simple validator for form
memoize db calls in Scoring::Validator
make passing in the validator make more sense
add a configuration object that can store this data

My constructors are getting cumbersome.  This is probably the wrong
approach, but it seems worth a shot.
add a Scoring::Processor to actually create scores
use configuration obj in form
use config object in validator class
provide sensible defaults for configuration
wrap score params up as Scores objects