Make viewer header not be position:fixed (#684).

Also make header box-sizing: box-border so horizontal scrollbar isn't
required.
Fix indentation in viewer code (#715).

Just an indentation fix (and one comment). No semantic changes.
Fix indentation in viewer code (#715).

Just an indentation fix (and one comment). No semantic changes.
Prevent wrapping in header-right menu (#702).

Prevents long usernames from wonkifying layout.
Merge pull request #718 from patternleaf/715-modal-viewer-toc

715 modal viewer toc
Update changelog

Addresses #715
Merge branch '715-modal-viewer-toc' of https://github.com/patternleaf/atlas into patternleaf-715-modal-viewer-toc

Conflicts:
	static/js/viewer/views.js
Update changelog
Merge pull request #720 from patternleaf/702-long-usernames-in-header

Prevent wrapping in header-right menu (#702).
Update changelog
Avoid race condition when updating index

Signal handlers are used to update the search index when SectionAsset
instances are deleted.  This works fine when they are deleted
explicitly, but causes a problem when they are deleted via the cascade
when the related Section is deleted.  When the section is deleted, the
story can't be fetched via ``instance.section.story``.  To work around
this, story a reference to the story in a ``pre_delete`` signal handler
so its available in the ``post_delete`` signal handler.

Addresses #723
Merge fixes for #723 into develop

Conflicts:
	README.rst
Update initial section thumbnail lookup keys

In ``SectionListView.addSectionThumbnail``, wire up a one-time event
listener to update the thumbnail view lookup table's key to be the
section's id instead of its cid when the section is initially saved.

Addresses #725
Disable save button on 'do:save:story'

This fixes a race condition where the auto-save when leaving
the title text input and the save initiated by clicking the "Save"
button both initiate the initial save of the story via a POST to the
API.  This causes 2 story records to be created.

This commit updates ``LastSavedView`` so the state of the button is
updated on the ``do:story:save`` event rather than the click event.

So, when the autosave triggers the ``do:story:save`` event, the
button's state will be updated and disabled so it will not respond
to the click event.

Addresses #728
Invalidate cached places list when story places change

Addresses #730
Bump changelog for version 0.9.6
Make that 0.9.7
Move builder image upload feature spec

Lettuce only permits one feature definition per file
Full process builder test script

This is a test script, written using Lettuce's feature/scenario/step
language, based on tests that @jwirfs-brock documented through
screen captures.

I haven't implemented the steps yet, and may not, but this seems like
a helpful, structured way, to manually test the builder.
Use latest Tastypie APIs

Starting with 0.9.12, Tastypie supports a new Authorization API that
supports more granular authorization checks. Functionality in many of the
``Resource``/``ModelResource`` classes also seems to be more factored
out, creating new hooks that can be used for our customizations.

Changes to our API resource and authorization classes include:

Update ``storybase.api.LoggedInAuthorization`` to use new Authorization API
instead of the old ``is_authorized`` and ``apply_authorization_limits``
methods. See
https://django-tastypie.readthedocs.org/en/latest/authorization.html#the-authorization-api

Add an authorization class, ``PublishedOwnerAuthorization`` to
encapsulate object list authorization that is repeated across
a few different resources. At some point, I think it makes the most
sense to move this into custom queryset methods implemented for each
model. This seems preferable to spreading authorization code throughout
the code base.

Move authorization checks out of ``obj_get_list`` as the kind of checks we
need are now possible in the authorization classes

Remove ``DelayedAuthorizationResource`` as the new Tastypie API now natively
offers more granular authorization checks.

Remove ``request`` as an argument from many of the resource methods as it
is no longer passed. In many cases the request is accessible via
``bundle.request``.

Update the signatures for resource class methods so that they accept
the ``bundle`` argument. ``obj_get_list`` is one example of a method where
the signature had to be updated in multiple subclasses.

Replace implementations of ``HookedModelResource`` methods with versions
that mirror the recent ``ModelResource`` implementations where, In many
cases, portions of the code have been factored out into separate methods.

Create an pass an "empty" bundle object in many of the methods of
``StoryBuilderView`` that use resource instances to output JSON to
bootstrap the Backbone views. In some cases, I had to bind the view's
request's user to the bundle's request user so that authorizaiton would
work correctly

Update signature for ``is_valid`` in our validation classes as
``Validation.is_valid`` now takes an optional ``request`` argument