The future of designed content

I’ve been snif­fling in bed watch­ing anime all day and now it’s time to write a post about the future of designed con­tent on the web.

A cou­ple of assump­tions going in:

  • The era of ran­dom con­tent shrap­nel has gone on long enough. We can do better.
  • We’ve sud­denly got a pretty bad-ass toolkit! Stan­dards like HTML5 and CSS3; exten­sions like Type­kit and jQuery; browsers like Fire­fox, Chrome and Safari. (And as an add-on to that last one: the sophis­ti­ca­tion and homo­gene­ity of Safari on the iPhone and, one pre­sumes, the Immi­nent Apple Product.)
  • We’ve got some start­ing points, both real and spec­u­la­tive. Peo­ple are think­ing about this stuff. Gan­nett hud­dled with IDEO for a whole year and the big idea they emerged with was… designed con­tent.

At the Hacks and Hack­ers meetup here in SF a few weeks ago, we kept using the words “arti­sanal” and “bespoke” to talk about designed con­tent. I like these words a lot, but I’m also wary of them:

  • I like them because they imply a real care for craft, and they imply that form matches func­tion. They also imply, you know, skill: smart peo­ple doing their best work.
  • I’m wary of them because they can serve as an excuse: “Oh, yeah, we only post one new story every two months because… it’s arti­sanal.” Designed con­tent shouldn’t try to com­pete head-on with Demand Media for page-views and place­ment in Google results, but it can’t ignore the real­ity of the web, either. It can’t be all stock and no flow.

So what I’m anx­ious to see is a syn­the­sis that matches bespoke design to web scale. But what would that look like?

The crew that comes clos­est right now is the NYT graph­ics and mul­ti­me­dia team: they work fast, their work is beau­ti­ful, and it’s often quite story-specific. But it’s also more “web inter­ac­tive” than truly “designed con­tent,” and there’s only so much they can do with NYT-style sto­ries. Those are both pretty sub­tle dis­tinc­tions; you’ll see what I mean in a moment.

Here’s my pitch for who could hit this syn­the­sis, if they wanted to:

Gawker Media.

Here’s why:

  • They’re web-native. They know head­lines; they know linkbait; they know SEO. They have trained with the Dark Lords of the Sith. This is the right foundation.
  • They’ve got voice. You could flip a switch to turn Gawker blogs into mag­a­zines, and they would make per­fect sense. That’s not true for any other blog net­work, and it’s a real achieve­ment. At the moment, those voices are trans­mit­ted through text and the occa­sional spec­ta­cle—but voice can drive design, too.
  • They’ve got scale. Gawker Media isn’t three guys in a garage scram­bling to keep the feed flow­ing. They’ve got cor­po­rate infra­struc­ture, and they could plau­si­bly invest in what I’m about to suggest.

Here’s the plan:

You build a small Gawker Media design desk. It’s just a hand­ful of young, hun­gry, multi-talented web designers—designers who dig edi­to­r­ial, not user expe­ri­ence or infor­ma­tion archi­tec­ture. Then, every day—maybe once in the morn­ing and once in the afternoon—each blog gets to pitch a hand­ful of ideas to the design desk. There’s a fast, ruth­less triage, and they go to work. The goal is to make stuff fast—on the scale of hours, some­times days. Never weeks.

The idea is not to make inter­ac­tive apps and draggy-zoomy data viz! That stuff is too com­pli­cated. Rather, the design desk’s man­date is sim­ply to present words and images in a way that makes you go: Uh. Wow. Just the way this does, or this does. (Actu­ally, yeah, jeez: Hire Jason Santa Maria to set this up why don’t you?)

And Gawker con­tent is a great match for this—almost per­fect, actually—precisely because it’s not NYT con­tent. It’s not, you know, Very Use­ful Infor­ma­tion. It’s punchy, sassy, funny and snarky. It’s chunky, and it should stay chunky. This isn’t about expand­ing blog posts into mag­a­zine arti­cle wannabes; it’s about pre­sent­ing 200–800 words of pure bloggy voice in an orig­i­nal, uh-wow way every time. Actu­ally, no, not every time: instead, only when it really counts. The Gawker Media design desk would develop a sharp, sub­tle sense for design oppor­tu­nity.

(It would have been pretty bad-ass to like, design this post in exactly the way I’m propos­ing, huh? Ohhh well.)

