Better way to use helper function in controller
It turns out that the accepted answer that I read on Stack Overflow was not the best answer.  The way that I was using was the same thing as the first thing that @cg505 did.  It allowed the function to be called when the controller was being a controller.  Using this method maintains DRY and prevents it from being called when the controller is being a controller (i.e. it is the same as if it was below the line `private`).
Do not show schedule if not logged in
Can somebody else fix indentation?  I am utterly confused by the closing ul tag, so I do not know how indented it is supposed to be.  @cg505, @four04
Fix sorting classes
@cg505 was this incorrect, or did you want period, then course name sorting?  I wanted course name, then period sorting.  But either way works.  I just think it'll be easier to find the course first, then the period (the brain can more easily see a bunch of similar names grouped together).
Change "New Classroom" -> "New Class"
Do not show event description in table
Showing the description will cause the table to become very ugly when a huge description is present.
Fix indentation and such from a96e5e0488b69526d7ab01d2d4167e807959d2e5

That was pretty impressively horrid. I'm sorry for anyone that had to
look at it before this fix.
Fixing sidebar and body stuff.

This works for v0.2.0, is this okay @cg505/@Sammidysam?
Turn New Event link into button
Switch color of new buttons to green
Sassify some stuff. Closes #5.

Most of the stuff in application.css.scss wound not benefit from sass.
Merge branch 'fixes' of github.com:kotct/docket into fixes
More sassification

More can be done with sass than only having methods.
Fix for #28 (error handling for if invalid user id in session token)

Basically just throw in an exception catcher and return nil if an
exception is thrown by User.find
Show user schedule in views/users/show
Merge branch 'fixes' of github.com:kotct/docket into fixes
Adding empty configuration system.

I mostly followed @cg505's comment in #23.
Update db schema to match new configuration migration

Forgot to migrate, now I did.
Add model relationships between configuration and user

Since it's just one-to-one (right?), it should be pretty simple.
Adding "My Account" link to navbar

This will make it easier for the user to get to their configuration in
the future (we'd just change it to user_edit_path or whatever works).
Merge branch 'v0.2.0' into user-configuration

This adds the "my account" link.