• Body copy is hard to read and makes me squint
• Hovering over the header labels from a post makes the top bar bump down almost like an animation
• Footer project list should make the homepage project list

• Images not showing up for me. My old version of Jekyll?
• Can we get "1.0" into the headline? "Production" is purdy nerdy.
• Can we get that this release has been powered by our community in the deck headline?
• Let's get an updated tally of our total contributor count into the story. There's a management command that cracks this out.
• Can we count what percentage of our lines of code have been written by volunteers?
• I think we should lead with the hard news second graf and flip below it the broader stuff.
• I don't know know if "indecipherable" is the right word. Dictionary check? I'm thinking "cryptic" might be more on point.
• "Normalize" is a little too nerdy maybe
• Update links to the new subdomain
• All the references to tables and fields should link into the documentation
• After the lead and nut, subhead before docs break out

👋 Hello! This is a really awesome project!

URL: https://calaccess.californiacivicdata.org/downloads/latest

I'm not sure if this is a recent bug, but I noticed today that when I click the 'data' link I'm shown the following error:

I can visit https://calaccess.californiacivicdata.org/downloads directly and see the table, but there might be a secondary issue: the size column is a little suspect. All of the datasets appear to be the same size, but missing in the July-Sept records.

It looks like this is the error originates on this line, probably the file_path.split('/')[1] part:
https://github.com/california-civic-data-coalition/django-calaccess-downloads-website/blob/master/calaccess_website/templatetags/calaccess_website_tags.py#L40

GitHub introduced GitHub Actions a while back which replace the webhook integration we were using to trigger builds. We should upgrade to the new system whenever we find some downtime.

See: https://docs.travis-ci.com/user/migrate/open-source-on-travis-ci-com/#existing-open-source-repositories-on-travis-ciorg

https://calaccess.californiacivicdata.org/downloads/

• State the problem. Our code is open. Our passwords can't be.
• Summarize all the working parts we need to link together.
  • RDS database
  • Production EC2 server
  • Development environment on multiple machines
  • Django project that boots and connects with all of the above
  • Fabric deployment routines that can interact with all of the above
  • Chef systems configuration that can interact with all of the above
• Walk through how we solve them one by one
  • A .env file modeled on the 12-factor design system where all the secrets are kept
  • django-dotenv integrates secrets into manage.py and settings.py
  • Fabric scripts that integrate secrets into the env object, Chef cookbook and push to production server
  • Fabric scripts that can update secrets and write to .env