Categories
37signals A Book Apart A List Apart Acclaim Adobe An Event Apart books Brands business Career Collectibles Community conferences content Coudal Partners Deck, the Designers E-Books editorial eric meyer Ethan Marcotte Free Advice glamorous Grief Happy Cog™ HTML5 Indieweb industry Jason Santa Maria Jeremy Keith launches Mentoring My Back Pages New York City NYC Products Publications Publisher's Note Publishing Responsibility Responsive Web Design San Francisco Small Business speaking State of the Web Surviving The Essentials The Profession This never happens to Gruber Typekit User Experience UX Wah! Web Design Web Design History Websites Wit and Wisdom Working writing zeldman.com

Of Books and Conferences Past

Some of A Book Apart’s 50-odd primary paperbacks, arranged like a color spectrum, and photographed against a piece of wood.

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.

An ecosystem apart

In spite of A List Apart’s running at a loss, in the early 2010s I co-founded two businesses that spun out of it: An Event Apart design conference with Eric Meyer, and A Book Apart with Mandy Brown (later replaced by CEO Katel LeDu) and Jason Santa Maria. And during those first years, business was great.

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!

Categories
Authoring Best practices Compatibility Content First Content-First CSS CSS3 Design Ethan Marcotte HTML HTML5 Jeremy Keith links Standards State of the Web Told you so Web Design Web Design History Web Standards

Of Patterns and Power: Web Standards Then & Now

IN “CONTENT Display Patterns” (which all front-end folk should read), Dan Mall points to a truth not unlike the one Ethan Marcotte shared last month on 24 ways. It is a truth as old as standards-based design: Construct your markup to properly support your content (not your design).

Modular/atomic design doesn’t change this truth, it just reinforces its wisdom. Flexbox and grid layout don’t change this truth, they just make it easier to do it better. HTML5 doesn’t change this truth, it just reminds us that the separation of structure from style came into existence for a reason. A reason that hasn’t changed. A reason that cannot change, because it is the core truth of the web, and is inextricably bound up with the promise of this medium.

Separating structure from style and behavior was the web standards movement’s prime revelation, and each generation of web designers discovers it anew. This separation is what makes our content as backward-compatible as it is forward-compatible (or “future-friendly,” if you prefer). It’s the key to re-use. The key to accessibility. The key to the new kinds of CMS systems we’re just beginning to dream up. It’s what makes our content as accessible to an ancient device as it will be to an unimagined future one.

Every time a leader in our field discovers, as if for the first time, the genius of this separation between style, presentation, and behavior, she is validating the brilliance of web forbears like Tim Berners-Lee, Håkon Wium Lie, and Bert Bos.

Every time a Dan or an Ethan (or a Sara or a Lea) writes a beautiful and insightful article like the two cited above, they are telling new web designers, and reminding experienced ones, that this separation of powers matters.

And they are plunging a stake into the increasingly slippery ground beneath us.

Why is it slippery? Because too many developers and designers in our amnesiac community have begun to believe and share bad ideas—ideas, like CSS isn’t needed, HTML isn’t needed, progressive enhancement is old-fashioned and unnecessary, and so on. Ideas that, if followed, will turn the web back what it was becoming in the late 1990s: a wasteland of walled gardens that said no to more people than they welcomed. Let that never be so. We have the power.

As Maimonides, were he alive today, would tell us: he who excludes a single user destroys a universe. Web standards now and forever.

Categories
Bandwidth Best practices Design Designers development DOM Ethan Marcotte HTML industry Markup Medium Off My Lawn! people Performance Responsive Web Design Standards State of the Web Tech The Essentials The Profession Usability UX Web Design Web Design History Web Standards XHTML

You’re welcome: cutting the mustard then and now.

