The NYT's Visual Election Outcome Explorer - How we made the D3 decision tree(source.mozillaopennews.org)
source.mozillaopennews.org
The NYT's Visual Election Outcome Explorer - How we made the D3 decision tree
http://source.mozillaopennews.org/en-US/articles/nyts-512-paths-white-house/
15 comments
In general I've been super impressed with NY times visualizations recently. I look at the 538 visualizations daily (http://fivethirtyeight.blogs.nytimes.com/). Sometimes they're splashy and cool, but in general they're just tastefully designed in way that gives quick insight into the data that I wouldn't have gotten otherwise. And that's the really crucial part, I think: culling the data so that the relevant stuff is what jumps out at you.
The NYT Graphics Desk keeps a tumblr where they occasionally talk about the process behind their creations. http://chartsnthings.tumblr.com/
What I enjoy about the NYT interactives in particular is not just their technical sophistication (which is formidable given that the creators of Backbone.js and D3 are among their employees) but the sophisticated information design. There's rarely a graphic that is made to show off bells and whistles. The NYT is far and away he closest to embodying the Tufte spirit and thoughtfulness online, given that Tufte has said very little about best practices in interactives
if you'd like a tufte-esque view on interactive graphics, checkout the PhD dissertation from Ben Fry (the creator of the Processing language). I rather enjoyed reading it, and it isn't crazy dense, it was a nice easy read.
http://benfry.com/phd/
http://benfry.com/phd/
I agree entirely. You never see the cliparty slapshy chartjunk that is most of the infographics online. Any infographic from NY Times is designed to show only the data and nothing but the data. For oil prices, a bar chart, not a chart of barrels.
Exactly. Sites like visual.ly are the 99designs of infographics. They're graphic design 101 projects with often misleading/misinterpreted data thrown on a document the size of the moon. They're hard to read and even harder to digest.
> We use a git-backed preview server that allows us to share versioned previews of graphics (any commit, any fork) and get feedback.
I'm jealous that this exists and I didn't know about it. Anyone aware of something like this that exists in the open-source/SaaS world?
I'm jealous that this exists and I didn't know about it. Anyone aware of something like this that exists in the open-source/SaaS world?
It's mostly open-sourced, available here: https://github.com/mbostock/git-static
Very cool. I love your work.
GitHub supports that. Commits (on any branch) that change images display the images inline, and you can comment on those commits. Example commit: https://github.com/cameronmcefee/Image-Diff-View-Modes/commi...
I actually ran into a very similar problem this weekend. I ended up using gitolite with post-commit hooks that checked out the repo to a directory served by nginx. It ends up taking up a lot more space than Mike's solution, but has fewer moving pieces, assuming you're already running nginx.
Additionally you can use it to set up some fancy rules, like the "production" branch push to a special place, allowing users to create their own repos, and fine-grained access controls via gitolite.
Additionally you can use it to set up some fancy rules, like the "production" branch push to a special place, allowing users to create their own repos, and fine-grained access controls via gitolite.
This may be completely wrong. But is mbostock's http://bl.ocks.org/ an example of this? Makes sense, since he's one of the creators of the nytimes graphics as well.
[deleted]
this is simply awesome, not only cause of the great visualization of data but because the interactions to model your scenarios blew me away. Really need to learn this D3 stuff ASAP.
The NY Times should do a behind the visuals for every post with visuals. Excellent work recently.