Post-election debrief and to-do

[mhulse]

After election, discuss how things went and areas we could improve.

Things to-do:

• [ ] Collect all JSON files as text files and put in REPO; update JS to point to the local files.
• [ ] Update bower.json and package.json to point to specific version numbers.
• [ ] There is an Election AP category. Wire it up.

• [ ] Note to Micky: Chris F. noticed it, so I commented out the endorsements include on templates/grids/opinion/opinion01.csp. You should double-check that I didn't make a total hash of it. Thanks.

  Reverting this change: https://github.com/registerguard/rg/commit/fc845f782da10d3d380a44095717c1fe93fa0b58#diff-b11b8a24c2bf87ca2a2473a59ba047f7R5

• [ ] Also, per Dave B./Carl, commented out pagetop banner in /templates/sections/section01.csp, so that could use a look too.

  Reverting this part of this change: https://github.com/registerguard/rg/commit/374d9899874cc8766ffb40a00ac763d4e715ba1a#diff-b2f22d3f07f5c11d1a2344a1126a9aceR159

• [ ] Turned paywall back on in news and local, in /assets/includes/head01.csp.

  Reverting this change: https://github.com/registerguard/rg/commit/374d9899874cc8766ffb40a00ac763d4e715ba1a#diff-7efd0344ed054c888d8a72ac3771694fL54

… ad more here.

[jheasly]

I think what we should do next is get this on a test set-up where we can stress it with Rick's load tester until it fails the same way: • about 250 simultaneous connections (which I think is about the traffic Rob was seeing on the analytics) • about 20 locks on the ballot_contest table • JSONP callbacks taking ~20+ seconds to complete What we should do is use the election night telemetry to our advantage; break it again, fix it. Job done. It's like we're 990 miles of the way on a 1,000-mile journey. We're so close!!!

... and then build more sophisticated performant things with what we learn from the above!

[robertdenton]

+1 to what John said.

Analytics

• 6,512 total pageviews
• 4:59 average time on page
• 4,000+ were referred from the email
• 4,295 from Eugene, 254 cities total
• Browser
  • 49% Safari
  • 22% Chrome
  • 14% Firefox
  • 10% IE
  • 2% Android
• OS
  • 44% iOS
  • 28% Windows
  • 16% Mac
  • 11% Android
• Screen res
  • 20% 768x1024
  • 16% 320x568
  • 8% 1366x768
  • long tail, 155 screen res's

Thoughts: Extremely popular, especially from the email blast. Could have easily double numbers if it were pushed on social media properly. The fact that we had the problems that we did and still got that kind of traffic is insane.