EVERY TIME I hear a young web developer cite the BBC’s forward-thinking practice of “cutting the mustard,” by which they mean testing a receiving web device for certain capabilities before serving content, I remember when my team and I at The Web Standards Project invented that very idea. It’s a million web years ago, by which I mean fourteenish human years ago, so nobody remembers but me and some other long toothed grayhairs, plus a few readers of the first edition of Designing With Web Standards. But I like you, so I will tell you the story.

Back then in those dark times, it was common practice for web developers to create four or more versions of the same website—one for each browser then in wide use. It was also a typical (and complementary) practice to send server-side queries to figure out which browser was about to access a site’s content, and then send the person using that browser to the site version that was configured for her browser’s particular quirks, proprietary tags, and standards compliance failings.

The practice was called “browser detection.” Nobody but some accessibility advocates had ever questioned it—and the go-go dot-com era had no time or care for those folks.

But we at The Web Standards Project turned everything on its head. We said browsers should support the same standards instead of competing to invent new tags and scripting languages. We said designers, developers, and content folks should create one site that was accessible to everyone. In a world like that, you wouldn’t need browser detection, because every browser and device that could read HTML would be able to feast on the meat of your site. (And you’d have more meat to share, because you’d spend your time creating content instead of crafting multiple versions of the same site.)

To hasten that world’s arrival, in 2001 we launched a browser upgrade campaign. Those who participated (example participant here) employed our code and content to send their users the message that relatively standards-compliant browsers were available for every platform, and inviting them to try one. Because if more people used relatively standards-compliant browsers, then we could urge more designers and developers to create their sites with standards (instead of quirks). And as more designers and developers did that, they’d bump against still-unsolved standards compliance conundrums, enabling us to persuade browser makers to improve their standards compliance in those specific areas. Bit by bit, stone by stone, this edifice we could, and would, erect.

The code core of the 2001 browser upgrade campaign was the first instance of capability detection in place of browser detection. Here’s how it worked. After creating a valid web page, you’d insert this script in the head of your document or somewhere in your global JavaScript file:

if (!document.getElementById) {
window.location =
"http://www.webstandards.org/upgrade/"
}

We even provided details for various flavors of markup. In HTML 4 or XHTML 1 Transitional documents, it looked like this:

<script type="text/javascript" language="javascript">
<!-- //
if (!document.getElementById) {
window.location =
"http://www.webstandards.org/upgrade/"
}
// -->
</script>

In STRICT documents, you’d either use a global .js file, or insert this:

<script type="text/javascript">
<!-- //
if (!document.getElementById) {
window.location =
"http://www.webstandards.org/upgrade/"
}
// -->

You could also just as easily send visitors to an upgrade page on your own site:

if (!document.getElementById) {
window.location =
"http://www.yourdomain.com/yourpage.html"
}

Non-WaSP members (at the time) J. David Eisenberg, Tantek Çelik, and Jim Heid contributed technical advice and moral support to the effort. WaSP sysadmin Steven Champeon, the inventor of progressive enhancement, made it all work—under protest, bless him. (Steve correctly believed that all web content should always be available to all people and devices; therefore, in principle, he disliked the upgrade campaign, even though its double purpose was to hasten the arrival of truly standards-compliant browsers and to change front-end design and development from a disrespected world of hacks to a sustainable and professional craft. ((See what I did there? I’m still respectfully arguing with Steve in my head.)))

Discovering rudimentary DOM awareness or its absence in this fashion was the first time web developers had tested for capabilities instead of chasing the dragon in a perpetual and futile attempt to test for every possible browser flavor and version number. It was the grandparent, if you will, of today’s “cutting the mustard.” And it is analogous as well to the sensible responsive design practice of setting breakpoints for the content, instead of trying to set appropriate breakpoints for every possible device out there (including all the ones that haven’t been invented yet).

Which reminds us that the whole point of web standards was and is forward compatibility—to create content that will work not only in yesterday’s and today’s browsers and devices, but in all the wonderful devices that have yet to be invented, and for all the people of the world. You’re welcome.

