Keep the weight attribute of SectionAsset.

This is neccessary to preserve backward compatibility to support stories
created on staging before we had the notion of containers and layouts.

This required editing a past South migration which might be considered
poor form, but I can't really think of a good way to do this otherwise.

Since the app isn't deployed anywhere else I think it's ok.
Render section assets not associated with a container

Closes #143

This implements a strategy for allowing sections to have assets not
associated with a particular section container.  This is needed to support
displaying stories created in the Django admin before the builder and
its notion of layouts and containers was implemented.

The rendering logic is largely moved out of Section.render_html and into
the container template tag
Show captions for HtmlAssets of type image.

Closes #142
Force autopopulation of profile_id field.

Closes #163.

Solution thanks to http://stackoverflow.com/a/11505977/386210
Story template loading in existing instance

Allow the stock story templates to be loaded from fixtures in an instance
that already has content (i.e. the current staging instance).

The stucture for a story template is just provided by a story itself.
This creates a problem with loading the templates into an existing instance
because of having to conflicts on the primary keys of the template story
models.

I worked around this by using Django's natural key serialization (see
https://docs.djangoproject.com/en/dev/topics/serialization/#natural-keys)
to refer to related models by their UUID key instead of the primary key.
This is a bit of an abuse of the functionality, since the UUID isn't a very
natural key.

There was a bug in Django's dumpdata management command that didn't allow
serializing self-referencing models (in our case Section) when using
natural keys (see https://code.djangoproject.com/ticket/16317) that has
since been fixed.  I backported the patch to Django 1.3 and make it
applicable using the apply_django_patches script.

I dumped new versions of the fixture JSON for section layouts and story
templates.  I had to manually edit files to merge in the models from
storybase_help into the ones from storybase_story, to break out the
layout and container models and finally to replace references to primary
keys with "pk": null
Travis CI should run tests for storybase_help

Closes #165
Cleaned up layouts of section editing in builder

A big part of this is centering the section assets in a 940px column,
then calculating the height of the asset containers based on common aspect
ratios of screens/images.

To make it easier to change things up, I've started to employ the LESS
dynamic stylesheet tool. The builder template uses a pattern that
compiles the LESS styles client-side in debug mode, and expects them
precompiled in production. I wrote a simple shell script to automate the
compilation of the LESS styles in scripts/buildless, but should probably
eventually move to something like django-compressor or django-pipeline.
Fix section title editability

This broke when I changed the CSS class of the section titles.
Update Jasmine tests so they pass
Removed debugging message.
Check dropped element before acting.

The SectionAssetEditView's drop event is triggered when sections are
reordered. Perhaps this is because the story section table of contents
bar has a fixed position and likely falls over the SectionAssetEditView's
element.

This commit checks that there is a valid asset id retrieved from the
dropped element's data attribute before going any further.

While this check makes sense, I need to initialize the dropable effect on
the SectionAssetEditView element so that it only accepts items dropped
from the asset list.
Only accept unused assets as droppable.

Closes #184.
Use minified versions of JavaScript libraries
Added error templates.

The design and text for these will need to be updated before launch.
Fix logic for loading builder CSS.

The LESS stylesheets should be loaded WHEN the site is in debug mode
(settings.DEBUG == True), not the other way around.

I also had to enable the "django.core.context_processors.debug" context
processor and set settings.INTERNAL_IPS to make the debug variable
available in the template context.
Update the tag collection's story

Closes #186

Previously, when a new story was created, the TagView's model property
was remaining undefined, even after the story was saved.  This caused
the view's colletion to have the wrong URL and selected all available
tags initially instead of no tags.
Replace getValue utility function with _.result

Closes #188
supporting foundations section on homepage is plugin-ized (intended to be text plugin).
Merge remote branch 'eric/templatizing' into theme

Conflicts:
	apps/storybase_story/templatetags/story.py
marking up twocol templates for use as generic content ("About", etc) pages.