If you do any viz work with d3.js, you're probably familiar with the work of Mike Bostock, who is the primary developer of d3 and produces stuff for the New York Times.
The realization I had while looking through a bunch of his examples is that he effectively solves the problem faced by most newsrooms in having to deal with an aging and often-incompatible stack: he simply hosts everything at Github, via a gh-pages branch.
This is brilliant. No worrying that your viz will crash with too much traffic! No having to fight with your news organization's server techs to let you run something in PHP! It's a great idea.
Alas, knowledge of Git isn't something that's very common in newsrooms, so I'm considering writing a module that uses Drupal to manage data sets and visualizations on a Github branch.
With this in mind -- can anything think of a good workflow to incorporate this? I'm thinking Drupal produces everything as a really basic HTML page, with datasets and whatnot being stored in Drupal, but finished visualizations pushed to Github.