This Is the Journal.
There are currently 811 entries in Unstoppable Robot Ninja.
Here are the most recent five.
The Last Five Entries:
As it happens, I’ve written a book. But this time, it’s not a second edition of a little yellow book—it’s a brand new book. It’s called Responsive Design: Patterns and Principles. I really hope you like it.
…okay, so with that introduction out of the way, I’m so very, very proud of this little orange book. As you might guess from the title, the book’s focused on responsive design patterns: the reusable, flexible bits of a design we stitch together, using them to compose a larger responsive design system.
Why spend my time (and yours) talking about tiny layout problems? Well, in the years since I wrote the first book, the industry has moved further from this idea of a “page” as a model for working responsively. Trent Walton often talks about designing “networks of content”, while Anna Debenham talks about patterns as “a solid foundation”. And it’s not just us designers: larger companies like Capital One and Starbucks have said that investing in a modular, pattern-focused design system has helped them go responsive more quickly. And since we’re designing for more devices, screen sizes, and contexts than ever before—far more than when I wrote the original article—it’s more critical than before to see our designs not as big, monolithic entities, but as a system of small but responsive layout systems, easily rearranged at a moment’s notice.
And honestly, I’ve found that pattern-informed design has a ton of interesting, tough challenges. That’s why the three central chapters look at challenges that arise from specific kinds of content: from responsive navigation systems, to strategies for managing images, as well as techniques for managing responsive advertising. But while there are tons of examples throughout, it’s not just a cookbook for design patterns: the first and last chapters are focused on broader principles that will, I hope, prepare you for the new responsive challenges before us.
I should note, of course, that writing a book takes a village. Katel LeDû is, as A Book Apart’s executive director, responsible for bringing this book into being—working with her is a joy. And as they always seem to do, Jason Santa Maria made the cover beautiful, while Rob Weychert designed a beautiful interior for the book. I’m honored to be part of the A Book Apart lineup again—especially since they managed to have Anna Debenham provide an absolutely stellar technical edit. Thank you, all.
Mandy Brown isn’t just a colleague, a one-time cofounder, and a dear friend: she’s also the person who invited me to write both the first article and book about this “responsive design” thing. As a result, I couldn’t be happier that Mandy agreed to write the foreword.
A most special thank-you to Erin Kissane, who’s one of the best editors (and people) I’ve ever worked with. She is a deft, fearless reader, and offered so much insight, feedback, and support on various drafts. I’m not going to lie: I was excited about my book idea, but once I heard Erin was available to edit it, I was thrilled to write it.
And I have to mention that today’s doubly exciting: it’s not just that my book is out, but I’m sharing a launch day with my good friend Karen McGrane. She wrote a book titled Going Responsive, which covers the process-related and organizational challenges that go into launching a responsive site. I’ve read it, and it is, as everything she writes, a wonder: buy ten copies, and give them to your teammates and clients. They’ll thank you, promise.
…phew. That was quite a lot, wasn’t it? I guess if you’re looking for the TLDR, it goes something like this: my first book helped readers understand how to build a responsive page; Responsive Design: Patterns and Principles focuses on the area within the page. And to me, that is an infinitely more challenging, interesting, and important area to work in.
Finally, if you get a moment to read my book, please do drop me a line—here, or on Twitter—if you’ve written a review on your blog/wall/Goodreads/whatever. I’d love to read it, and hear your thoughts.
As always, thanks for reading. I’m thrilled, humbled, and, yes, a little scared that the book’s out in the world. But above all else, I’m excited to see what you make with it.
In recent years, I’ve been lucky enough to do a lot of speaking. As a result, I’ve drafted a set of questions I send to organizers, which help me figure out which events I’m able to participate in. It’s a great way of figuring out whether or not I’ll be a good fit for the lineup—and, like the start of any other client engagement, they help me understand how well the organizers and I might work together.
When I’ve mentioned my list of questions to some colleagues, they’ve asked if they could see ’em—so I thought I’d share them here. But before I dive in, a few quick caveats!
- I should note I’m not proposing that these questions are, like, THE Best Questions™; I’ve changed them significantly over the years, and will probably continue to tweak them.
- I’m also not suggesting you should copy and paste this into your own replies to conference organizers.
Basically, these are questions I’ve been revising over the past few years of speaking, and I’ve found they’re helpful to me: I thought I’d share them in case they spark ideas of what might be helpful to you.
Sound good? Great! With all that folderol out of the way, here’s my list:
If you don’t mind, I have a few standard questions I like to send to organizers. Whenever you have a moment:
- How do you plan to compensate your speakers?
- What kind of audience would I be speaking to? (Size, industry, etc)
- What kind of talk would be most relevant? (“Big picture”, practical, etc.)
- Are you committed to building a diverse lineup of speakers?
- Does your event have a code of conduct?
These might be pretty clear. But as someone prone to fits of over-explanation and blathering on at length, I thought I’d step through each question, and say a bit more about why I ask it.
“How do you plan to compensate your speakers?”
This is a logistical question. But in full disclosure, this is also the question that’s been revised the most.
Historically, I’ve liked being up front about my terms, and starting the list with something a little more direct. (Something like, “Do you have a budget for speaker’s fees? My standard fee for a hour-long presentation is $X, plus lodging for Y nights and travel.”) I felt like leading with terms immediately was helpful for me and the organizer; if their budget didn’t line up with my fee, for example, then we could save a few rounds of back-and-forth over email.
But recently, a colleague suggested this alternate take, which I really like: it lets me start the conversation around how the organizer thinks about compensation for all their speakers, not just me. And I think it’s a nice alternative to leading with my rate immediately; from that initial, more general question, we can start a discussion about my terms, and see how well it lines up with the event’s budget.
So since I like this approach, I’m trying this question out. But like I said, I revise these pretty constantly; it’s possible I’ll go back to my old question, or maybe try a different tack. And maybe a different tack will work better for you.
And of course, I don’t want to suggest that my terms aren’t open to negotiation. (They are!) And I don’t want to imply that I won’t speak for free under certain conditions. (I have!) But in general, I’ve found that mentioning my standard terms as soon as possible helps me be a bit more direct with organizers, and set the expectation that this is a professional engagement.
With terms out of the way, here are the next two questions:
“What kind of audience would I be speaking to? (Size, industry, etc)”
“What kind of talk would be most relevant? (“Big picture”, practical, etc.)”
These are also logistical questions, but of a different sort. This is where I’m trying to figure out what kind of talk the organizers would like me to give, and what the audience’s expectations might be. If I’ll be addressing a non-technical audience, a “hands-on” talk about implementing responsive design might not interest them; conversely, a broader talk might be out of place at a more code-focused conference.
On a slightly more personal note, these questions occasionally start some great conversations about the kind of event the organizers hope to create and, in doing so, the kind of audience they’d like to see at their event. And I love hearing those stories. If the organizers are passionate about the people, you can tell the event’s gonna be good.
And the last two questions, which I love:
“Are you committed to building a diverse lineup of speakers?”
“Does your event have a code of conduct?”
I love ending with these two questions. Lemme step through ’em in turn—here’s the first one:
“Are you committed to building a diverse lineup of speakers?”
To be clear: I’m not looking for organizers to respond with some sort of quota, that they expect to have
Ywomen on their lineup of
But I do want to hear that an organizer considers diversity an important issue. Events that represent more perspectives and backgrounds—not just in their audiences, but onstage as well—are more interesting by default. And those are the conferences I want to speak at.
And from there, I want to hear that they care deeply about the safety of their attendees, and have taken clear steps to protect them. That’s why this is my last question:
“Does your event have a code of conduct?”
I want to work with organizers who see building safer conferences as a worthy design challenge, and who have an enforced code of conduct. As Erin Kissane so beautifully put it,
[To define a code of conduct is] to express and nurture healthy community norms. In a small, limited way, it’s to offer sanctuary to the vulnerable: to stake out a space you can touch, put it under your protection, and make it a welcoming home for all who act with respect.
In other words, diversity and safety aren’t just important to me. They make for better, safer events—and as a result, they’re incredibly important to the welfare of our industry.
That’s why I ask these questions.
And today, there’s a second edition available.
There’s an interview with me at A List Apart that explains the scope of the new edition, and talks about various other things responsive. But if you’re wondering what’s in the new edition? Well, quite a bit. In fact, inside each copy of the second edition—whether an ebook, printed, or both!—you’ll find a little note from me, right up front, that’ll also answer your question.
Here’s my introductory letter in full as, well, I think the whole thing’s relevant:
Oh. Hi. It’s great to see you again.
In this latest edition of Responsive Web Design, you’ll find a whole host of changes: updated figures, fixed links, and a truckload of little corrections.
But ultimately, the three main ingredients of a responsive design—flexible grids, fluid images, and media queries—are as relevant today as they were when I first coined the phrase. So while the structure of the book hasn’t changed that much, I think you’ll agree there are a lot of significant edits throughout. Also, in the years since this book was first published, designers, agencies, and large organizations alike have been producing stellar responsive designs, pushing the concept forward. At every relevant opportunity, I’ve included their work, writings, and research.
One thing hasn’t changed, though. You see, when I wrote an article about something called responsive web design a few years ago, I didn’t think for a second I’d be lucky enough to write a book on the topic. (Much less write another edition of it.) In other words: I’m still very humbled by the attention the idea of responsive design has gotten. But I’m also thankful because, well, that attention’s due to you. Thanks for asking such great questions over email, for the feedback on Twitter, for recommending the book to your friends, and for building such wonderful responsive sites. This new edition wouldn’t have been possible without your help. Even if you’re reading this book for the first time, your interest in responsive design helped make this edition possible.
Thank you so, so much for reading my book. As I said the last time around, I can’t wait to see what you’ll make with it.
PS The line about the pirate hat has not been edited in any way, as it was contributed by my wife, who continues to be much funnier and smarter than I am.
I meant what I said: I never thought I’d be writing a book about responsive design, much less a second edition. The only reason this post even exists is, well, entirely thanks to you.
So, thanks. Really. From the bottom of my heart, thanks: thanks for reading, for emailing, for tweeting, for questioning, for building, for designing. The only reason “responsive design” is a thing is because you all got impossibly, incredibly excited about it.
Thanks for letting me be part of it all.
I can’t wait to see what you build next.
A few years back, I wrote a little article about something called “responsive web design.” When I did, I figured I’d scoop up the
responsivewebdesign.comdomain. And of course, as with so many domains I purchase, it just sat there unused, eventually acting as a glorified redirect to my book. A neglected domain, unseen and unloved, like so many tears in the rain.
So earlier this year, when Karen McGrane and I we were going to start offering some corporate workshops on responsive design, I have to confess: it felt really, really good to finally get some use out of the
In fact, it felt so good to publish something on the site, Karen and I decided to keep doing it: namely, we’ve started a podcast about responsive design, which launches today.
Now, I know better than anyone that a responsive design is built upon a foundation of fluid grids, fluid images, and media queries—but you won’t hear any of that discussed on our podcast. That’s right: no CSS to see here, folks. Instead, Karen and I are
interviewing the people who make responsive designs happen: we’ll be speaking with people that have launched large responsive designs, and hearing about how designing more flexibly has changed the way their organizations design. And after recording a dozen or so of these interviews, I’ve been fascinated to hear how these big responsive redesigns happen. I think you will, too.
And I couldn’t be more excited that our first episode features my friend and colleague Miranda Mulligan, the Digital Design Director at Northwestern University’s Knight Lab. But when I met her, we’d worked together on a little site called The Boston Globe.
In the weeks ahead we’ll speak to people from Condé Nast, Marriott, Capital One, Starbucks, and many more—and we can’t wait to share their stories with you. So point your favorite podcasting app at our RSS feed, or just follow myself, Karen, and/or my responsive design account on Twitter: we’d love to have you tune in.
The web isn’t a “platform” like a native OS: it’s a continuum. Varying support levels work with progressive enhancement.
As he usually does, Jeremy put words to something that’s been bugging me for some time.
As I see it: we play the long game in this business. Standards get authored, browsers implement them (often at a varied, staggered pace), and, over time, we learn to rely on them in our work.
Despite that, we keep getting hung-up on perceived short-term failings in various browsers. No, IE6 doesn’t have
document.querySelectorAllsupport; no, we don’t have wide in-browser access to a user’s camera; no, there isn’t a way to reliably detect touch; no, we don’t have reliable insight into the user’s “context.”
Often, that leads to people deciding the web is being “held back.” So there’s some hopscotching of, say, progressive enhancement—which, in addition to being a great philosophy, has been shown to have real, practical benefits to businesses—in favor of “not being held back.” So, in response, we make the same arguments—good and great arguments, mind, but we’ve been making them for some time now.
I don’t really have any answers here—hell, I’m not entirely sure what I’m griping about. But I do wonder if our collective short-term frustrations leads us to longer-term losses. And seeing the web not as a “platform” but as a “continuum”—a truly fluid, chaotic design medium serving millions of imperfect clients—might help.
I mean, ages ago John Allsopp wrote about “[embracing] the ebb and flow of things” on the web. But it’s taken me some fourteen years to realize he wasn’t just talking about layout: our attitude toward the web has to be as flexible as our designs. And maybe it’s worth remembering that the web’ll get there, eventually—we just need to keep playing that long game.