Looks like we had a couple of resources that weren't loading over HTTPS on the front page. Should be fixed now.