As I’ve said before, speaking at An Event Apart is a wonderful, terrifying experience. Wonderful because of, well, the insane caliber of the speakers—imagine taking some of the most fiercely intelligent designers, developers, and thinkers working today, and giving each of them an hour to talk about whatever most excites them about the web. And it’s terrifying because of, well, see above: standing shoulder to shoulder with the likes of Nicole, Dan, Aarron, and of course Jeffrey and Eric is, you know, slightly nerve-wracking.

Being part of this year’s road show has been one of the highlights of my career, traveling through five cities with my web heroes: the audience is fantastic, the speakers consistently wonderful, and I’ve learned something new at each show. Naturally, I’m excited and thrilled to be part of AEA’s newly announced 2011 lineup. I’ll be taking the stage in Boston, and then co-leading another installment of A Day Apart alongside Jeremy Keith. Hope to see you there, whether this year or next!

If you haven’t, you should immediately read Jeremy’s post titled A responsive mind. Not because he says some incredibly kind things about yours truly, but, well, of bits like this:

That’s the thing about responsive web design: you can’t just think of it as a sprinkle of pixie dust that can be applied to any site. It requires the right mindset. It requires that sites be built on solid foundations of best practice. If those foundations are in place—a flexible layout, flexible images, optimised performance—then responsive web design can work its magic.

There are so many wonderful, quotable points that I’m doing Jeremy a disservice by even excerpting that one. If you’d like to understand why a responsive approach would be right for your project (or, perhaps as importantly, why it might not), I urge you to read the whole thing.

Words to tattoo on your knuckles:

Over the past couple of years, my blog hasn’t felt my own, to a degree. It’s felt like I’ve been writ­ing for an audi­ence, post­ing stuff for oth­ers rather than myself. That’s arse-backwards. A blog should be about per­sonal expres­sion. The moment you start think­ing, and writ­ing, to please oth­ers then it’s a bind; it feels less like a per­sonal exer­cise and more of a job.

A beautiful, thoughtful redesign from Mark Boulton (and a responsive one at that). Go go, read read.

Front-end developer Steffan Williams of Gridinator fame digs into some of the rendering inconsistencies across various browsers when dealing with percentage-based widths. Now, I don’t think this is a real problem for flexible, grid-based layouts or properly responsive designs. Some of these rounding issues won’t necessarily manifest themselves in your work, or at least not quite as noticeably.

I was, however, emphatically raising my fist in the air when I read this:

While I’m well aware that things don’t have to look the same in every browser, it just seems to strike me as odd that CSS3 features keep getting touted on the front of browser homepages, and yet something as fundamental as a percentage would be rendered incorrectly (or, rather, not as well as would be expected).

Emphasis mine. Much of the behavior Steffan notes was outlined by John Resig in 2008, nearly three years ago. There are some incredible inconsistencies at play here, and designers really shouldn’t have to shoulder the burden of working around them.

In short, some broad consensus between the different rendering engines needs to be reached—and if it comes at the expense of pushing the Next Hot Bleeding-Edge Experimental Sexy CSS3 Feature™ to market, I’m all for it.

Since striking out on my own, much of my time’s been dedicated to, well, the book. But I’ve also been fortunate enough to collaborate a bit with Filament Group on one of their projects: namely, a large-scale engagement that requires a responsive approach.

Needless to say, I am having the time of my life.

We’re also learning a lot, too. A lot of discussions about approach and execution have come up, largely because processes for a lot of this stuff don’t exist yet. That will, with a bit of hard work and community discussion, change over time. Still, there has been a lot of brilliant stuff created so far.

Here’s just one example:

The goal of this technique is to deliver optimized, contextual image sizes for responsive layouts that utilize dramatically different image sizes at different resolutions. Ideally, this approach will allow developers to start with mobile-optimized images in their HTML and specify a larger size to be used for users with larger screen resolutions — without requesting both image sizes, and without UA sniffing.

Check out the script, download it, and kick the tires a bit—feedback and tweaks are most welcome.

I realize that there are always going to be philosophical differences around responsive web design. But for me, the solutions-driven discussions are always going to be infinitely more interesting to me than the alternative.

I won’t lie to you: I might’ve pounded the table emphatically a few times while reading Mark Boulton’s latest entry:

We can now design effective adaptive layouts that respond to their environment. If these layouts are based on a system that defines its ratios from the content, then there is connectedness on two levels: connectedness to the device, and connectedness to the content.

Mark’s thinking about flexible, content-driven grids has me damned excited about his upcoming talk at AEA Boston, and you know I’ll be flinging fistfuls of lucre at my laptop screen whenever his new book’s available to preorder.

The web really feels fun again.

So that Trent Walton went and redesigned his blog. And it is responsive. And on top of all that? It is sexy.

I’ve been admiring the Paravel team’s work for some time, and especially their dabblings in responsive design; if you haven’t seen the Do Lectures site, give it a whirl. It’s visually and technically impressive, and is a joy to browse at any resolution.

