I like theory. I prefer articles, not tutorials. Tell me why to do something, not how to do the current in-demand thing using your favorite method. This is especially true in the case of Responsive Design because, as I am becoming increasing aware, developers and designers are two very different animals with very different mindsets. And, just like not every “instructional designer” knows anything at all about instructional design, not every web designer knows anything at all about User Experience (UX) or User Interface (UI) concepts. And here I was, all this time, getting smug and irritated because those skills have been given a special name (like “instructional design”).
Without the “why” being at the top of your Best Practices or To Do list, your site is useless no matter how adaptive it seems. The user, the visitor is your customer, not the client who blindly asks for this responsive design thing.
I’ve found A Few Good Articles on RWD (apparently, some people feel the need to add that “W” in there) and I’ll add items to this list as I find and read them.
Oh, and BTW, we’re not web designers/UX/UI specialists or whatever anymore, we’ve already moved on to “Responsive Web Design Practitioner.”
- Responsive Web Design by Ethan Marcotte (May 25, 2010) – Like a few other resources I’ve posted, this one is pretty old and yet still far better than any other more recent I’ve found thus far.
I found Marcotte’s article because Rob Tarr began his article with, “If you haven’t read Ethan’s article, stop now, read it, and then come back here.” Class act.
I love it when teachers/writers include why you shouldn’t do something. When I teach CSS, I always start with inline styles, move on to embedded styles, and then linked style sheets so my budding young designer/developers know how much time and effort they’re saving.
- Responsive Design Media and Custom JS by Vasyl Zhuk (September 23, 2014)
I haven’t yet read this next one but am totally intrigued because one of my pet peeves (totes legit, not funny) is elements “moving around” from page to page (or, in eLearning, slide to slide or scene to scene). The home page for the Code for Tampa Bay site I’m working on (not yet live) has a bit more content than the others so it’s “longer” and, thus, has a vertical scrollbar. So every visitor’s first experience is all the navigation jumping a bit when they go to the next page. I’m working on it.
- A Developer’s Dilemma: Responsive Design and the Vertical Scrollbar by Jen Scott (September 2, 2015)
If I find more, I’ll add them. See ya.