New track Tool plan
Google analytics in prod only:
Review app plan
[ ] Basic review app completed
[ ] Next steps: reconcile pr commit vs individual commit. I want to get the sha into the Pr comment link. To have separate review apps per commit. But pr sha is a hypothetical sha that doesn’t match my branch commit shas. So the same commit that makes the Deploy needs to be the one that writes the Pr comment. Or does it? Are both shas available as Travis env vars during the Pr build?
[ ] Add more detailed log messages
[ ] Play with it a little during the week as I add tracks.
[ ] Need to think how timestamps on posts will need to be once things get more collaborative. How to sequence properly? Final step before merge is an admin updating timestamp to current . Do not use git timestamp unless we want that to reorder tracks. Becomes updated timestamp instead of created at. That might be what I want for tracks actually. AuthorDate
[ ] Add Hugo build info to ci.json
[ ] Master deployment leger. Sequential files in s3 bucket. One for each deployment. The process those files with s3 -> lambda
[ ] Why didn’t Purdue get tweeted? It is correct in the xml feed. Need to check ifttt
[ ] Allow google maps api from staging domain