Model shouldn't know about things like close buttons, visibility, and so on

Hacking the Python, because our JS dependency management is borked.

It appears that one notification stealing focus from another causes some weirdness:
both clicking on a button on one view triggers the event on both views (the original
and the new view that stole the div). As long as the first view does *not* define
any click events, everything is fine -- this is the case for the saving notification.
I'll worry about the reason for this later; it has something to do with views
listening to models even after they no longer should be.

To create handy WarningMessage, ErrorMessage, and ConfirmationMessage classes

And delete `CMS.ServerError`

Hook up course name edit interaction, with notification framework

Not that it really matters, since the changes are invisible :)

So that modifications don't affect the model

Matching docstring in feedback.js models

removed symbolset, replaced with fontawesome throughout for new buttons; updated old code for new button at bottom of grading to also use the FA style

add MITX Feature setting to enable django admin site