What’s slated for CSS4 Selectors? - destroy/dstorey
David gives a quick rundown of some of the selectors we can expect to see in CSS4.
5th | 10th | 15th | 20th | 25th | 30th | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
12am | |||||||||||||||||||||||||||||||
4am | |||||||||||||||||||||||||||||||
8am | |||||||||||||||||||||||||||||||
12pm | |||||||||||||||||||||||||||||||
4pm | |||||||||||||||||||||||||||||||
8pm |
David gives a quick rundown of some of the selectors we can expect to see in CSS4.
This thread on whether HTML5 Boilerplate should include Respond.js by default (and whether the CSS should take a small-screen first approach) nicely summarises the current landscape for web devs: chaotic, confusing …and very, very exciting.
Turning text into hypertext. Pivot on people, places and things mentioned in books. I really, really like this.
A framework for banging out ready-made responsive designs.
To quote Jessica: “Seems stupid but it’s kind of a good idea.”
A responsively designed comic. Yeah, you heard me right. Responsive. Comic!
This vision thing commissioned by Microsoft shows a future-friendly networked world where content flows like water from screen to screen.
If you live in the States, please, please, for the love of the internet, write to your representative at fightforthefuture.org/pipa
A damning indictment on the lack of any upgrade path for most Android phones. It’s disgusting that most customers have contracts that are longer than the life cycle of their phone’s operating system (and crucially for me; their browser).
Josh nails it: publishers need to stop thinking in terms of issues:
Publishers and designers have to start thinking about content at a more atomic level, not in aggregated issues. That’s how we already understand news as consumers, and we have to start thinking that way as publishers, too. This is why Flipboard, Instapaper, and other aggregators are so interesting: they give you one container for the whole universe of content, unbound to any one publisher.
Paolo Bacigalupi’s The Windup Girl seems even more prescient now.
This is a great encapsulation of what I’ve been banging on about at conferences for a while now: let’s stop pretending we know the capabilities, network speed or viewport size of a site visitor’s browser.
This encapsulates the difference between the WHATWG and the W3C: a concern for interoperability matched against a concern for procedure.
Rob documents how he approached his first responsive design.
A nicely-designed project to highlight everyday life in a three-week period in England in 1943 by imagining how four people would have used Twitter.
Richard would like your help. Take a few minutes to run through a card-sorting exercise to help classify fonts in a more meaningful way.
I’ve been using Tumblr to store interesting quotations (and cat videos). Findings looks like it could be a good alternative for the quotations (though less good for cat videos). The Kindle integration looks interesting.
A very honest post from Meagan that I can relate to (and Jessica too, I suspect).
Given some recent hand-wringing about the web as a “platform,” it seems appropriate to revisit this superb article from Ben. The specifics of the companies and technologies may have changed in the past year but the fundamental point remains the same:
Everything about web architecture; HTTP, HTML, CSS, is designed to serve and render content, but most importantly the web is formed where all of that content is linked together. That is what makes it amazing, and that is what defines it. This purpose and killer application of the web is not even comparable to the application frameworks of any particular operating system.
Andy responds to Joe Hewitt’s recent despondent posts about the web. I tend to agree with Andy: I think comparing the web to other “platforms” is missing the point of what the web is.
See also: http://benward.me/blog/understand-the-web
A wonderfully in-depth article from Zoe on all the practical aspects of using media queries for layout.
John reinforces the importance of universal access above the desire to build only for the newest shiniest devices:
Universality is a founding principle of the web. It is the manifesto the web has been built on, and I believe one of the key drivers of the almost unimaginable success of the web over these last two decades. We ignore that at the web’s peril.
Rob is back.
The HTML5 doctors are hosting a copy Mark Pilgrim’s Dive Into HTML5 at http://diveinto.html5doctor.com/ and they plan to keep it updated via Github.
Brendan is posting pictures of everything he fabs. Fab!
Sims who are on fire will no longer be forced to attend graduation before they can put themselves out.
Jake Archibald has a blog now. Subscribed.
I got your 1% right here.
An excellent point from Jonathan: both native apps and web apps require an internet connection …and both native apps and web apps can be made to work without an internet connection.
This might sound obvious, but the myth that “only native apps can work without an internet connection” is surprisingly widespread.
Aral takes the words right out of my mouth. This is pretty much exactly how I feel about Dart.
Ethan compiles a list for .net magazine of twenty of his favourite responsive designs.
Superb science-hacking.
Beautiful timelapse.
The Flickr stream for this Niagara Falls haunted house attraction is like some kind of user-generated art piece on the universality of human nature. It’s also very funny in its aggregate view.
Celebrating pornographers who go the extra mile when set dressing classroom porn and actually write something on the blackboard. What do they write, and is it correct?
As part of her with the Institute For The Future, Ariel is maintaining this great blog dedicated to open science and all-round nerdy goodness.
A great collection of the future-friendly techniques of today: progressive enhancement, mobile first and responsive design.
This is great idea! A website for putting the digital makers of Brighton in contact with the city’s student population.
An insight into Elliot’s current design process which highlights the advantages of designing in the browser when you take a content-first approach.
This presentation from Lea contains some CSS gems (and it’s all delivered in HTML).
While others recall Steve Jobs’s legacy with Apple, Tim Berners-Lee recounts the importance of NeXT.
Jason continues his look at responsive images techniques by diving into the nitty-gritty of the various options out there.
This remains one of the greatest pieces of documentary footage ever filmed.
The process behind a responsive realignment …and the end result is very nice indeed.
A visual representation of the design process.
An addendum to the excellent Everything Is A Remix series, focusing on the influences on The Matrix.
Reminiscences of the BBSs of yesteryear that could in time be applied to the social networking sites of today.
A rallying cry from James: since when did we decide that text couldn’t stand by itself without extra layers of “interactive” shininess?
A speculative timeline of future history.
Glenn has written up the discussion that followed his UXCampBrighton talk on web actions.
A rallying cry from Neal Stephenson for Getting Big Stuff Done.
There are echoes of “the footage” from Gibson’s Pattern Recognition in this strange tale of a cold war radio signal.
A terrific presentation on progressive enhancement and mobile web development from Brad at Web Design Day. You can look at the slides, read the notes and watch the video.
Looks like Lyza’s presentation at Over The Air at Bletchley Park was really excellent.
A great little interview with Lyza, wherein she outlines her future-friendly attitude to web development.