—CHICAGO, Westin Chicago River Hotel, 1 September 2015


Hat tip: John Morrison

Categories
A List Apart Best practices Code Design development editorial Ethan Marcotte Future-Friendly HTML Responsibility Usability W3C Web Design Web Design History Web Standards Websites Zeldman

No Good Can Come of Bad Code: Ask Dr Web in A List Apart

Remember: the future will come whether you design for it or not. If your company charges $300,000 for a website that won’t work on next week’s most popular device, your company won’t be able to stay competitive in this business. It might not even be able to stay in the business, period. After all, clients who pay for sites that break too soon will look elsewhere next time—leaving your company perpetually hunting for new clients in a downward spiral of narrowing margins and diminishing expectations.

Your company’s survival is tied to the ability of the products it makes to work in situations you haven’t imagined, and on devices that don’t yet exist. This has alwaysbeen the challenge of web design. It’s one A List Apart has taken seriously since we began publishing, and our archives are filled with advice and ideas you can boil down and present to your bosses.

Source: No Good Can Come of Bad Code

Categories
business businessweek client management client services clients content Content First CSS3 Curation Dan Benjamin Design E-Books Ethan Marcotte findability Google Happy Cog™ HTML HTML5 Jeremy Keith Microsoft podcasts Publishing Real type on the web Redesigns Responsive Web Design Standards State of the Web The Big Web Show Usability User Experience UX Web Design Web Design History Web Standards Zeldman

Leo Laporte interviews JZ

IN EPISODE 63 of Triangulation, Leo Laporte, a gracious and knowledgeable podcaster/broadcaster straight outta Petaluma, CA, interviews Your Humble Narrator about web standards history, responsive web design, content first, the state of standards in a multi-device world, and why communists sometimes make lousy band managers.

Categories
A Book Apart A List Apart Design Ethan Marcotte Layout Responsive Web Design Web Design Web Design History Web Standards

Boston Globe’s Responsive Redesign. Discuss.

AS EVERY WEB DESIGNER not living under a rock hopefully already knows, The Boston Globe has had a responsive redesign at the hands of some of today’s best designers and developers:

The spare Globe website has a responsive design that adapts to different window sizes, browsers and devices, and it has a built-in Instapaper-type feature that saves articles for reading off various devices on the subway. The overhaul has incorporated the talents of Boston design firms Filament Group, and Upstatement, as well as a large internal team, and pre-empts the need to build separate apps for each device.—New York Observer

As the first responsive redesign of a “real” website (i.e. a large, corporately financed, widely read newspaper site rather than some designer’s blog), the site has the potential to raise public awareness of this flexible, standards-based, multi-platform and user-focused web design approach, and deepen perceptions of its legitimacy, much as Mike Davidson’s standards-based redesign of ESPN.com in 2003 helped convince nonbelievers to take a second look at designing with web standards:

In a major step in the evolution of website design, the Boston Globe relaunched their site today using a Responsive Design approach. For a consistent experience across mobile and desktop browsers, they redesigned the site to add and remove columns to the layout based on the width of your browser window.

This marks the first major, high-traffic, content-heavy website to adopt a responsive design. The lead consultant behind the project is none other than Ethan Marcotte, the designer who wrote the book on responsive design. Much as ESPN changed the way we worked by being one of the first to launch a fully CSS driven site a decade ago, the Boston Globe’s redesign has the potential to completely alter the way we approach web design.—Beaconfire Wire

More work remains to be done. Some sections of the paper have not yet converted, and some site architecture has yet to be refreshed, so it is too early to call the overhaul a complete success. But it is clear that Ethan Marcotte, author of Responsive Web Design and creator of responsive design, together with the geniuses at Filament Group, Upstatement, and the Globe’s internal design/development team have managed to work beautifully together and to solve design problems some of us don’t even know exist.

Congratulations to the Globe for its vision and these designers and developers for their brilliant work.