mechanicalgirl/progressive_giving

progressive_giving's Issues

content: write tweet text for the recipients who don't have it

find a better way to post to FB

right now, I'm just forwarding from the Twitter account, but that means the FB post gets a Twitter handle that can't be clicked on

what I'd rather do is use the view that returns the Twitter post also trigger a post to FB, but I need to read up on the FB API (and also populate more recipients with FB urls)

add Charity Navigator ratings

add a col to the model to hold the rating

can adding the values be scripted? I doubt Charity Navigator has an API, but maybe I can scrape to get at least most of the ratings?

on category pages, replace Twitter handle with icon

use tiny Twitter (and now FB) icons in place of the handles:

http://www.progressivegiving.com/category/animal%20welfare/

on the suggestion form, add a profanity filter to the form validations

http://www.progressivegiving.com/suggest/

redesign the front page

add a 'hopper' to funnel specific timely organizations to the Twitter/FB account

Give the org name a max font size

Right now it can get goddamn huge, even though the container maxes out at 960px.

set up a Facebook account

newsletter content should be posted to it once a week automatically

start writing newsletter text for recipients

update the by_slug view

e.g., this view: http://www.progressivegiving.com/org/institute-nonprofit-news/

should display the tweet text if it exists, and also the longer newsletter text if we have it for this org

add some design to the blog, then link to it

add a blog feature (don't activate until newsletter text is written for a few recipients)

tweak font sizes on mobile - things are "weird looking"

update the tweet algorithm for already-posted orgs

The algorithm that determines what to tweet first looks for orgs without a posted date, then falls back to those that have already been posted. Of the 800+ orgs in the database now, less than half have been posted so far. But eventually they will all have a posted date.

Before that happens, I want to change the algorithm so that when it goes into that block, it picks an org whose last posted date is at least 90(?) days back.

The date delta is open for debate - with the current recipient count, it'll take more than 200 days to get through them all, so maybe that delta should be longer. Or maybe we should just pick the oldest org, the one that was posted the longest time ago. That would effectively repeat all the previous tweets in order, but if that sequence restarts every 7 months, I don't think anyone is going to notice or care. I certainly don't care.

newsletter signup needs to return something, or redirect after the form submit

add a form page to allow users to submit recipient suggestions

1. store in the same table (as inactive, with a new field to indicate that it needs to be reviewed)?
   or
2. store in a separate table (with a hook that moves it to the main table once it's been ok'd)?

1 - add a new checkbox to the existing model
2 - add a new model
both - new form

logic that hits the existing db on form submit, returns an error message if the recipient already exists in our system

point home page and category links to local slug-based pages

add a blog app

newsletter content should be posted to it once a week (or whenever the newsletter publishes) automatically

set up an rss feed for the blog

slugify all the org names so we can write a view that places each one in the home page picker

for candidates, add a date field for their next election, use that as an expiry

(in other words, don't select that candidate after the expiry date has passed)

design a newsletter template for the MailChimp account