Add list of those who support the action to FAQ.

Also, note that when people donate, they may also want to make public
statements of support.

Image inside FAQ should scale to size.

Some have complained that the image inside the FAQ does not scale to
size. This corrects that problem.

Move progressbar CSS to CSS file, not hard code.

Also, increase size of progress bar (HT tmarble)

Don't hard code style; use class and improve CSS

This changes the hard-coded style for what I'm calling the
content-with-donate-sidebar. The advantage of not hard-coding style are
obvious, but I'm doing this now rather than later so that I can add
changes to the CSS that causes the width to extend to 100% on smaller
screen media when the donate bar disappears (the latter of which is
already implemented).

Require browser even a bit bigger before left dt.

(HT jgay)

Adjust widths slightly when these are combined.

When we have both dt's and the donate-sidebar floating around, things
get tight. Perhaps there is a better solution than this (e.g., can you
set the @media conditional on there being a donate-sidebar at all?), but
this should be a reasonable hack to fix the problem.

Avoid left floating dt's on small screens.

Set the min-width for the left-floating dt's to 550px, so that small
screens just get everything in one column.

Note that the formatting previously used is now moved purely to @media,
which I don't know how that will impact browsers that don't support
@media in CSS, but OTOH, I believe the graceful degradation is done
correctly here.

Make FAQ entry done in dt look better with CSS.

This is accomplished by three key changes:

* use em rather than px sizes, so that font changes are accomodated.

* Add a margin to the dt.

* center the text in the dt's rather than right align.

Remove footnote about t-shirt shipment

Remove footnote since t-shirts are being shipped already.

Sure up wording for ambiguous modifier

HT jackhill for this suggestion.

Supporting docs for announcement of VMware lawsuit

The VMware lawsuit will be announced publicly momentarily.

s/Conservancy's/Our/

Tony and Karen prefer this.

s/GPL/GPL Compliance/ in menu

Karen and Tony prefer this.

Automatically generate fundraiser percentage text.

Using this span, we can update the number in the fundraising percentage
text automatically. The downside is that non-javascript browsers will
not receive a fundraising percentage, but the upside is that fewer
things need to be calculated by hand, and now only the amount raised so
far needs updated.

Overview: top level menu -> incorporated in about

The overview is now incorporated into the About section of the website,
primarily to make more space on the toplevel menubar.

Shorten longest menu item.

This menu item was the longest on the top bar. We need it shorter now
that we just added something else.

Begin work to highlight sidebar menu correctly.

The sidebar menu, and its related top menu item should match setups used
with other sidebar based pages on the site.

See if making an outer div here fixes formatting.

This is somewhat of a hack to normalize this to other setups used
elsewhere on the site.

Begin templated section about compliance.

There will be a new area of the website specifically about compliance.
This begins the work to make a templated section about it.

Absolute URL back to /blog for year.

<tmarble> if you go to http://aspen.sfconservancy.org/blog/
<tmarble> then you click on 2014 in leftnav [15:46]
<tmarble> you get the new leftnav
<tmarble> BUT the URLS are borked
<tmarble> http://aspen.sfconservancy.org/blog/2014/2015/
<tmarble> http://aspen.sfconservancy.org/blog/2014/2014/
<tmarble> etc.

Fix blog by year index.

Add an additional context data that is always the entire list of years,
and use that instead of date_list for the current queryset.

Correct navigation links.

Earlier commit incorrectly implemented navigation link suppression when
only one page present, such that this was never shown. This is now
corrected herein.

Restore navigation links.

Previous commit incorrectly implemented solution for avoiding showing
nav links. This corrects that.

Move blog index to be part of base template.

This way, it's not on the bottom of pages. This shouldn't cause
trouble, since when date_list isn't defined, nothing is shown by this
code.

Typo fix from last commit:

s/extra_content/extra_context/

More extra_context stuff? Put it all in there!

Simply move the blog_entries field into extra_context and pass the whole
darn thing along to the template.

Typo fix.

<tmarble> also blog left nav is borked [15:11]

Rework blog's custom_index for new pagination.

The pagination support changed, and as was previously done a few commits
ago for news, I'm trying a similar solution for blogs.

In this case, I'm trying to use the existing custom_index() method we
have and adapt it to properly support pagination in the way we want.

I'm not completely sure this will work, but I think it's at least close.

Improve pagination links and text in template.

This should correct various issues with pagination in the press
releases.

Allow additional arguments to listing() call.

The urls setup of old gave us various arguments at call time for
custom_index(), and some where useful. Hopefully, listing() can support
the same type of system, over time, once adapted. Here's an attempt to
get it started, first by supporting paginate_by.

Remove custom_index() method from news view.

I don't believe custom_index() should be used anymore given that we have
this new listing setup. At least, that's what I surmise based on
current error messages. I may bring this back if removing it breaks
something else.

Fix cut and paste error from documentation

This is trying to build a pagination of a news queryset.

HT tmarble for pointing this out.

Attempt to use Django 1.7 Paginator object.

Upon reading
https://docs.djangoproject.com/en/1.7/topics/pagination/#using-paginator-in-a-view

I wonder if we should simply follow this model for pagination of news
items. I've attempted to adapt that herein. This is a first attempt
and likely will have issues.