How Vox Media uses Static Site Generators
I’m constantly on the lookout for sophisticated and interesting uses of static site generators. Here’s the forward thinking Vox Media on their use of Middleman as part of their publishing strategy:
In a nutshell, our Editorial Apps system consists of a static Middleman site, which is populated from one or more Google Spreadsheets at build time (using our middleman-google-drive extension, which we’ll talk about in a future article), and then deployed to Chorus by doing a git push and using git post-receive hooks, in a way not unlike deploying an app to Heroku.
Read the rest at Vox Media’s Product blog.
This is interesting for a lot of reasons. Vox is, aside even from their publishing efforts, is on the forefront of content management with their Chorus CMS, so I’m happy to hear that static sites fit into their vision. I’m also interested to hear that their using Google Spreadsheets for data. As easy as I find Markdown documents and YAML lists, not everyone feels comfortable with them and a spreadsheet is comfortable and certainly good for some data, and, of course, using Google Spreadsheets has the benefit of being great for collaboration.
I’ve seen others use this approach. Jim Pravetz used GS for an online shop and wrote about it on his blog (“Generating Jekyll Pages From Data”), though I believe he’s now using Shopify for that site now. Coderwall has a brief tutorial on “Use a Google Spreadsheet as your JSON backend” too.
Vox has made the source code for the Verge-50 site public so anyeone can benefit from their work.