clean up PFS markup to fix IE quirksmode issues
add Voter Guide to homepage
fix position A responsive ad z-index issue
add new repeater station to about page [ci-skip]
Add the Rails 4 bin files
Switch to Rails 4 caching for archive pages

Cache individual content, then content group sections, so that changes during
the day aren't as painful.
Use Rails 4 caching on blogs index and blog index

* Use Rails 4 caching for blog_module on blogs page
* Use Rails 4 caching for recent posts list on the blog index page
* Add caching to the `blogs/_entry` partial, and then nested caching to the
  `blogs#show` entry list
* Remove unused `full` checks in `blogs/_entry` partial
Convert homepage top section caching to Rails 4

* Move cache call into the layout partial to try and avoid any confusion
  about which templates are in use
* NOTE: Template changes under `shared/content` won't automatically
  trigger a refresh, but changes to the layout templates should
Add Rails 4 caching for upcoming forum events
Convert Homepage missed it bucket caching to Rails 4
Use Rails 4 caching for BreakingNewsAlert and Masthead Events

NOTE: This does add a SQL query to each page for the BreakingNewsAlert. It's
a simple query, though, so I'm ok to add it now and refine it away later
Rails 4 caching for Masthead Latest News and shared/related_content

* latest_news helper now returns content, not content mapped to articles.
  That's expensive to do every time.
* Change caching in `shared/_related_content_and_links.html.erb`
* Move the masthead latest news caching from `shared/masthead/_news.html.erb`
  to `shared/masthead/_featured.html.erb`
add contributing bylines to kpcc/_segment and new/single_preview
Update caching for masthead blogs and Missed It buckets
Remove a leftover `register_content` call
Switch cache store to `redis_store`
Also change cache store in test and staging
Remove includes for CacheExpirationHelper concern

Only relevant for ContentStore
Add caching to `render_content`; Fix all_news RSS feed

* render_content: Cache the results of our render using the content object
  and the template that we will be using to render. Caches should be
  invalidated if the content object changes or the template changes.
  NOTE: Cache will not currently be invalidated by a change to the asset
  template.
* feeds#all_news: Remove controller caching. Use the render_content
  caching instead.
Remove old BreakingNews expiration logic; Clean up some tests