But that’s not all: given Trent’s penchant for full-width, type-heavy headings, he and the team at Paravel decided to knock out FitText, a jQuery plugin to create full-width, scaleable headlines from, well, your headlines. I can’t wait to give this a whirl.

Of course, in the middle of this cornucopia of goddamned fantastic things, Trent has to go and drop beats like this:

My love for responsive centers around the idea that my website will meet you wherever you are—from mobile to full-blown desktop and anywhere in between.

Emphasis mine. That sentence—that sentiment—is so good, I want it tattooed on my knuckles.

(Hrm. Wonder if there’s a jQuery plugin for that.)

There are people you just need to say “yes” to.

I consider myself fortunate to have known and worked with Erin Kissane for years, and I’ve admired her writing for quite some time before that. Krista Stevens has been a friendly fixture throughout my career; she used to run an impossibly tight ship at Digital Web, where some of my first articles were published, before doing wonderful and incredible things at A List Apart. So yeah, when they asked me to work with them on their New Secret Project©, I basically signed up before they could finish telling me what it was all about.

And with that, I’m thrilled to announce that Contents, a new magazine focusing on content strategy, will be launching this fall.

Here’s Erin’s introduction:

The conversation about content strategy, online publishing, and all the subfields and specializations that surround them is flourishing. Wonderfully, it’s no longer possible to keep track of the posts, comments, talks, and events that take place every week within our world. And it’s not just that we’re voluble: our community is extraordinarily generous with knowledge, help, and professional support.

After benefiting from this conversation in so many ways, we’d like to give something back. A bounded collection of ideas and connections. A place to catch up with the movement of our fledgling industry and the much older fields from which it emerged. An editorial lens.

As a designer-person who benefitted immensely from Erin’s and Kristina’s respective books on the subject, this is all music to the ol’ ears. Because I think Contents is going to be a wonderful, oh-so-valuable resource for those of us looking to better understand content strategy (myself included), and I’m excited to contribute a little bit to making that happen.

In short: because of folks like Erin, Krista, and the oh-so-capable Erik Westra, I know Contents will be something special. You should check us out on Twitter, and maybe contribute an article or eight if you’re so inclined.

I’m doing a disservice to this lovely interview with Shaun Inman—one of my favorite designers and people—by quoting it, but, well:

How do you stay focused?

I’m not sure that I do. I’m kind of all over the place, with my attention split between web apps, iOS games and apps, and Safari extensions…. If I feel my focus waning, I let it wane. Curiosity or that unpleasant feeling of leaving something unfinished usually draws me back to a problem or task before too long.

“5 Minutes on The Verge: Shaun Inman”

This. Oh, so very this.

I’m sad to say that due to a personal matter, I’ve had to bow out of speaking at this year’s Mobilism conference. You might have seen PPK’s announcement to that effect, and I’m definitely disappointed I’ll miss the event.

Because let’s be honest: my absence isn’t going to do a damned thing to diminish how amazing this conference is going to be. Seriously, look at this lineup. Look at it. Learning from the likes of Scott Jenson, Stephen Hay, Jake Archibald, Lyza Gardner, and Jason Grigsby is too good to be true, and in Amsterdam? And if you haven’t already, watch Jeremy Keith’s epic mobile browser panel from last year, a performance he’s repeating again in May.

Yeah okay I’m officially depressed all over again about missing it.

Seriously though: while I won’t be there, you can be. If you haven’t already, go register for Mobilism 2012 in May. You’ll have one hell of a time.

I’ve always sucked at writing.

Not the words, mind you: those usually come easily. (When I remember to sit down and write them, that is; hellooooooo, sad and neglected blog.) It’s more the process of the thing, I guess. It’s a struggle for me to get ideas down quickly; I get intimidated by the promise of that final draft, of shipping, so I often feel every word needs to be perfect as soon as it’s typed.

(No, I’m not going to tell you how long it took to write this fucking blog entry.)

Anyway. So, yes: writing’s hard. But I’m learning how to make it easier. And, alongside a few friends, I’m working on something that might make it easier for you, too.

Last year, I had a long conversation with Mandy. She talked about this idea she had: an idea for a tool that would facilitate conversation, discussion, and, most importantly, iteration during the writing process. Not just an application, actually: more a set of features to support a workflow, one that would, if done right, make writing not just easier, but better.

She and Jason had already sketched out how it might work. Soon after, David joined our merry band, and turned our responsive prototypes a living, breathing application. And Rob joined our team recently, and has been, as Mandy said, effortlessly solving problems we once thought impossible.

I am beyond honored to be a small part of this team, and I can’t wait to show you what we’ve been working on. We call it Editorially, and you can read more about it on our first blog entry.

Stay tuned.

These thoughts aren’t especially well-formed, and/as I haven’t had my coffee yet.

