Responsive Design

By now it’s no secret that the recommended approach for building websites is using components.  Component-driven development is breaking entire web pages into smaller pieces and working with those pieces individually.  As Stephen Hay puts it in his talk on Responsive Design Workflow, “We’re not designing pages, we’re designing systems of components."

It has been an interesting week since I wrote part 1 of this blog series. For one, more people have been talking about the <picture> element and that is a good thing because the more we talk about it the more attention is brought to an issue that is due for best practices and standards. Second, more people are experimenting with the <picture> element and this is also good because the more input and feedback we get the better at determining whether this is the way to go or we should move on to something else.

I'm very excited to be a featured speaker at this year's DrupalCamp Los Angeles on Saturday, September 6th and Sunday, September 7th. This event, held at annually at the conference center at the University of California, Irvine, is a free event for the Drupal Community of Los Angeles, Orange County, and the Greater Southern California area. My session will focus on Responsive Web Design using Sass.

The release of Apple’s new iPad 3 is a reminder of how quickly the Internet is evolving. In a few short years, smartphones, tablets like the iPad, and e-readers like the Kindle Fire have remade the web as a leaner, more nimble, social cloud.

Drupal has always been a leader in social networking, and the Drupal community does a great job of keeping up with the latest web developments. Drupal founder Dries Buytaert saw the mobile “writing on the wall” over a year ago at Drupalcon Chicago, when he announced the Drupal 8 Mobile Initiative. Things have accelerated since then, challenging the community to keep up.