Followup on how it was built here: http://coding.smashingmagazine.com/2012/04/17/beercamp-an-ex...
Full repo here: https://github.com/nclud/2012.beercamp.com
As it stands, how many people will hit the site, see it's not working because they have the wrong browser version, and leave?
I love this casual dismissal of tablet/mobile phone users as if it were a non-issue.
So flash or JS, certain mobile users that should be able to see it won't be able to see it.
Obviously they didn't apply it here fully, but it would have been possible for them to reuse their text divs on text-only browsers, drop their svgs for some prerendered raster graphics on SVG-less browsers, use their SVGs but have them render flat on 3d-transform-less browsers, have static 3d copies of each page if JS isn't available but 3d was, etc., etc.
It's even possible for established sites to collect statistics on combinations of available browser features, estimate ROI vs. development effort and decide which combinations beyond the least-common-denominator are worth coding for and slowly roll them out one at a time.
BTW: works fine in Safari 6.0 OSX
Now, if I could only stop flipping the pages and get back to work...
Very neat effect though. Is this based on actual folding math or is it just a series of neat animations? Like could this be built into a sort of popup book framework?
Latest Chrome on Centos6 using a ssh socks proxy.
edit: solved thanks to http://news.ycombinator.com/item?id=4393135
Chrome Version 21.0.1180.79 works for me.