So with that disclaimer out of the way, I have to say I’m a bit disappointed to hear Opera’s news: namely, that they’re abandoning their browser’s Presto engine, and adopting WebKit/Chromium instead.

Other folks far, far smarter than I have already weighed in. And don’t get me wrong: I’ve had my fair share of gripes with various bugs in Chromium (especially recently), but it’s a fantastic piece of software; as a friend said recently, ten-years-ago-me would’ve killed to have browsers as fine as we do now.

But right now, what I’m most worried about is the lack of diversity: four rendering engines is not exactly a large number, and going to three is a significant shift, if not an outright loss. Additionally, I worry we’re already facing a rather “well, it works with -webkit, so why worry about anything else?” mentality, which is something we’ll have to work harder to combat. Especially with an engine as fragmented as Webkit.

Of course, since the news is all of, like, minutes old, this is all speculation. Hell, it’s not even that: this is all just a pre-caffeine ramble, and not an especially well-formed one at that. I will say that Bruce’s take leaves me feeling hopeful. And I hope he’s right, and I’m wrong to be a bit disappointed. But right now, I know there’s one less (fantastic) rendering engine in active development, and that makes me a little sad.

Having a bit of a problem with my laptop lately, and thought I’d write up the problem in case it’s affecting anyone else:

So my MacBook Air (mid-2009, OS X 10.8.3) When my computer wakes from sleep, it doesn’t immediately reconnect to my wireless network. What’s more, if I open up the wireless menu in OS X’s menu bar, it doesn’t show any networks nearby. Zip. Zero. Zilch. It’ll scan for new networks repeatedly, but won’t see a single one.

But here’s where this gets really, really annoying: if I open the Network panel in System Preferences, all nearby networks are immediately visible without delay.

Given the weird inconsistency between the two menus, and that I can reproduce this issue consistently, I figure this is a bug: either with 10.8.3, or with my aging little laptop. Either way, I’d love to fix it. So if you’ve come across this problem and know how a workaround, suggestions via email or Twitter would be most welcome.

Update: Charles Gaudette suggested on Twitter that it might be a couple , and pointed me toward a page showing how to clear out corrupted plist files. Deleting the com.apple.network.identification.plist and com.apple.airport.preferences.plist files seems to have done the trick—thanks, Charles! And thanks to everyone else who wrote in or twittered suggestions at me.

A confession: I love working in Keynote. Love it.

(I’m speaking, of course, of Keynote ’09. Not the feature-stripped version that was released last month. Still, I’m hopeful it’ll improve over time, since it is so very pretty.)

It’s not perfect, mind you—after four or five years of use, the program’s got some not-insignificant stability issues, crashing way more often than I’d like. But after all that time it’s still one of my favorite visual editors: it’s great for quickly prototyping UI components, sketching out ideas for animation timing, and, yes, making slides.

Anyway: over the years, folks have said some very kind things about the visual design of my presentations. I don’t have any special knowledge about Keynote, mind, but thought I’d share a couple things I use in my presentations, in case anyone else finds them helpful.

First up: Magic Move.

Basically, Magic Move is a transition you can apply between two slides. If the second slide shares any objects—images, text boxes, or what-have-you—with the first slide, those objects will be, well, magically moved from one position to the next.

Here’s a very, very simple example:

As you can see, there’s just one object on both slides: a picture of my good friend Dwayne. The image is the same on both slides—you can duplicate the slide, or copy/paste the object to the second slide—but since its position changed, Magic Move kinda tweens the photo to its new position.

Now, I don’t use Magic Move a lot, usually preferring to just lean on simple dissolves between slides. But it’s great for managing more complex animations, like this one:

This animation requires a bit more setup, but the principle is basically the same:

1. In the first slide, the “screenshots” you see are basically a lot of tiny little screencaps, each containing just one element of the interface. (So there’s an image for the toolbar in Editorially’s editor, another for the discussion panel, another for the account menu avatar, and so on.)
   1. When I’m arranging complex flyouts like this, I’ll usually have a reference screenshot on the canvas as a base layer, and place the smaller screencaps atop it. Just to make sure everything’s aligned, that is.
2. Then, in the second slide, I move all those small images where I’d like them to end up.
3. Turn on Magic Move, and you’re left with a neat little flyout cross-section of an interface.

As with most things Keynote-related, Magic Move is pretty reliable…but the more you use it, you’ll probably run up against a couple idiosyncrasies. You can’t magicmove (oh god i’m so sorry) an object if it has any builds or actions on it; animated objects (YES MOM, I’M TALKING ABOUT GIFs) will just blink to their new position; and some objects might move completely counter to what you’d expect.

And as with anything animation-driven, it’s very, very easy to overuse and abuse: try to consider marrying the animation with what you’re actually saying, and ensure the visuals don’t outwhelm your words as you’re presenting. That said, Magic Move is a fantastic tool to keep near at hand—when used just right I think it can be, well, kinda magical.