But let me expand on that a lit­tle bit more, because it’s impor­tant. The idea is not to wrap meaty, thought­ful posts like this io9 insta-classic in fancy design. Those are the posts that need it least! It’s like, “yo, get out of my way, let me read.” Rather, the idea is to come up with a new class of con­tent entirely. Again: design oppor­tu­nity.

Now, it’s not imme­di­ately obvi­ous what this new class of con­tent gets you (besides, you know, approv­ing links from Snark­mar­ket) because… Google doesn’t index design! I mean, stop and think about that for a minute: Google doesn’t index design. Even though it has infor­ma­tional con­tent of its own, and even though it con­tributes to clar­ity and util­ity: Google doesn’t index design. It doesn’t know how. When I search for “how to tie my shoes,” Demand Media’s semi-literate blob of instruc­tions is prob­a­bly going to show up above your lovingly-designed dia­gram. Ugh.

But Gawker Media is already past this. They’re not just play­ing the Google game any­more; they’re play­ing the uh-wow game. And that is what this class of con­tent gets you. It gets you more uh-wows and more daily impact. It gets you con­tent that screams to be shared. (Not unim­por­tantly, it prob­a­bly gets you some inter­est­ing adver­tis­ing oppor­tu­ni­ties, too.)

Okay—the point of this artic­u­la­tion is not to con­vince Gawker Media to hire a bunch of design­ers. Rather, it’s get you to imag­ine what blogs like those would look like if they both­ered with bespoke design every day. I think it’s a super-interesting vision.

And it would be even more inter­est­ing if RSS aggre­ga­tors could pre­serve that design and dis­play it inline. No more ran­dom con­tent shrap­nel! Instead, Google Reader starts to look like some crazy scrap­book, with pages pulled from hun­dreds of dif­fer­ent mag­a­zines and pasted together into a seam­less scroll.

Okay, until Gawker gets wise, go read Pic­tory. And let me know if this makes any sense. Can you imag­ine the designed con­tent at Life­hacker and io9 the way I can? Crisp, coher­ent chunks of rich imagery and clever typography—like rocks in the stream?

Semi-related: try­ing to under­stand how peo­ple nav­i­gate rich, designed con­tent… with graphs!

