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!
Blue Beanie Day is everywhere! Here astronaut Bowman from 2001: A Space Oddysey flaunts his basic blue toque, couresty of Kevin Cornell (illustration) and Douglas Vos (inventor of the holiday).
Saturday, 30 November 2024, marks the 17th annual Blue Beanie Day celebration. It’s hard to believe, but web standards fan Douglas Vos conceived of this holiday way back in ’07:
The origin of the name of the holiday is the image of Jeffrey Zeldman on the cover of his book wearing a blue knit cap.[7][8][9] Over the years, the Blue Beanie Day also became an action day for web accessibility, for which the correct use of web standards is a basic requirement.[8] — Wikipedia
How can you join this year’s fun? That’s easy! Snap a self-portrait wearing a blue beanie and post your Blue Beanie Day photo to Bluesky, Threads, Instagram, Tumblr, LinkedIn, Facebook, your blog (you’ve still got one, right?), and whatevs. Hashtag: #BlueBeanieDay.
Red, black, and white. Always a good look. Screenshot of The Line website.
If you’re finding today a bit stressful for some reason, grab a respite by sinking into any of these web design inspiration websites.
Gathered from conversations on Reddit and elsewhere, each site offers a collection of other sites’ designs, chosen for impact, originality, and innovation. Each collection should offer at least a few designs that will inspire your own ideas and creativity—and most contain more than a few. Lots more.
We make no claims as to usability, accessibility, or appropriateness of design. Which doesn’t mean that the chosen websites are unusable, inaccessible, or inappropriate to the brand, subject matter, or needs of the audience. Indeed, from the care devoted to the graphical interface, we assume that many of these sites are as good under the hood as they are on the surface. But it’s just an assumption; we haven’t tested, and the point of this post is purely to share visual and creative inspiration. Enjoy!
Baby Yoda pixel illustration by Justin Dauer aka @pseudoroom, icon art O.G.
Sure, watches that tell you when you’re walking unsteadily and pocket computer phones that show you the closest pizzeria are swell, but were you around for ResEdit? That humble yet supremely capable Macintosh resource editing tool is what we used to design pixel art back in the day. (And what day was that? Come August, it will be 30 years since the final release of ResEdit 2.1.3.) Stroll with us down memory lane as we celebrate the pearl anniversary of pixel art creation’s primary progenitor, and some of the many artists and design languages it inspired. Extra credit: When you finish your stroll, consider posting a Comment sharing your appreciation for this nearly forgotten art form and/or sharing links to additional pixel art icon treasures missing from our list below.
The Dead Pixel Society (2014) and founders: “We honor the humble pixel with icon creations designed under 90’s era MacOS constraints: 256 colors, pixel-by-pixel, on a 32 x 32 canvas.”
So, I’m a web designer. And I also specialise in accessibility, design systems, and design.
…Why do I think that this is the best title? Here’s why.
I’m designing for the web. The infinitely flexible web. The web that doesn’t have one screen size, one browser, one operating system, or one device. The web that can be used by anyone, anywhere, on any internet connection, on any device, on any operating system, on any browser, with any screen size. I’m designing with the web. Using the web platform (HTML, CSS, JS, ARIA, etc.), not a bloated harmful abstraction. I have a deep understanding of HTML and its semantics. I love CSS, I know how and when to utilise its many features, and I keep up-to-date as more are added. I have a strong understanding of modern JavaScript and most importantly I know when not to use it.
The Wax and the Wane of the Web (2024): Forget death and taxes. The only certainty on the web is change. Ste Grainer takes a brief look at the history of the web and how it has been constantly reinvented. Then he explores where we are now, and how we can shape the future of the web for the better. – A List Apart
The Cult of the Complex (2018): 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. Admitting the problem is the first step in solving it. – A List Apart
Dear AIGA, where are the web designers? (2007): For all the brand directors, creative directors, Jungian analysts, and print designers, one rather significant specimen of the profession is missing. – zeldman.com
Standardization and the Open Web (2015): How do web standards become, well, standard? Although they’re often formalized through official standards-making organizations, they can also emerge through popular practice among the developer community. If both sides don’t work together, we risk delaying implementation, stifling creativity, and losing ground to politics and paralysis. Jory Burson sheds light on the historical underpinnings of web standardization processes—and what that means for the future of the open web. – A List Apart
Screenshot of slide highlighting the four phases of WordPress Gutenberg.
Not only are we enabling folks to express themselves uniquely on the web, unlike the cookie cutter looks that all the social sites try to put you into. We’re doing it in a way which is standards-based, interoperable, based on open source, and increases the amount of freedom on the web.
Mike Essl and I discuss his portfolio on Night 2 of An Event Apart Online Together Fall Summit.
Herewith, a scene from last night’s interview with legendary web & book designer (and Dean of The Cooper Union School of Art) Mike Essl, who shared his portfolio, career highlights, early web design history, and more. Fun!
If you get a chance to meet, work with, or learn from Mike, take it. He’s brilliant, hilarious, warmly human, and one of the most creative people you’ll ever have the good fortune to know.
Pulling the trigger just got easier. Now anyone can have a beautifully designed, standards-compliant WordPress site. The 60-plus recently created free WordPress themes (AKA template collections) listed by InstantShift’s Daniel Adams are categorized by function and style: “Clean and Minimal,” “Artistic and Fancy,” “Magazine Style,” “Portfolio Style,” “News and Social Media Style,” “Showcase and Galleries Style,” “E-Comerce and Shopping Cart Style,” “Domain Parking/Coming Soon Style,” and “Other.” Something for everyone.
Not everything here is a winner or will appeal to every taste, but there is plenty of great work to be had here. If WordPress is your CMS (it’s mine), even if you are a designer, you may ask yourself if you really need to perform that next site redesign from scratch.
An Event Apart Chicago has sold out. If you wanted to join us in Chicago on October 12–13 for two days of design, code, and content, we’re sorry to announce that the show has completely sold out. There’s not a spare seat to be had.
That means, if you don’t already have a ticket, you won’t be able to watch Jason Santa Maria, Kristina Halvorson, Dan Brown, Whitney Hess, Andy Clarke, Aaron Gustafson, Simon Willison, Luke Wroblewski, Dan Rubin, Dan Cederholm, and your hosts Eric Meyer and Jeffrey Zeldman share the latest ideas in design, development, usability, and content strategy.
We’re sorry about that.
But, hey. If you can’t be with us in Chicago next week, please join us in San Francisco later this year. Or come see us in 2010 at any of these fine cities:
Join Tantek Celik Wednesday 12 August at the first-ever microformats workshop to be held in New York City. An Event Apart fans get 40% off the advance price of $195 (regular $375) with discount code aea40 when you order by midnight tonight.
In the past year, microformats support has been launched and built into products and services by Google, Microsoft, Yahoo, Yelp and numerous other companies, as well as nearly every new social network website.
Taught by industry leader Tantek Çelik, the workshop will cover just about everything you need to know to get started with microformats.
In half a day you will learn how to add key well-established microformats to your website to benefit your users, help your website’s findability in search engines, and provide a standards based API for web developers.
You will learn not just the theory of microformats; you’ll also get down and dirty with some hands-on markup:
What are microformats? Get a good grounding in the kind of problems microformats are designed to solve… and find out where the limits of microformats are (by design).
Foundations for microformats. it’s important to understand the value of meaningful markup before implementing microformats. This will get you thinking about how you should be marking up your content using plain ol’ semantic HTML before adding any microformat enhancements.
Incremental building blocks. From simple elemental microformats that consist of nothing more than adding an attribute, right up to compound microformats that can be mashed up together, you’ll meet them all.
Smell the microformats. Just as you can develop a nose for wine tasting, you can also develop a sense for spotting which content is just crying out to be microformatted. Once you’ve learned to see these patterns, you’ll never surf the web the same way again.
Add microformats to your sites. Using a combination of exercises, this workshop will teach you to how to spice up your content with semantic goodness. If you’re up to the challenge and bring your laptop, by the end of the workshop you’ll have added microformats to your site in HTML4, XHTML, or HTML5.
Powerful user experience enhancements. Add powerful one-click contact info download and event subscription functionality for your users to easily add your site to their address books and calendars.
Search Engine Optimization (SEO). With both Google and Yahoo now indexing microformats and using them in search results, it’s critical to make sure your site properly marks up contacts, events, and reviews with microformats for search engines to discover, index, and display better results to users.
In Issue No. 289 of A List Apart, for people who make websites: 90% of web design is redesign. The hardest redesigns are the ones you do for yourself. In this special issue, we look at how two of the great ones handled the challenge of redesigning their own sites.
In a mere two years, Erskine Design grew from two people working at home into a full-fledged agency of eight, working with major clients. Their website needed to better reflect their achievements, abilities, and team strengths. They also sought to improve the quality of data collected during client inquiries. Simon Collison explores the agency’s thought processes, and the decisions they made as their own client.
Redesigning your freelance website is an exercise in masochism. There are no colleagues to share the pain: It’s just you. As the designer who wrote The Art of Self-Branding, freelancer Lea Alcantara knew her site had to be just right. People were bound to scrutinize any update to the design, and she couldn’t afford to damage her credibility. Follow her process and decide for yourself if she succeeded.
Now the right hand knows what the left hand is doing. Happy Cog™ and Airbag Industries announce the merger of our firms, effective today, August 3, 2009. The resulting super-agency will be called Happy Cog, and will maintain studios in three cities:
Happy Cog East, in Philadelphia, directed by President Greg Hoy;
Happy Cog West, in San Francisco (the newest branch), directed by President Greg Storey; and
Happy Cog Studios, the original, in New York City, directed by little old me.
From an internal perspective, this merger of people and resources, freely shared across all three agencies, means we can now bring boutique-style craftsmanship to any size job. If you’re a client, you no longer have to choose between “big enough” and “good enough” when selecting a vendor. You can hire a big agency that designs and cares like a small one.
With the mix of people now at our disposal, you can expect exciting product development as well.
Staffed up and pumped up, Happy Cog East and Happy Cog West will specialize in client services, web design, and development. Happy Cog Studios in New York, while also designing selected websites, will focus on business strategy and content development via A List Apart Magazine, An Event Apart design conference, and other ventures.
None of us knows exactly where all this is going. But we like who we’re going with—and we trust them with our lives. More than that, we trust them with our reputation.
Designed by Happy Cog and launched today, The Amanda Project is a social media network, creative writing project, interactive game, and book series combined:
The Amanda Project is the story of Amanda Valentino, told through an interactive website and book series for readers aged 13 & up. On the website, readers are invited to become a part of the story as they help the main characters search for Amanda.
The writing-focused social media network is designed and written as if by characters from the Amanda novels, and encourages readers to enter the novel’s world by joining the search for Amanda, following clues and reading passages that exist only online, and ultimately helping to shape the course of the Amanda narrative across eight novels. (The first Amanda novel—Invisible I, written by Melissa Kantor—comes out 22 September.)
The site developed over a year of intense creative collaboration between Happy Cog and Fourth Story Media, a book publisher and new media company spearheaded by publishing whiz Lisa Holton. Prior to starting Fourth Story, Lisa was was President, Scholastic Trade Publishing and Book Fairs; managed the publication of Harry Potter and the Deathly Hallows; and oversaw development of The 39 Clues. Before that she spent nearly a decade developing numerous bestselling, franchise-launching series at Disney.
Happy Cog‘s New York office developed this project. The team:
Equally vital to the project’s success were Fourth Story’s leaders and partners, including:
Lorraine Shanley, Principal Advisor
Ariel Aberg-Riger (website, Twitter), Creative Development & Marketing Manager
JillEllyn Riley, Editorial Director
Dale Robbins, Creative Director
David Stack, Director, Digital Partnerships
Melissa Kantor, Writer
Peter Silsbee, Writer
Polly Kanevsky, Art Director
Sam Gerstenzang, Technology Consultant
Today’s launch is not the end of our relationship with Fourth Story Media. The Amanda Project will continue to evolve, and Happy Cog will remain an active partner in its direction and growth. We thank our brilliant collaborators and congratulate them on today’s milestone.
Back in 2000, CSS co-creator Bert Bos set out to explain the W3C’s design principles—“to make explicit what the developers in the various W3C working groups mean when they invoke words like efficiency, maintainability, accessibility, extensibility, learnability, simplicity, [and] longevity….”
Eventually published in 2003, the essay, although ostensibly concerned with explaining W3C working group principles to the uninitiated, actually articulates the key principle that separates great design from the muck we normally wade through. It also serves as a warning to Bert’s fellow W3C wizards not to seek the dark magic of abstract purity at the expense of the common good. Tragically for these wizards, and for we who use their technologies, it is a warning some developers of W3C specifications continue to overlook.
Design is for people
In his introduction, Bert summarizes the humanistic value that is supposed to be at the core of every web standard:
Contrary to appearances, the W3C specifications are for the most part not designed for computers, but for people. … Most of the formats are in fact compromises between human-readability and computer efficiency….
But why do we want people to read them at all? Because all our specs are incomplete. Because people, usually other people than the original developers, have to add to them….
For the same reason we try to keep the specifications of reasonable size. They must describe a useful chunk of technology, but not one that is too large for an individual to understand.
Over the succeeding 25 web pages (the article is chunked out in pamphlet-sized pages, each devoted to a single principle such as “maintainability” and “robustness”) Bert clearly, plainly, and humbly articulates a series of rather profound ideas that are key to the web’s growth and that might apply equally admirably to realms of human endeavor beyond the web.
The Web now runs on HTML, HTTP and URLs, none of which existed before the ’90s. But it isn’t just because of the quality of these new formats and protocols that the Web took off. In fact, the original HTTP was a worse protocol than, e.g., Gopher or FTP in its capabilities….
And that fact shows nicely what made the Web possible at all: it didn’t try to replace things that already worked, it only added new modules, that fit in the existing infrastructure. …
And nowadays (the year 2000), it may look like everything is XML and HTTP, but that impression is only because the “old” stuff is so well integrated that you forget about it: there is no replacement for e-mail or Usenet, for JPEG or MPEG, and many other essential parts of the Web.
He then warns:
There is, unfortunately, a tendency in every standards organization, W3C not excluded, to replace everything that was created by others with things developed in-house. It is the not-invented-here syndrome, a feeling that things that were not developed “for the Web” are somehow inferior. And that “we” can do better than “them.” But even if that is true, maybe the improvement still isn’t worth spending a working group’s resources on.
Shrinkage and seduction
In his gentle way, Bert seems to be speaking directly to his W3C peers, who may not always share his and Håkon‘s humanism. For, despite what designers new to CSS, struggling for the first time with concepts like “float” and the box model may think, Bert and Håkon designed the web’s layout language to be easy to learn, teach, implement, maintain, and (eventually) extend. They also designed CSS not to overwhelm the newcomer with advanced power at the cost of profound complexity. (“CSS stops short of even more powerful features that programmers use in their programming languages: macros, variables, symbolic constants, conditionals, expressions over variables, etc. That is because these things give power-users a lot of rope, but less experienced users will unwittingly hang themselves; or, more likely, be so scared that they won’t even touch CSS. It’s a balance.”)
This striving to be understood and used by the inexperienced is the underlying principle of all good design, from the iPhone to the Eames chair. It’s what Jared Spool would call usability and you and I may consider the heart of design. When anything new is created, be it a website, a service, or a web markup language, there is a gap between what the creator knows (which is everything about how it’s supposed to work), and what you and I know (which is nothing). The goal of design is to shrink this ignorance gap while seducing us into leaping across it.
What were once vices are now habits
You can see this principle at work in CSS, whose simplicity allowed us to learn it. Although we now rail against the limitations of CSS 1 and even CSS 2.1, what we are really complaining about is the slow pace of CSS 3 and the greater slowness with which browser makers (some more than others) adopt bits of it.
Note that at one time we would have railed against browser makers who implemented parts of a specification that was still under development; now we admire them. Note, too, that it has taken well over a decade for developers to understand and browsers to support basic CSS, and it is only from the perspective of the experienced customer who craves more that advanced web designers now cry out for immediate CSS 3 adoption and chafe against the “restrictions” of current CSS as universally supported in all browsers, including IE8.
If CSS had initially offered the power, depth, and complexity that CSS 3 promises, we would still be designing with tables or Flash. Even assuming a browser had existed that could demonstrate the power of CSS 3, the complexity of the specification would have daunted everyone but Eric Meyer, had CSS 1 not come out of the gate first.
The future of the future of standards
It was the practical simplicity of CSS that enabled browser engineers to implement it and tempted designers to use (and then evangelize) it. In contrast, it was the seeming complexity and detachment from practical workaday concerns that doomed XHTML 2, while XHTML 1.0 remains a valid spec that will likely still be working when you and I have retired (assuming retirement will be possible in our lifetime—but that’s another story).
And yet, compared to some W3C specs in progress, XHTML 2 was a model of accessible, practical, down-to-earth usability.
To the extent that W3C specifications remain modular, practical, and accessible to the non-PhD in computer science, they will be adopted by browser makers and the marketplace. The farther they depart from the principles Bert articulated, the sooner they will peter out into nothingness, and the likelier we are to face a crisis in which web standards once again detach from the direction in which the web is actually moving, and the medium is given over to incompatible, proprietary technologies.
