Brad Frost is a prolific, smart web designer with big credentials (e.g. Nike, An Event Apart), so it’s no surprise that he makes a strong case that generally web carousels are unnecessary (in Brad’s words, “carousels are organizational crunches”) or poorly implemented. It’s advice I’ll consider when I’m reflecting on the carousel that’s running on my home page…it may need a rework.
There are many excellent guides and references online for basic, “core” HTML and CSS. But for more intermediate and advanced topics like media queries and CSS3 based transformations, most great articles tend to be comprehensive yet very narrow in scope. This extended tutorial guide set up by developer Shay Howe and others is different; you’ve get a really nice starter introduction to a broad range of HTML and CSS topics.
One small quibble though; I’d argue the second lesson on “detailed positioning” is content that should be in a basic or starter tutorial, not a guide labeling itself as advanced.
Film Crit Hulk:
>
BUT IN ALL THE PRESS THAT HE GOT TO DO FOR THE FILM, THERE WAS SOMEONE HE REFERENCED TIME AND TIME AGAIN, AND INSTANTLY HULK SAW THE ENTIRE THROUGHLINE.
HOOPER IS OBSESSED WITH KUBRICK.
AND THEN IT ALL MADE SENSE…
HOOPER DOESN’T KNOW FUCK ALL ABOUT WHAT KUBRICK WAS ACTUALLY DOING.
Nice Branch thread where a lot of experienced web developers – David Kaneda, Harry Roberts and many others debate the pros and cons of various CMS options. Interesting to see a lot of support for both Jekyll and Perch, two options I’ve generally overlooked on my own side CMS work.
SlashFilm‘s David Chen:
It is a fact that many people will leave this film thinking that torture, in some way, helped lead to the killing of Osama Bin Laden. That’s what political pundits are getting upset about — the fact that people think torture was effective at all. And if the pundits are correct in saying that the film sends people out of the theater with an understanding that torture was effective, then who is wrong? Filmgoers for not understanding what the film is trying to say? Or Bigelow for depicting torture irresponsibly? As usual, I think the answer lies somewhere in between.
I don’t fully agree with David’s stance here, but his writing and the evidence behind his arguments is excellent.
Author David Bushell’s work tutorial here for Smashing Magazine is notable, not for hitting the usual responsive design notes but his restraint. There’s a legitimate smaller scope with his example: the emphasis is on progressive enhancement and heavy lifting on CSS3 where possible, not flashy jQuery plugins. That’s a good thing.
This article by The Verge‘s Laura June has gotten a lot of buzz online, and deservedly so. There’s so many bits of information I had no idea about (pinball was banned in NYC until 1974?!). The page layout is stellar as well, with pull quotes in big typography against a parallax-style background.
Web developer Philip Walton:
The key to avoid getting tripped up is being able to spot when new stacking contexts are formed. If you’re setting a z-index of a billion on an element and it’s not moving forward in the stacking order, take a look up its ancestor tree and see if any of its parents form stacking contexts. If they do, your z-index of a billion isn’t going to do you any good.
Great advice. Read the rest of the article for a more through breakdown, with a simple example, of why this is the case.
Really solid, deep analysis of PT Anderson by Kevin B. Lee over at BFI. You can see a steady change in Anderson’s direction: early works (e.g. Hard Eight, Boogie Nights) tend to be far more kinetic and Scorcese-like, while later films (There Will Be Blood) use the Steadicam in a more restrained fashion.
Every few episodes the Iterate podcast team add an extended roundtable discussion to the mix with generally great results. No exception here: host Rene Ritchie gathers a mix of mobile app developers to predict where the iOS and Android app economy will shift in the long run.