Use supporter-page.js & its formatting conventions

The npoacct campaign was launched before the Supporter program, and
parts of its functionality were incorporated into supporter-page.js
ultimately. This commit hopefully now backports that functionality to
npoacct campaign.

Function to compute how far to the goal we are.

This is also inserted by the Javascript code as well, but no reason we
can't compute it server side, too.

Convert npoacct fundraiser to use dynamic content

If this new model works, we should be able to update the fundraiser
amounts in the Django database instead of the HTML.

Correct get call to use arg properly.

This was just a typo in from previous commit, more or less.

Fundraising goal lookup for template: 1st attempt

This seems to be the best approach to pass a fundraising goal record to
a template. While the static hack that tmarble implemented probably
needs work anyway, this is probably the best way currently to interface
certain general data that we seek to place on many different pages
through the templates.

I looked into a templatetags solution, but this seemed more
straightforward and more fitting with Django principles (I think :).

Make defaults for BooleanFields.

According to django-admin check,

(1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.

Just quit it with this relative import stuff.

While I think these relative imports seem to be valid for the running
application, I am having trouble with the django-admin applications
regarding them. I don't see this syntactic sugar as absolutely
essential, so I'm just going to change it now.

Initial hack at a fundraising goal application.

This simple application will simply store the code name and the to goal
of each fundraiser. The so_far number will likely just be updated by
some external script, modifying the appropriate entry in the SQL
database.

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.