Skip to content
This repository has been archived by the owner on Aug 20, 2019. It is now read-only.


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

"I'd vote for Hillary, But..." | Hillary Clinton Myths

A website to refute myths and misconceptions about Hillary Clinton. The live version is at

Set up

You can skip this step if you already have Ruby and Bundler installed.

  1. Get Ruby. Note that these instructions are for OS X 10.6+ only, which comes with Ruby, but it's used for system's own purposes. Follow these steps to avoid mucking with that Ruby's config.
    1. Install homebrew
    2. Run brew update
    3. Run brew install rbenv
    4. Follow instructions to hook rbenv into your shell. Basically, you'll need to run rbenv init and then add something like eval "$(rbenv init -)" to your ~/.bash_profile.
    5. Run rbenv install 2.3.1
    6. Run rbenv shell 2.3.1
    7. Run ruby --version. You should see something like
         ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
  2. Get Bundler by running gem install bundler.
  3. Run bundle install in the project folder i.e. i-like-hillary-but to install project dependencies.


  1. Run bundle exec jekyll serve to start a local server.
  2. Copy/paste the server address into your favorite browser's address bar.
  3. You should see the built site.
  4. Making changes to the source will automatically regenerate Jekyll content.
  5. Refresh the page to see the changes.


  1. Run rake. This exact thing will happen automatically when you post a pull request. As a result, your pull request will either have the "All checks passed" or "All checks failed" from a mysterious Travis CI. If you get an error, click on Details to see the results of the test run.
  2. When the test fails, it usually comes up with a list of errors. Here's a handy guide to some errors:
    1. The 404 No error message means that the link in your article is likely leading to a dead end. Please double-check the link.
    2. The 302 Number of redirects hit maximum amount error sometimes happens when the site you're linking to takes special measures to protect against bots (such as the link-checker in our test).
  3. If you are satisfied with your check, but the error still appears, you can suppress it by adding the {:data-proofer-ignore="true"} incantation at the end of the link markdown. For example:
... Well, [one study]({:data-proofer-ignore="true"} indicates ...


Content, UI design, and frontend code contributions are welcome. Please see our list of open issues. Please see our Contribution Guide for more detail. The guide also covers the DevProgress code of conduct and the DevProgress Contributor Agreement.


A site for explaining and refuting common complaints about our next president.







No releases published


No packages published