Still hard coded
https://trello.com/c/GSjVYcNz/76-change-hardcoded-drop-down-elements-on-staging

Refactor the code to handle file input type (use a custom button, and automatically submit upon file selection) so that it can be used on multiple pages. Add an upload button on the view/edit page.

Nominal styles for graph - as only have one type not really easy to see how other  colours would work. Style now more in keeping with minimal styles of tables etc..

-- reduced index numbers to single digits
-- resized body min width
-- fixed margins on message box for smaller screen

removed image from tablet size as it was not going to stretch comfortably across 700+ px width. Also reduced min-width for body to 320px as seems to fit chart ok

-- enabled navbar-toggle
-- separated footers
-- set 'a project of internews' into image
-- moved login dropdown to right

-- removing hanging tabs
-- added easing to spinner and adjusted messages box to fit

Fetch the table data using the API, and use the existing view item table to render the content of the widget.

Use django_assets to manage our assets and ensure we can minify js/css, compile less files, and merge all js/css into a single file. For this to work in production, all assets must be statically defined in his/assets.py. To ensure the correct js/css is included, views can invoke hid.assets.require_assets which will raise an exception if the asset is missing. This also has the advantage of making clear which part of the code depends on a given asset. The admin command in django_asset library's latest release does not work with the latest Django - so we use a version pulled from git. See https://github.com/miracle2k/django-assets/issues/52

Move font files under /media/fonts so they can be accessed at the expected place once the css is compiled into one file (font awesome accesses the fonts relative to the css location - so from /css/ to ../fonts/)

Disable mysql foreign key checks on staging, production and jenkins as well. See http://stackoverflow.com/questions/6178816/django-cannot-add-or-update-a-child-row-a-foreign-key-constraint-fails

Revert change to local_settings.py.dev regarding foreign key checks (mistakenly added with other styling changes)