WOW! I’m impressed! I bet you guys learned a lot from developing your site! Something that you need to improve is the load time. I’m at school (we have a 60 meg fiber line) and it took awhile for your page to load (it looked like it was grabbing some assets for your css stuff). A great learning experience, but the thing now is, do you have members to sustain it after you leave? for this reason alone, I chose Wordpress. What are you guys using as your backend?
Thanks! We have a bunch of developers (at least five in the web team alone, plus at least a dozen robot programmers) who will be qualified to run the site in the future. Our team’s programming division uses Git and GitHub for all of our development, so learning the workflow for site development doesn’t require much additional training.
They use replication, clustering and load balancing to provide low latency and hight availability and I would say they are pretty good at doing that.
Therefore, the load time must have been due to the Typekit fonts that get downloaded upon the first visit to the site.
Furthermore, since the site is 100% static, there actually is no backend. Everything on the website exists somewhere in the source code. The only time the server needs to do anything other than serve static files is to recompile the site using Jekyll every time we push new commits to origin/master. New blog posts are added by creating new files in the _posts/ directory.
That’s cool! To make our site run faster, and super secure, we use cloudflare as our CDN “front door” to cache pages. We also just turned on the new fast web standard “Railgun”, so hopefully our pages will load faster then they have in the past, which was just as fast too
That’s an interesting way to update blog posts. Very cool!