31 Responses

    Tiara says:

    Would that make much of a dif­fer­ence if you’re read­ing it from an RSS reader, which is pretty devoid of style any­way? How about mobile reading?

    Robin Sloan says:

    No, this is what I’m say­ing: I don’t want RSS read­ers to be so stu­diously style-free!

    And yep, mobile too. That’s a great point. What’s a perfectly-designed iPhone screen-full look like?

    Tiara says:

    From my expe­ri­ences with my Nokia n96, design ele­ments usu­ally get in the way of what I’m after on the web­site — if I’m check­ing some­thing on my phone, I prob­a­bly don’t have a lot of time, money, or bat­tery power to try to thumb past oodles of bro­ken images just to get to the content.

    As for RSS read­ers: sim­i­lar prin­ci­ple — I read blogs for the con­tent and find it annoy­ing when a font colour or font size changed up means that the stuff’s unread­able through my feed reader. No point hav­ing fancy design if I can’t read you!! Also with things like down­load quota (in Aus­tralian Inter­net), if you’re rely­ing on design to relate infor­ma­tion, but then make design = pretty pic­tures, you’d be cost­ing peo­ple money.

    As it is, I find a lot of what counts as “great design” overrated…they all have the same “uber web designer flashy new” look. yawn.

    Luc says:

    I’ve been sit­ting on the fence with designed blog arti­cles for a while, and am finally going to try and imple­ment them with the redesign of the lit­tle blog net­work I help run (winningelevenblog.com and fifasoccerblog.com). I (like the major­ity of read­ers I sus­pect) don’t come via RSS, they come via a browser, and that wow-factor is much more spread­able than a catchy google-juiced head­line. It’s not some­thing you can do with every post, but for those impor­tant ones, I think it will add a lot.

    I seem to live on Kotaku / Life­Hacker / io9 at the moment, and I’d love them to be more magazine-style — so yes, I can see the poten­tial as I sus­pect you can — if they can do it, it’d be awesome…

    Ryan Sholin says:

    Yes.

    And RSS read­ers are more likely to click through if they start hear­ing peo­ple talk about the design on the page. I assume, for instance, Jason Santa-Maria’s sub­scribers click through when new posts show up in their reader. An easy way to cue this behav­ior by default is to include a short, say, ital­i­cized, footer at the bot­tom of the post itself (so it shows up in the feed) with a design credit for the post. “This post’s candy wrap­per was hand­crafted with love and grids in New York City by Khoi Vinh.” And I click.

    A minor alter­nate news exam­ple (not count­ing, y’know, a cen­tury of printed pages): lasvegassun.com — While I haven’t known them to design indi­vid­ual sto­ries, other than mul­ti­me­dia pack­ages, they’ve long exper­i­mented with chang­ing their home­page lay­out on a reg­u­lar basis to prop­erly present fea­tured sto­ries. The effect can be an “uh wow” moment or two if you’re a reg­u­lar vis­i­tor to the page. And some­times they just go into Drudge-mode with break­ing news and 14 head­lines in a row. If it dri­ves traf­fic, they’ll try it.

    Dan says:

    Oh, you had me so excited at the prospect of Jason Santa Maria head­ing up that whole Gawker media deal, bravo sir!

    Kyle says:

    It’s a great idea, although I’d say to do it right, you’d want visual design­ers and, depend­ing on the sub­ject mat­ter, some­one who can take a real pretty pic­ture wouldn’t be a bad idea either. The free­dom to con­cept with­out being bound by what imagery you can cur­rently find on Google Images would add a lot to the design desk’s repertoire. 

    Two more points in sup­port of the over­all design desk/bespoke con­tent idea:

    1.) So much of a site like Gawker’s bread-and-butter is increas­ingly break­ing news; traffic’s much bet­ter if you’ve got the exclu­sive. But even then, a lot of the blogs out there would take a Gawker story and make it their own, giv­ing a pal­try link credit. With bespoke con­tent, there’s a much stronger visual brand ele­ment to every bespoke story. There’s no way to co-opt that con­tent with­out giv­ing the Gawker site its due, brand-wise.

    2.) One of the best places to see this in media today — The Daily Show. The lit­tle visual gags that they cus­tom curate each night often times get the biggest laugh. Of course they’re a bit raw and rough, which only adds to their effec­tive­ness within the con­text of a half-hour com­edy show about the absur­dity of the day’s news.

    Jose R Mejia says:

    Have been think­ing along these lines for some time now, so glad some­one artic­u­lated the ideas so well… in my esti­ma­tion, Twit­ter is all the shrap­nel we need, par­tic­u­larly as peo­ple become more famil­iar with it. Blogs/websites should absolutely evolve in the direc­tion of being a bit more stock-y, and hav­ing a richer visual dimension.

    Gavin says:

    Maybe this is the future of mag­a­zine design? And maybe it’ll become more preva­lent with this new Apple tablet device that would allow us to manip­u­late the data in sim­ple ways?

    Either way, I’m in. Edi­to­r­ial passed through design = com­pelling content.

    Scott T. says:

    Some exam­ples of “bespoke” blogs:

    http://dustincurtis.com/
    http://theoatmeal.com/

    And I agree this is the future of “mag­a­zines” as defined as highly visual, highly pro­duced timely (on the scale of weeks & months; not hours & days like the “news”) content.

    I think I’m going to give this idea a spin on my own blog. I’m try­ing to fig­ure out the best way to do that.

    It’s funny, because it seems drop­ping a CMS and “blog­ging engine” all together seems like the eas­i­est way to do what I want. Type in a text edi­tor, go and hand code some HTML, and we’re back to the clas­sic per­sonal web­site of 1999. Try­ing to get “bespoke” with a blog post is more has­sle than it’s worth with a CMS because the sys­tem is built for mod­u­lar­ity, not customization.

    Another inter­est­ing thought. When­ever dis­cussing this topic, I fre­quently hear the descrip­tion say­ing these efforts are to make “web­sites feel more designed like mag­a­zines.” That seems like a bad descrip­tion, or at least when draw­ing a com­par­i­son to mod­ern mag­a­zines. While a small seg­ment of web design­ers are try­ing to make web­sites look more like mag­a­zines, there’s a large num­ber of mag­a­zines that look more and more like web­sites. Con­tent filled up in columns, text on every page, metain­for­ma­tion over­load, and cov­ers filled with linkbait.

    I think there’s a cou­ple really won­der­ful exam­ples of edi­to­r­ial design out there right now, but very rarely does some­thing take my breath away as much as a spread from an old Harper’s Bazaar issue that Alexy Brodovich art directed, or an Esquire cover from George Lois. The main qual­ity is, yes, con­cept, but also, the design has room to breathe.

    There’s a lot of things fight­ing for space on a mag­a­zine spread, mainly adver­tis­ing ver­sus con­tent bal­ance. With the web, I think we can get away from that, and really give the idea and a design room to breathe. You’ve got as much space as you need. And that is what’s appeal­ing to me.

    Designed blog = mag? Google “mag search” to give a head start to bespoke content?

    (Full dis­clo­sure: I set­tled for the URL http://pictoryMAG.com. That said, I don’t think its a bad term for an online mag­a­zine or designed blog. How often do you call a print mag­a­zine a “mag”?)

    I like “mag” bet­ter than “zine.” When zines were ragged lit­tle pho­to­copied bun­dles passed hand to hand, or dis­cov­ered in comic book shops in lower Man­hat­tan, say, the name seemed apt. But call­ing a Web site a zine always seemed overly coy, to me. “Mag” sounds off­hand, an antithe­sis to coy (maybe because it rhymes with “rag”), and so to apply it to an online com­pi­la­tion, a gath­er­ing of con­tent, seems unpretentious.

    Back in the 1990s we had Feed (feedmag.com), an early project from Steve John­son. I always liked that URL because it evoked a feed­bag, and a horse con­tent­edly munch­ing — which it like what I do with a good magazine. 

    Pic­tory is a beau­ti­ful mag, by the way.

    Wilson Miner says:

    Tan­gen­tial, unfin­ished thought: Using an RSS reader still feels like turn­ing on a shower with the plumb­ing exposed in an unfin­ished base­ment. I want to see the next level, where the plumb­ing is just plumb­ing and the expe­ri­ence isn’t such a lit­eral trans­la­tion of the machinery.

    I like the idea of nam­ing it, Laura. It’s like a les­son from the Old Tes­ta­ment: nam­ing some­thing gives you power over it.

    A few addi­tional thoughts: If you hand-code your page, you don’t have an RSS feed. I’m not sure what my fix­a­tion is with ditch­ing RSS, but I think intro­duc­ing a bit of fric­tion (hav­ing the user have to actively go out and fetch the con­tent), and pro­vid­ing a sat­is­fy­ing reward feels like it kind of flies in the face of how we per­ceive we should con­sume the web today. You might have less eyes on your work, but not all eyes are cre­ated equal, right?

    The truth is, since almost all of our con­tent comes to us instead of the other way around, we have less invested, and we absorb con­tent at a cur­sory level. There’s really very lit­tle inter­ac­tion hap­pen­ing on the inter­net now. (At least, between the vis­i­tor and the web­site itself.) It’s mostly just com­ment boxes. (I get the irony.) Remem­ber the Don­nie Darko web­site by hi-res? Peo­ple were dig­ging into that. Sure, the nov­elty of flash and of how to use the web has waned, but I lament the loss of peo­ple being con­sumed by what they were doing. It was par­tic­i­pa­tory. Also, it was narrative.

    I’m also get­ting more and more drawn to projects on the inter­net that have a “done” state. Mean­ing, if I’m mak­ing it, I can have a log­i­cal place to fin­ish. If i’m con­sum­ing it, I get the sat­is­fac­tion of fin­ish­ing. That doesn’t hap­pen often on the web. We don’t get to kick back often enough to cel­e­brate a job well done.

    Edi­to­r­ial shouldn’t be “passed through” design, though. 

    The best design is always baked in, part of the fun­da­men­tal recipe. Peo­ple who think of design as the last phase or some­thing added to an oth­er­wise autonomous “prod­uct” miss the essen­tial point.

    Apple gets this bet­ter than any­body. They don’t apply design to their prod­ucts. Their prod­ucts are designed.

    (I wish “Objec­ti­fied” had done a bet­ter job artic­u­lat­ing this in talk­ing with Jonathan Ives. I think it’s one of the paces edi­tors and writ­ers most often fail.)

    Matt Penniman says:

    Maybe Google *does* index design. Isn’t PageR­ank sort of a proxy for design? Or at least intended par­tially as such? Great design attracts atten­tion, which online means links. The whole point of PageR­ank is to out­source “qual­ity” judg­ments — like design — to human brains.

    SJ says:

    If you think rss should be full of design cruft, then you really don’t under­stand rss.

    How exactly is bespoke design sup­posed to trans­late into the mil­lion dif­fer­ent out­puts of an rss feed? Given that the con­tent would be designed for view­ing in a browser, why not just direct peo­ple to the ideal place to view the design ele­ments if they want to see them, rather than booching up rss? Your mag­i­cal scrap­book sounds just like the web we already have.

    Robin Sloan says:

    Although an RSS feed has a mil­lion dif­fer­ent ouputs in the­ory, *in prac­tice* the Snark­mar­ket RSS feed (for exam­ple) has pri­mar­ily one out­put: Google Reader. (We know this from Feed­burner stats.)

    So I’m think­ing about that real­ity, and try­ing to respond to the real use case: There’s a desire to aggre­gate with­out homog­e­niz­ing. There’s no for­mat or tool that allows you to do that today. You’re right that a plain-vanilla web browser is prob­a­bly the clos­est thing! But it doesn’t really do what I want — yet.

    Quick quan­ti­ta­tive remark: I launched Pic­tory last month with­out an RSS and had many peo­ple ask for one. I now have a “tease” RSS and the fol­low­ing stats:

    1,300 feed­burner sub­scribers
    2,600 email newslet­ter sub­scribers
    3,500 twit­ter followers

    Matt Saler says:

    The webprint ver­sion of Radiolab’s mini-piece from Morn­ing Edi­tion today does this in a mild way. Would expect it from Krul­wich and Abum­rad, as they do it aurally in their shows.

    I hope some­one from Gawker is lis­ten­ing, Robin. Great idea and a pretty clear-cut way to make already-great blogs like Life­hacker and io9 better.

    sj says:

    My apolo­gies for my last com­ment sound­ing so angry.

    I think my prob­lem is this: not every­one using the inter­net is com­ing from the same place of priv­elege with regard to band­width, data, and hardware.

    For some, plain vanilla rss actu­ally affords them access that would oth­er­wise be out of reach. So when oth­ers want to mod­ify that tech­nol­ogy to serve them­selves and their own for­tu­nate posi­tion it really rankles.

    So, Google Reader, desk­top or mobile? Images on or off?

    Tiara says:

    +1*infinity to this com­ment. Not every­one has super­fast broad­band, and even those that do may not care for fancy design. There’s already things like Styl­ish if you want a dif­fer­ent visual for your web­sites (my Facebook’s in pur­ple and black).

    John Holdun says:

    To those argu­ing against this idea because it will get in the way: good design doesn’t always mean resource inten­sity. Look at the arti­cles on Drawar:

    http://www.drawar.com/articles

    Many of them have dis­tinct lay­outs, but none (as I recall) have any dec­o­ra­tive images whatsoever—that is, what you’re see­ing is exactly what would show up in your RSS reader. But it’s all laid out quite thought­fully in a way that aids the read­ing expe­ri­ence with­out becom­ing a nuisance.

    Robin Sloan says:

    Very cool example—I hadn’t seen Drawar. Thanks!

    Bill says:

    It’s espe­cially nice when peo­ple who don’t spe­cial­ize in the web are giv­ing their web con­tent the atten­tion to detail it deserves:

    http://theskateboardmag.com/articles/contenders-andrew-elliot/
    http://theskateboardmag.com/articles/contenders-nolan-johnson/

    Ninety Nine says:

    Um, isn’t there an essen­tial con­tra­dic­tion in the phrase “bespoke design every day?”

    Robin Sloan says:

    I don’t think so. When I say “bespoke design” I mean “design that is spe­cific to the con­tent it presents.” And I’m mostly talk­ing about graphic design, lay­out & typog­ra­phy (vs. inter­face design or over­all infor­ma­tion architecture).

    So, some news­pa­pers pro­duce this sort of design every day; so do many TV shows (via motion graphics).

    Ninety Nine says:

    Sorry for the late reply — no doubt I see your point about bespoke. And if we use the anal­ogy of say, suit mak­ing, I can promise you Gawker is pay­ing rates that might get you Men’s Ware­house qual­ity design, rather than Sav­ille Row. And that is not chang­ing any­time soon.

    Won­der­ful arti­cle, Robin. Have you seen the iPhone app from McSweeney’s? It is dis­tinctly designed — for small-screen reading.

    http://iphone.mcsweeneys.net/

    It’s one of the nicest things on my iPhone.

    […] Bespoke design meets video game the­ory in More Rock, Less Talk, a col­lab­o­ra­tion between Bran­don Boyer and Super Broth­ers. Love it. […]

The Snarkmatrix awaits your reply