We’ve long dreamt of a time when we could shed ourselves of the shackles of pixel-pushing to embrace a more idealistic way of working—designing in the browser. Many have tried and many have failed, but it doesn’t have to be all or nothing. In this article, I dissect the design process to explore which tools are the most helpful for certain parts of the web design process.
I’m so proud to be contributing on a site I’ve respected for quite a while now, the Web Standards Sherpa. Review number 23 is a look at how older sites can still benefit from responsive techniques.
For a while now we’ve been feeling that selecting a set of breakpoints and expecting them to work across an entire system of content is only a partial solution. In this piece, I’m exploring the idea that maybe breakpoints should be created when their needed for the specific atomic element that I’m styling as opposed to the system as a whole. Also, there are Matrix references.
I’m so excited to have written something that will actually be printed. The folks at .net magazine gave me the opportunity to share some of the thinking I’ve been doing on how to use responsive techniques on older sites. This is a tutorial-type article and the issue is packed with some great stuff. Many thanks to the wonderful Stephanie Rieger for her technical review and fantastic feedback.
Are off-canvas layouts a shiny new tool ripe for abuse? Just posing a quick question for us to consider.
An explanation of my 30,000 foot view of our industry’s current state as it relates to responsive web design.
For centuries, we have shaped our layouts and typefaces according to the meaning of the content we’re presenting. While this has traditionally been done on fixed-width paper canvases, we need to embrace the fact that the web is not fixed width. Content prototypes give us an opportunity see our content in its real habitat—the web—sooner.