The document discusses the limitations of the term 'responsive web design' (RWD) and the author's contemplation on the broader aspects of the approach. It introduces a playful 'responsive web abc' that includes various disciplines and activities relevant to RWD, highlighting the complexities involved beyond mere design. The author invites input on additional terms, emphasizing the importance of understanding user needs and context in the RWD process.

1.
By Mads Fuhr
Responsive Web ABC
Responsive Web Design as a term might not be sufficient enough. We need to
think before, between and beyond.
First of all: Sorry to disappoint anyone who were expecting a thoroughly
tested check-list of things to keep in mind, when doing responsive web
design. This is not that article, this is just a fun exercise I did last night…
I couldn’t really sleep and I had a presentation the next day on responsive web
design. The presentation wasn’t the reason why I couldn’t sleep, but it kept me
laying there, wondering about the subject of responsive and how our
experiences and learning's have already evolved from what we knew way back
in 2010.
Responsive Web ABC
1 of 4

2.
By Mads Fuhr
I started contemplating on the term “RWD” and why Ethan Marcotte (the guy
who coined the term ), chose “design” as the last and third word for this great
approach. I don’t disagree and it reflects very well, what this approach is about,
but I was missing the bigger picture. Even though “design” can embrace
literally anything from conceptual design, user experience design, interaction
design to digital design etc., the many other disciplines you have to go through
in the process, makes this one word (design) inadequate to some extend.
Now I know you have to keep it simple and easy to remember, so adding a
fourth, fifth and sixth word to the phrase would completely kill it. I get that. So
instead I just started going through all the other possible activities and areas
which you should also address, while exercising the RWD approach. Disciplines
like “content, navigation, experience, markup, usability” and so on — which
quickly evolved into a playful game based on the alphabet.
Responsive Web ABC
2 of 4

3.
By Mads Fuhr
So here goes — my “Responsive Web ABC”:
A. Responsive Web Adaptation/Apps
B. Responsive Web Building
C. Responsive Web Content/Context
D. Responsive Web Design
E. Responsive Web Engagement/Experience
F. Responsive Web Front-end
G. Responsive Web Graphics
H. Responsive Web Hub
I. Responsive Web Interaction
J. Responsive Web Jam (any suggestions?)
K. Responsive Web Knowledge
L. Responsive Web Language
M. Responsive Web Markup
Responsive Web ABC
N. Responsive Web Navigation
O. Responsive Web Optimisation
P. Responsive Web Programming
Q. Responsive Web Queries
R. Responsive Web Relations
S. Responsive Web Stylesheets
T. Responsive Web Technology
U. Responsive Web Usability
V. Responsive Web Value
W. Responsive Web Widgets
X. Responsive Web Xperience/X-ray
Y. Responsive Web Yummy
Z. Responsive Web Zen
3 of 4

4.
By Mads Fuhr
Okay so I fell short in the final few words — please share your own ideas on
these and any word for that matter. I’m sure you could replace a lot of them, but
still it gives you an impression and idea of just how many activities you could/
should address in this process. Hint to all our great clients out there ;-)
Because what happens when you talk RWD, is that you quickly start talking
user needs, device strategy, context, content, technology etc. Responsive Web
Design is so much more than just designing a solution, but often you don’t
realize that until you’re knee deep in it.
So next time you face the client brief saying “we need it to be reponsive”, having
this alphabet in the back of your head might be a way to remind yourselves —
and others — about the implications and magnitude a RWD process can result
in.
Responsive Web ABC
4 of 4