Fix admin auth ordering

Change the ordering of current user authorization/authentication:
  * Check if the current user is an admin first. Check needs to be done
    with '.try(:admin?)' in case there is not current user.
  * If the current user is an admin, it will always pass the next auth
    check by devise (or should, unless something strange is happening).

Only if a user is authenticated and an admin should it be allowed to
see the admin interface.
Reorganize location of app layout partials

Move normal application partials to their own directory and change the
layout rendering to include them from their new location.

Change in in preparation of implementing a new admin layout separate
from the general application layout.
Fill out admin layout

Add in the basic layout for the admin interface.
Create admin header partial
Create empty admin asset files (js, css)
Add Twitter Bootstrap to gems
Bundle in TWBS gem
Make Twitter Bootstrap js/css's available

Include twbs in the admin interface stylesheets and javascripts.
Fill in some of the Admin navbar

Start to fill out the Admin navbar with links back to the root
application and the Admin dashboard.
Add first admin check

Redirect to the new user registration page if there are no users yet.
Use site name as navbar 'home' button
Route to custom User registration controller

Creating admin users will require special actions be done and will
require customization of the registration controller. Point devise
routes to this custom controller instead of using its default.
Move first admin check to home controller

Only redirect to new user registration with the intention of creating a
new admin user if the user makes a request for a 'home' page. Having
the check done in the application controller resulted in an infinite
redirect loop.
Perform first admin user setting in User model

Instead of extending the Devise registration controller, set the admin
boolean value in the User model before the User record is first
created.
Reorganize location on main application assets

Move some assets (css, images) to an 'application' directory so that
admin resources can be easily excluded. This will prevent CSS
properties belonging to the admin interface being applied to anything
in the main application views. Main application images need to be moved
in a similar manner so that they can be properly referenced.

TODO:
  * Move and refrence main application javascripts in a similar manner.
  * Adjust main Admin asset referencing and inclusion to work in the
    same way the main application asset handling is done.
Move/fix admin CSS inclusion & manifest
Separate Application and Admin JS assets

Separate inclusion and handling of JS assets in a similar manner to how
CSS and image files are being handled. A manifest for each appears in
'app/assets/javascripts' and includes any necessary third-party
libraries and all associated files from their respective
sub-directories.
Fix Admin JS manifest file

Include jquery so that bootstrap works correctly. Fix comment styling
(don't use CSS style comments).
Update basic layout of admin interface

  * Ensure doctype is HTML5
  * Allocate column space for new sidebar and main content
  * Affix navbar to the top of the window
Update routes

Remove all Current C_UD actions from the available routes to general
users. Add in all actions for Ideas, Tags, and Currents to the Admin
interface.

TODO:
  * Update all Currents specs to reflect the unavailability of some of
    the routes.