Many designers still think in px first when creating baseline styles. But we know intellectually that various relative typography approaches are better suited to our medium in all its complexity. Better for accessibility. Better for avoiding bizarre typographic disasters linked to user preference settings, device limitations, and the unforeseen ways our overwrought styles can interact with one another.
As I contemplate a long-overdue redesign of my own site, it’s worth taking a refreshing dip into what we’ve learned about web typography over the past 20+ years. From the pages of (where else?) A List Apart:
Bojan Mihelac: “Power to the People: Relative Font Sizes” (2004)
An early and simple creative solution for text resizing that respects users’ choices and also gives them an additional option for resizing despite the limitations of some of the most popular browsers of the day. Presented for its historical importance, and not as a how-to for today. https://alistapart.com/article/relafont/
Lawrence Carvalho & Christian Heilmann: “Text-Resize Detection” (2006)
Detect your visitors’ initial font size setting, and find out when they increase or decrease the font size. With this knowledge, you can create a set of stylesheets that adapt your pages to the users’ chosen font sizes, preventing overlapping elements and other usability and design disasters. Presented for its historical importance as an insight into the complex dancing we’ve done in the past to ensure readability. https://alistapart.com/article/fontresizing/
Richard Rutter: “How to Size Text in CSS“ (2007)
Sizing text and line-height in ems, with a percentage specified on the body (and an optional caveat for Safari 2), provides accurate, resizable text across all browsers in common use today. An early move toward more responsive type and away from the accessibility problems created by setting text sizes in px in some browsers and devices. https://alistapart.com/article/howtosizetextincss/
Wilson Miner: Setting Type on the Web to a Baseline Grid
The main principle of the baseline grid is that the bottom of every line of text (the baseline) falls on a vertical grid set in even increments all the way down the page. The magical end result is that all the text on your page lines up across all the columns, creating a harmonious vertical rhythm. https://alistapart.com/article/settingtypeontheweb/
“We must now practice a universal typography that strives to work for everyone. To start, we need to acknowledge that typography is multidimensional, relative to each reader, and unequivocally optional.” https://alistapart.com/article/flexible-typesetting/
Keep going…
For more web design community wisdom and web typography history, see Typography & Web Fonts in A List Apart, for people who make websites.
And in the Comments below, please share your favorite resources for creating websites that look great and read beautifully, no matter what technical and human capabilities get thrown at them.
Just as nobody who marries spends their wedding day planning their divorce, almost nobody starts a business contemplating what rocks it will eventually splinter and break upon, and how to build a life raft for themselves.
I take that back. Some folks I know, who played pivotal roles in the evolution of the web, actually started their businesses with a clear goal of selling them to somebody bigger. Like Typekit was designed to sell to Adobe. Or Blogger was designed to sell to Google.
Such folks, several of whom are now post-economy wealthy, lived in the Bay Area in the 1990s and early 2000s, where building to flip was widely discussed and accepted.
Meanwhile, in NYC…
I, on the other hand, live in New York. So I started my web businesses (like Happy Cog™ design studio) to serve clients, as NYC creatives have always done, and with no understanding that I would one day need to leave the company and should have an exit plan. Why would I exit? Why would I ever stop doing work that brought excitement and meaning to my life?
Similarly, I started my personal site with its “Ask Dr. Web” tutorials in 1995, and co-founded my web design publication, A List Apart, in 1997, for the sheer joy of sharing knowledge, with no concept of making money, let alone of one day selling the business.
Eventually, despite my naivete, and mostly thanks to Jim Coudal and Jason Fried, A List Apart began making money by running one carefully screened ad per page. I used that money, as you will expect, to pay our writers, editors, and producers. And when it came time to stop running ads, I slowed our publication schedule, paid writers out of my own pocket, and worked with a small crew of fellow volunteers, who published ALA because we believed in the mission. (Still do.)
If I had come of business age in San Francisco, I likely would have sold A List Apart to somebody like O’Reilly, but that was never my plan because I make toys to play with, not to give away.
We published HTML5 For Web Designers the day after Steve Jobs, waving an iPhone on the world’s biggest stage (okay, sitting at his desk), announced that Flash was dead because HTML5 would bring app-like dynamism to the web using open standards instead of proprietary code. It (our first book, I mean) sold brilliantly. “Gee, publishing isn’t that hard” I naively told myself. (No, I knew it was hard. My favorite publishers had been laying off my favorite editors for ten years before my partners and I took the plunge. But the early success did make me think the books we published about web design would always find a large, eager audience. In time, I would learn otherwise.)
And while we began the publishing house by relying on the best writers we knew personally to write about the topics they were most passionate about, I’m proud to say that, as we went along, we also discovered brilliant first-time book authors, helping them create perfectly polished, fluff-free manuscripts that made genuine contributions to our readers’ understanding of UX and all it entails. (And not just to our readers. The insights they brought to their work after digesting our books rubbed off on their colleagues.)
In giving these brilliant writers a platform, we not only helped them take their careers to the next level, we also helped people who create web content think and work better, which in turn helped the people who used the websites, applications, and products our readers designed and built. Of that, I am proud.
Stay hungry
An Event Apart (RIP) was also a damned fine early success. Web designers liked our innovation of a multi-day, single-track conference, with a holistic approach to web design, code, and content, and unifying themes between the individual talks. Our freaking-amazing speakers debuted Huge Ideas including Mobile First and Responsive Web Design—ideas which, like perfect contextual menus in UX, arrived at the very moment designers needed them.
Not only that, but these humble geniuses also sat in the auditorium with our audience for all three days of each conference event: listening to each other’s presentations, and updating their own presentations to better bounce off each other’s ideas and the evolving themes of that particular show.
I could spend hours telling you how our producer Toby M. made miracles happen at every show, or how person-in-charge Marci E. brought joy to our community. How many of our speakers became authors. How some “graduated” from An Event Apart as newcomers replaced them. How the diversity of our speaking line-up, which wasn’t terrific in 2008, improved greatly each year. (Not that we ever said, “We need another black speaker” or “We need a trans speaker” or what-have-you. Just that we learned to swim outside the pool we came from, and discover great talent everywhere.) Our speakers were also almost uniformly Just Nice Good People, which doesn’t always happen when you’re collecting the greatest minds in an industry.
That’s not even to mention the incredible people who attended our shows, some of whom became lifetime friends for me.
So why, given the joy these businesses brought to everyone connected to them, including me, would my partners and I have even conceived of an exit strategy? We wanted the Good Times to roll on forever.
But of course they never do.
Things end
COVID did in An Event Apart. Some conferences survived, of course. Different priorities, different overheads, different business models. Some that survived do not pay their speakers. Others, where the conference is an adjunct to a bigger business, laid off or reassigned conference staff while the pandemic made live events impossible. Others that survived mostly rely on volunteer labor, whereas we had paid staff. They were worth their weight in platinum, and we’d have paid them more (because they were worth more) if the pandemic and six-figure hotel contracts hadn’t made continuing the show impossible. My partner and I earned nothing during the business’s last five years, and got personally stuck with a six-figure debt when the event closed. It is what it is.
Although books should be COVID-proof, multiple financial problems eventually beset our publishing house as well. For most of the run of the business, my partner and I earned nothing beyond the glow of contributing to our community’s knowledge. We paid our CEO, authors, and editors, kept nothing for ourselves, and tried, oh how we tried, to keep the business going as its revenues tanked.
Speaking only for myself, I’ve learned that I am good at starting businesses and keeping them going creatively, as long as somebody else figures out the money. I suck at that, and I’m obsessed with the notions of fairness and self-sacrifice that were drummed into me by a narcissistic family that valued me for taking on the roles they were emotionally incapable of handling—such as bringing up my baby brother in my father’s absence, which no child is equipped or should be asked to do, and yet it happens all the time. Growing up this way made me put my own self-interest last. Which is also why it never occurred to me to plan an exit. And by the time I needed to do so, the businesses were not in shape to sell.
Closing a conference is bad, but attendees can go to other conferences, and speakers can speak at other conferences; closing a conference doesn’t end a community. It sucks for the business but doesn’t strand participants.
But closing a publishing house hurts like hell, and you feel you let everybody down. I know how much our closing hurt some of our authors, and I think about that, instead of the good we achieved, when I look back.
No doubt when my partner and I write the large personal checks to cover our deceased business’s outstanding debts, we’ll be regretting the harm our closing caused, not basking in the warm glow of how many careers we changed for the better. Like the standup comedian who obsesses about the guy who’s frowning at table 3, and doesn’t hear the laughter of the rest of the crowd. We also, hopefully, won’t focus too closely on our financial wreckage. Just pay the bill, and move on.
Anyway, I hadn’t publicly addressed the endings of these businesses, so I figured it was time to do so. I’m sharing my experience only. If you ask any of the people I worked with on these projects, they might have a different story to tell. And that would be their story, and it would be every bit as valid as anything I’ve said here.
I also didn’t ask permission of my partners, speakers, or authors before sharing these thoughts. Probably I should have. But, hey. As I’ve said. I’m speaking here only for myself.
So, anyway.
Parting gift
Is it worth the risk of starting a web-related business that isn’t a venture-backed startup? I still think it is, and I applaud all who try. Heck, I might even do so myself someday. If you’re doubtful because of (((gestures at everything))), it might be worth noting that I started Happy Cog™ during the dot-com crash, when studios were closing all around me. And we launched A Book Apart during the world financial crisis of late 2008. Don’t let (((all this))) deter you from trying something bold. Let me know when you do. I’ll keep watching the skies.
P.S. Under swell third-party ownership and management, Happy Cog is still going strong. Check it out!
I’ve started a Bluesky list featuring some of the brilliant writers, designers, coders, editors, and others who’ve contributed to A List Apart “for people who make websites” from the magazine’s first dawning back in the 19(mumbles). Bluesky fans, grab the list here:
Why only *some* of the contributors? Simple. Several are, sadly, deceased. Many others are likely alive and well but not yet on Bluesky. We can’t unmake death, but we can offer the living networked comradeship and a wee increase in visibility.
So if you’re an A List Apart contributor who’s been thinking of joining Bluesky, consider this an incentive. Note: I’m not a partner in Bluesky, and have nothing to gain from inviting you, beyond the pleasure of your company—be it salty or sweet.
Once you join and have started a profile, ping me and I’ll add you to the list. (I’m zeldman.bsky.social on Bluesky.)
Soon after we launched A List Apart Magazine, we began to notice other websites reusing our content (including illustrations) without permission, and often without so much as a credit. As that violated our author’s copyrights and ours, we’d invariably reach out to the makers of those websites with brief, politely worded takedown requests.
Not every content poacher was contactable, but those we did reach almost always quickly complied with our requests. They also nearly always claimed that an “intern” or “freelancer” had grabbed the content without their knowledge or permission. Some, perhaps fearing that we might be litigious, even went so far as to tell us that they’d “fired” the imaginary intern/freelancer the instant we informed them of the issue.
We always pretended to believe them.
Why? Because letting embarrassed people save face is kind. It also helps the whole interaction go more smoothly. Besides, the amateur pillager claiming “the intern did it” today may be your colleague or friend tomorrow.
An Event Apart 2013 limited edition lunchbox; illustration by Kevin Cornell.
It’s nearly twenty years ago, now, children. Facebook had only recently burst the bounds of Harvard Yard. Twitter had just slipped the bonds of the digital underground. But web geeks like me still saw “social media” as a continuation of the older digital networks, protocols, listservs, and discussion forums we’d come up using, and not as the profound disruption that, partnered with smartphones and faster cellular networks, they would soon turn out to be.
So when world-renowned CSS genius Eric Meyer and I, his plodding Dr Watson, envisioned adding a digital discussion component to our live front-end web design conference events, our first thought had been to create a bespoke one. We had already worked with a partner to adapt a framework he’d built for another client, and were considering whether to continue along that path or forge a new one.
And then, one day, I was talking to Louis Rosenfeld—the Prometheus of information architecture and founder of Rosenfeld Media. I told Lou about the quest Eric and I were on, to enhance An Event Apart with a private social network, and shared a roadblock we’d hit. And Lou said something brilliant that day. Something that would never have occurred to me. He said: “Why not use Facebook? It already exists, and that’s where the people are.”
The habit of building
Reader, in all my previous years as a web designer, I had always built from scratch or worked with partners who did so. Perhaps, because I ran a small design agency and my mental framework was client services, the habit of building was ingrained.
After all, a chief reason clients came to us was because they needed something we could create and they could not. I had a preference for bespoke because it was designed to solve specific problems, which was (and is) the design business model as well as the justification for the profession.
Our community web design conference had a brand that tied into the brand of our community web design magazine (and soon-to-emerge community web design book publishing house). All my assumptions and biases were primed for discovery, design, development, and endless ongoing experiments and improvements.
Use something that was already out there? And not just something, but a clunky walled garden with an embarrassing origin story as a hot-or-not variant cobbled together by an angry, virginal undergraduate? The very idea set off all my self-protective alarms.
A lesson in humility
Fortunately, on that day, I allowed a strong, simple idea to penetrate my big, beautiful wall of assumptions.
Fortunately, I listened to Lou. And brought the idea to Eric, who agreed.
The story is a bit more complicated than what I’ve just shared. More voices and inputs contributed to the thinking; some development work was done, and a prototype bespoke community was rolled out for our attendees’ pleasure. But ultimately, we followed Lou’s advice, creating a Facebook group because that’s where the people were.
We also used Twitter, during its glory days (which coincided with our conference’s). And Flickr. Because those places are where the people were.
And when you think about it, if people already know how to use one platform, and have demonstrated a preference for doing so, it can be wasteful of their time (not to mention arrogant) to expect them to learn another platform, simply because that one bears your logo.
Intersecting planes of simple yet powerful ideas
Of course, there are valid reasons not to use corporate social networks. Just as there are valid reasons to only use open source or free software. Or to not eat animals. But those real issues are not the drivers of this particular story.
This particular story is about a smart friend slicing through a Gordian Knot (aka my convoluted mental model, constructed as a result of, and justification for, how I earned a living), and providing me with a life lesson whose wisdom I continue to hold close.
It’s a lesson that intersects with other moments of enlightenment, such as “Don’t tell people who they are or how they should feel; listen and believe when they tell you.” Meet people where they are. It’s a fundamental principle of good UX design. Like pave the cowpaths. Which is really the same thing. We take these ideas for granted, now.
But once, and not so long ago, there was a time. Not one brief shining moment that was known as Camelot. But a time when media was no longer one-to-many, and not yet many-to-many. A time when it was still possible for designers like me to think we knew best.
Designers can either become drivers of business within their organizations, or they can create the businesses they want to drive. We’re entering an era of design entrepreneurship, in which some designers are realizing that they’re not just a designer employed by a business; they’re creative business people whose skill set is design.
The quotation above is from a report at trends.uxdesign.cc subtitled “Enter Late-Stage UX.” It is an important thought. And if it seems like a new one to designers in their first decade of work, it will feel quite familiar to to those of us who earned our merit badges during the 1990s and 2000s. See, for instance,
by Scott Kramer (2000, one of four terrific ALA articles by Scott on that subject).
That widespread, intoxicating entrepreneurial impulse led to a cornucopiaofinternetcontent and products (and, eventually, “real-world”products, too). Some flopped. Some flowered for a magical season (or twelve), and then faded as times and the market changed. Some grew and grew, growing communities with them. A few changed the world, for better or worse. (And, occasionally, for both.)
History repeats, but it also changes. If flying from your corporate perch feels like your best response to an industry where the idealism that led you to UX feels somewhat beside the point, go for it! —But first, check your bank balance, and talk with family, friends, and a business advisor, if you have one.
Trusting my ability to use design and words to say something original enabled me to work for myself (and with partners) from 1999–2019, and it was good. Financially, running independent businesses is a perpetual rollercoaster, and it can crush your soul if your beloved creation fails to connect with a community. Some people exit rich. Others just exit. “Don’t burn any bridges” is a cliché that exists for a reason. But I digress.
“Consider entrepreneurship” is but one piece of useful advice in this year’s excellent State of UX report by Fabricio Teixeira and Caio Braga, with deeply clever illustrations by Fabio Benê and significant contributions from Emily Curtin (God bless the editors!) and Laura Vandiver.
I invite you to read and bookmark the whole thing. I plan to reread it several times myself over the next weeks. It’s that deep, and that good. Hat tip to my colleague Jill Quek for sharing it.
Who will design the next generation of readable, writerly web layouts?
Layouts for sites that are mostly writing. Designed by people who love writing. Where text can be engaging even if it isn’t offset by art or photography. Where text is the point.
With well considered flexible typesetting, modular scaling, and readablemeasures across a full range of proportions and devices. With optional small details that make reading screens of text a pleasure instead of a chore. With type sizes that are easy to read without needing to zoom in. And with a range of interesting sans and serif fonts (including variable fonts) that support reading and encourage creative exploration where headlines are concerned.
So what comes next? For writers, one hopes that what’s next is a fresh crop of small, innovative advancements. Improvements that are felt by readers, even when they aren’t always consciously noticed. Layouts that are not merely legible, but actually feel inevitable, at all sizes and in all contexts.
Beyond outside the box
Services like Typetura may point the way. A marriage of type and tech, Typetura is different from other typesetting methods. An intrinsic typography technology, it “enables you to design with more flexibility, while dramatically reducing code.” Disclaimer: I’m friends with, and have long admired the work of, Typetura founder Scott Kellum. Designing With Web Standards readers will recognize his name from the Kellum Image Replacement days of the early 2000s, but that ain’t the half of what he has done for web design, e.g. inventing dynamic typographic systems, high impact ad formats, new parallax techniques, and fluid typesetting technology. Scott was also the coder, along with Filipe Fortes, of Roger Black’s late, lamented Treesaver technology. But I digress.
The tech is not the point—except in so far as it improves our ability to think beyond our current understanding of what design and layout means. Just as Gutenberg’s printing press was not the point, but it was the point of departure. Initially, the invention of movable type reproduced the writing we already knew (i.e. the King James Bible). But ultimately, by freeing writing and reading from narrow elite circles and bringing it to more (and more diverse) minds, Gutenberg’s invention transformed what writing was and could be—from the invention of newspapers to the fiction of Virginia Woolf to multimedia experiences, and perhaps even to the web.
Let us all to play with Jen Simmons’s intrinsic web layout ideas and Scott Kellum and partners’s Typetura. While we also sketchin pencil and spend time looking at well designed books —printed, bound ones as well as digital publications in various devices. And specifically, not just fabulous coffee table books, but books that you’ve reread over and over, to understand what, beyond the text itself, encourages that reading response. So that, together, we may take the experiences of both reading and writing to the next level.
Appendix: Resources
If you’re new to the interplay between design and code on the open web, or if you just want a refresher, here are some evergreen links for your further learning and pleasure:
A wireless coverage map of Waushara County, Wisconsin. The tan areas of the map indicate downlink speeds between 3 and 9.99 Mbps. Red areas are even slower, while the pale and dark blue areas are faster.
Jeremy Wagner’s “Now THAT’S What I Call Service Worker!” provides innovative techniques to harness the power of Progressive Web Apps with smaller HTML payloads and better performance for repeat visitors.
“IN AN INDUSTRY that extols innovation over customer satisfaction, and prefers algorithm to human judgement (forgetting that every algorithm has human bias in its DNA), perhaps it should not surprise us that toolchains have replaced know-how.”
Our addiction to complicated toolchains and overbuilt frameworks is out of control. Web-making has lately become something of a dick-measuring competition. It needn’t stay that way.
If we wish to get back to the business of quietly improving people’s lives one thoughtful interaction at a time, we must rid ourselves of the cult of the complex. For more about why and how, see my new article, “The Cult of the Complex,” in A List Apart, for people who make websites.
JOIN An Event Apart’s Eric Meyer on a journey through the inner workings of CSS Grid as he tests various techniques to build a tic-tac-toe board filled with content. Hearkening back to the early days of CSS and A List Apart, these playful hacks rekindle a spirit of experimentation.
ABOUT A YEAR ago, around the time I launched my new design studio, I moved nearly all business-related communications to Basecamp 3, the latest evolution of the web-based project and communications management tool from my Chicago designer friends who used to be called 37signals.
One of Basecamp 3’s nicest features is the ability to set up automatic check-ins, such as asking all team members “What did you work on today?” at 5:00 pm daily.
On the surface, it’s intended as a way of letting everyone know what their teammates are working on, thereby deleting needless meetings from everyone’s schedules. But the feature can go much deeper, as I’ve discovered to my great pleasure. A day at a time, it can build community and help you design your career and your life. It even brings back some of the joy we once derived from the days of the personal web.
What did you work on today?
Over the years, I’ve started or cofounded several web-related businesses. Rather than limit my new studio.zeldman Basecamp exclusively to the designers, developers, and UX specialists who make up my studio, I decided to include everyone from allthebusinessesI touch.
Naturally, I’m mindful of people’s bandwidth, so anyone who doesn’t wish to participate can opt out or selectively block threads or projects that don’t interest them. I also refrained from inviting two staffers from one of my businesses who, for whatever reason, have just never hit it off with Basecamp. (Evangelizing any tool, however much one personally loves it, is like trying to convince a carnivore to go vegan. It accomplishes nothing, and leaves everyone feeling hurt.)
Save those two folks, with whom I collaborate through other methods, everyone else I work with on a daily or weekly basis, across all my little businesses, has access to a shared Basecamp. And every day at 5:00 pm Eastern Time, Basecamp asks all of us, “What did you work on today?”
The evolution of open sharing
At first, those who chose to participate took the question literally, sharing the work-related tasks we’d accomplished that day. But, over time, we began something sharing else. We began sharing our lives.
As if in a Unitarian church group, or an AA meeting, we share daily joys and sorrows, hopes and aspirations. One of us has a child leaving the nest; another’s child may have had a tough day at school. One of us is writing a book, another has begun physical therapy. Some of us comment on each other’s shares; others use Basecamp’s “applause” feature to indicate that we read and appreciated what was shared. Some folks write essays; others share via bulleted lists.
Hearkening back to the old, personal web
Sharing and reading other people’s posts has become a highlight of my day. Of course it helps me get my work done, but more importantly, it also lets me focus on my life and professional goals—and those of my friends. I love getting to know people this way, and I deeply appreciate how respectful and safe our sharing space feels—partly because Basecamp designed the space well, and partly because I work with people who are not only talented and bright, but also kind and empathetic.
If we all sat together in the same office space, I doubt we would let down our guard as much as we do when responding to Basecamp’s automatic check-in. Indeed, far less personal sharing goes on with the non-remote colleagues in my NYC studio space—probably because we are all there to work.
It reminds me of what life was once like on the old web, where people shared honestly on their personal sites without fear of being harassed. I’m not the only old-timer who misses that old web; in recent years, several of my internet friends who once blogged blithely have switched to opt-in newsletters, sharing only with subscribers. Although I mourn the personal, open-hearted web we once shared, I understand this impulse all too well. Sharing with my colleague/friends on Basecamp restores some of the joy I used to take from sharing and listening on the old open web. You might try it.
DESIGN is a balancing act—and never more so than when it comes to accessibility (AKA #a11y). So what can you do when an a11y solution you’ve devised for one group creates a fresh a11y dilemma for another?
Through the prism of typeface choice, Eleanor Ratliff relates how she and her team tackled the problem of accessibility whack-a-mole for a rebranding project. In today’s edition of A List Apart, for people who make websites.
I SPENT yesterday with my Swedish friend Pär (“Peyo”) Almqvist, who returned from LA Sunday morning and headed home to Sweden Sunday night. We met in Stockholm in 1999, when Peyo was 19, and have been close ever since. In 2000, Peyo wrote “Fragments of Time” for A List Apart. Reading it, you can see how thoughtful he is as a creative person.
A few years ago, Peyo cofounded OMC Power, a start-up that brought affordable solar power to rural villages in India—profoundly poor villages where, until that time, folks had relied on dirty gasoline-powered generators to get what little electricity they could.
National Geographic TV covered OMC’s work just this week in their special, “Years of Living Dangerously;” in the video clip on their site, you can watch David Letterman interview one of Peyo’s co-founders about what they’ve accomplished so far, and why it matters.
Letterman went to India to cover the threat of climate change and what’s being done to fight it. OMC Power is providing clean energy and a model for India to electrify itself without adding to the pollution that contributes to climate change. OMC started in India because folks in India needed the power and therefore welcomed them; and also because, by working with small rural villages, they encountered less violent opposition from the oil companies than they would have if they had attempted the experiment in Europe or North America. When the power grid fails in the west, folks in India will still have power—an irony of developed nations’ dependence on dirty fossil fuels.
In a time when so many of us feel helpless about climate change, and others, at the behest of corporate masters, cynically deny that it exists, it is good to know people who are making a difference and earning a living in doing so.
While Peyo remains an advisor to OMC Power, he has since co-founded a music startup, which I can’t talk about yet, but which I believe will meet real a need in music and may even change how some music gets made. (Like me, Peyo has a musical background, although, unlike me, as a producer and composer he has had hits in Sweden.)
It was his new music start-up music business that brought Peyo to New York and LA during the past week. I missed the chance to spend the week with him as I was in San Francisco doing the final AEA conference of 2016. It was great to spend a day together in New York, talking about our families, our businesses, and the world.
2006 DOESN’T seem forever ago until I remember that we were tracking IE7 bugs, worrying about the RSS feed validator, and viewing Drupal as an accessibility-and-web-standards-positive platform, at the time. Pundits were claiming bad design was good for the web (just as some still do). Joe Clark was critiquing WCAG 2. “An Inconvenient Truth” was playing in theaters, and many folks were surprised to learn that climate change was a thing.
I was writing the second edition of Designing With Web Standards. My daughter, who is about to turn twelve, was about to turn two. My dad suffered a heart attack. (Relax! Ten years later, he is still around and healthy.) A List Apart had just added a job board. “The revolution will be salaried,” we trumpeted.
Preparing for An Event Apart Atlanta, An Event Apart NYC, and An Event Apart Chicago (sponsored by Jewelboxing! RIP) consumed much of my time and energy. Attendees told us these were good shows, and they were, but you would not recognize them as AEA events today—they were much more homespun. “Hey, kids, let’s put on a show!” we used to joke. “My mom will sew the costumes and my dad will build the sets.” (It’s a quotation from a 1940s Andy Hardy movie, not a reflection of our personal views about gender roles.)
Jim Coudal, Jason Fried and I had just launched The Deck, an experiment in unobtrusive, discreet web advertising. Over the next ten years, the ad industry pointedly ignored our experiment, in favor of user tracking, popups, and other anti-patterns. Not entirely coincidentally, my studio had just redesigned the website of Advertising Age, the leading journal of the advertising profession.
Other sites we designed that year included Dictionary.com and Gnu Foods. We also worked on Ma.gnolia, a social bookmarking tool with well-thought-out features like Saved Copies (so you never lost a web page, even if it moved or went offline), Bookmark Ratings, Bookmark Privacy, and Groups. We designed the product for our client and developed many of its features. Rest in peace.
I was reading Adam Greenfield’s Everyware: The Dawning Age of Ubiquitous Computing, a delightfully written text that anticipated and suggested design rules and thinking for our present Internet of Things. It’s a fine book, and one I helped Adam bring to a good publisher. (Clearly, I was itching to break into publishing myself, which I would do with two partners a year or two afterwards.)
In short, it was a year like any other on this wonderful web of ours—full of sound and fury, true, but also rife with innovation and delight.
As part of An Event Apart’s A Decade Apart celebration—commemorating our first ten years as a design and development conference—we asked people we know and love what they were doing professionally ten years ago, in 2006. If you missed parts one, two, three, or four, have a look back.
I SPENT yesterday with my Swedish friend