Make first attempt at applying UI to application.

The layout created won't work properly until all templates inheriting from
`base.html` are updated to use {% block body %} and {% block body_title %}.
The two blocks allow `section#content` to be properly styled.
Update all templates inheriting from base.html

Make all templates inheriting from base.html properly use {% block body %} and
{% block body_title %}. This allow the styling rules in base.css to properly
style the content in `section#content`.
Update page titles.

Make the titles of several pages more consistent.

The page titles, as they stand, are currently awkward and rather useless. It
might be better if, for example, the very top header on the page is used as a
breakcrumb nav section, linking to each portion of the current URL (RESTful URL
design makes this possible). The more friendly and informative page title could
then reside with the remainder of the content. For example, this might go at the
very top of a page:

    <ol>
        <li><a>Item</a></li>
        <li><a>{{ item.id }}</a></li>
        <li><a>Update Form</a></li>
    </ol>

And this would go at the top of the content just following it:

    <h1>{{ item.name }}</h1>
Add "breadcrumb" navigation element.

The semantics of `base.html` have changed. The layout of that file now has this
top-level design:

    <body>
        <nav id='sitenav'>...</nav>
        <section id='shortcuts'>...</section>
        <nav id='breadcrumb'>...</nav>
        <section id='content'>...</section>
    </body>

nav#sitenav allows navigation between top-level sections of the site, such as
/item and /tag. nav#breadcrumb allows navigation within a single section of the
site, such as /item/42/update-form and /item/42. section#shortcuts contains
tools such as the log out button and "priority categories" (links to groups of
items, filtered by their tags). section#content contains the bulk of content
unique to each page.

This commit removes the <div> introduced in the previous commit, and the
contents of each template inheriting from `base.html` are much more natural.
Reorganize template `base.html`.

Change layout from this:

    <body>
        <nav id='sitenav'>...</nav>
        <section id='shortcuts'>...</section>
        <nav id='breadcrumb'>...</nav>
        <section id='content'>...</section>
    </body>

To this:

    <body>
        <section id='shortcuts'>...</section>
        <nav id='sitenav'>...</nav>
        <nav id='breadcrumb'>...</nav>
        <section id='content'>...</section>
    </body>

The latter layout makes more intuitive sense (to the author).
Link "breadcrumb" navigation elements.

Create links in all breadcrumb navigation elements. For example, `item-id.html`
contains the following:

    {% block breadcrumb %}
        <li><a href='{% url 'elts.views.item' %}'>Item</a></li>
        <li><a href='{% url 'elts.views.item_id' item.id %}'>{{ item.id }}</a></li>
    {% endblock %}

This change means that the user finally has a full set of basic navigation
elements for the site. `nav#sitenav` provides navigation between each top-level
section of the site, and `nav#breadcrumb` provides navigation within each
section of the site.