Skip to content
A national voter mobilization email marketing platform
Python HTML CSS JavaScript Shell
Branch: master
Clone or download
nickcatal Update project to reflect that it's a new fork
This fork of EveryVoter is neither supported nor maintained by
Organizing for Action. As the project is MIT licensed we don't need to
reference OFA anywhere except the copyright notice in the LICENSE.
Latest commit 1e2ceb8 Jul 1, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
accounts Exclude email activity where there is no associated mailing Nov 8, 2018
api Code cleanup (thanks pylint!) May 6, 2018
assets Update project to reflect that it's a new fork Jul 2, 2019
blocks Add paragraph breaks below blocks Sep 24, 2018
branding Update project to reflect that it's a new fork Jul 2, 2019
config Add core files (pip, yarn, django, heroku, etc) Mar 25, 2018
data Add 2018 data to the repo May 8, 2018
democracy_consumer Quick pylint-id'd syntax cleanup (#2) Oct 31, 2018
docs Update project to reflect that it's a new fork Jul 2, 2019
election Quick pylint-id'd syntax cleanup (#2) Oct 31, 2018
everyvoter Update project to reflect that it's a new fork Jul 2, 2019
everyvoter_common Quick pylint-id'd syntax cleanup (#2) Oct 31, 2018
feedback Fix error related to bad parameter change May 11, 2018
geodataset Quick pylint-id'd syntax cleanup (#2) Oct 31, 2018
hirefire Refactor celery/heroku workers Jun 26, 2018
location Add an index to the geolookup model May 9, 2018
mailer Fix pagination template include on Mailing Template page Nov 13, 2018
manage Use `select_related()` on manage page to reduce queries Aug 8, 2018
notifications Add optional daily notification for DemocracyWorks changes Oct 3, 2018
rendering Allow easier access to the mailing template in emails Nov 8, 2018
scripts
staff Use correct pagination placement and template path Aug 8, 2018
templates Rename "Mailings" to "Send Mailings" Aug 22, 2018
user_import Quick pylint-id'd syntax cleanup (#2) Oct 31, 2018
.babelrc Add core files (pip, yarn, django, heroku, etc) Mar 25, 2018
.buildpacks Add core files (pip, yarn, django, heroku, etc) Mar 25, 2018
.coveragerc Add core files (pip, yarn, django, heroku, etc) Mar 25, 2018
.gitignore Add ability to import users Apr 4, 2018
.pylintrc Quick pylint-id'd syntax cleanup (#2) Oct 31, 2018
.travis.yml Add Travis CI (#1) Oct 31, 2018
LICENSE Update project to reflect that it's a new fork Jul 2, 2019
Procfile Allow Celery scheduler dino to process SES feedback Nov 8, 2018
README.rst Update README to reflect the new fork Jul 1, 2019
common-requirements.txt Bump django, python, celery versions Aug 7, 2018
dev-requirements.txt Pylint version bump Mar 30, 2018
gulpfile.babel.js Use javascript-based block multi-select May 22, 2018
manage.py Rename django system folder from kennedy to everyvoter Apr 22, 2018
package.json Update project to reflect that it's a new fork Jul 2, 2019
requirements.txt Bump gunicorn version Jul 29, 2018
runtime.txt Bump django, python, celery versions Aug 7, 2018
yarn.lock Upgrade packages using yarn Nov 8, 2018

README.rst

EveryVoter

EveryVoter is an email automation platform that helps digital teams at organizations involved in voter outreach send customized, targeted “Get Out The Vote” emails at mass scale. Each email can contain its own specific messaging, drilling all the way down to the State House level.

Here’s an example: Let’s say, as a national organization, you want to send state- and district-specific emails on why voters should turn out this year (and who they should vote for).

This is what that EveryVoter email looks like for someone in Wisconsin’s 1st District.

https://everyvoter.readthedocs.io/en/latest/_images/wi_example.png

The key to EveryVoter is in sending around election-related deadlines:

  1. You select the deadlines you want to email around -- dates that could include Voter Registration deadlines, Early Voting or Absentee deadlines, and Election Day. EveryVoter continually monitors and updates these deadlines as states change them.
  2. You write and and pre-load HTML copy into the platform.
  3. You track your emails as EveryVoter takes care of the rest at the right moment.

Your organization’s EveryVoter schedule, then, could look something like this:

  • 7 Days Before Voter Reg Deadline
  • 3 Days Before Voter Reg Deadline
  • 0 Days Before Voter Reg Deadline
  • 2 Months Before Election Day
  • 1 Month Before Election Day
  • 10 Days Before Election Day
  • 7 Days Before Election Day
  • 2 Days Before Election Day
  • Election Day

EveryVoter complements your existing email program by taking care of a large chunk of your GOTV email needs.

Credits

EveryVoter was originally written by Nick Catalano at Organizing for Action. The code for EveryVoter can be viewed at the official GitHub repository, where pull requests can also be submitted.

You can’t perform that action at this time.