Category: Off My Lawn!

Categories
AI Law & Legal Off My Lawn! State of the Web

Your opt-innie wants to talk to your opt-outtie.

Photo of a legal gavel. ℅ Unsplash. Details at the end of the post.

Here’s a fact: “Opt-in” is great for programs a platform controls, but meaningless when that platform has no control.

Take, for example, oh, I don’t know, let’s say AI companies scraping web content without your permission. The heart wants to make content scraping permissions “opt-in,” so people who post content online are protected by default.

Except we won’t be. Smaller, “good” AI companies may comply with “opt-out” notices; big ones surely won’t. Scrapers gonna scrape.

So why even bother with an “opt-out” setting? Because companies that continue to scrape opted-out content may find themselves on the losing end of major lawsuits.

Of course there’s no telling how these lawsuits will work out—not with ketamine supervillains and their GOP enablers willfully violating consumer, worker, and climate protection laws here in the benighted States of America. But even so, an opt-out notice is a red line, and most corporate legal teams are cautious and sober—at least during working hours.

An opt-out notice is *something.* It smells funky, but has a chance of working.

Of course opt-in feels better. It’s how we’d do things if we had control over third-party scrapers. But we don’t have that control.

Which makes opt-in for AI scraping a feel-good but basically performative gesture. And we don’t have time for those.

However pretty it might be to think otherwise, something imperfect that might work beats something pure that won’t. Don’t hate me ’cause I’m beautiful. I’m only here to tell you what we both know in our souls.

Your AI sponsor,

z

Photo by Tingey Injury Law Firm on Unsplash.

Categories
glamorous New York City NYC Off My Lawn!

My Glamorous Life: The Unexpected Samples

Beneath a mad blue sky, a horse whinnies in terror. Photo by Mikael Kristenson on Unsplash.


A whinnying horse. A blaxploitation sample. A female instructor saying Chinese is the easiest language to learn. These three brief audio samples regularly interrupt my late-night headphone music listening.

I’m not tripping or having a medical episode. My bedroom faces the rear of the Chinese Mission to the UN. I can’t be certain that these unwelcome late-night audio interruptions come from there, but it’s a theory. If you’ve never fallen gently asleep to a bespoke playlist of jazz ballads, only to sit bolt upright in terror an hour later because a horse is shrilly whinnying in your ears, you should try it some time.


Photo by Mikael Kristenson on Unsplash

Categories
Accessibility Adobe Advocacy AIGA art direction Authoring Bandwidth Best practices Browsers business Career client management Community creativity CSS Design Designers development Digital Preservation Fonts Future-Friendly HTML industry interface maturity Medium My Back Pages Off My Lawn! Performance Photoshop Rants Real type on the web Responsibility Responsive Web Design Site Optimization Standards State of the Web The Essentials The Profession Typography Usability User Experience UX Web Design Web Design History Web Standards Websites webtype work Working writing

This Web of Ours, Revisited

ONE MONTH and 24 years ago, in “Where Have All the Designers Gone?” (my HTMHell design column for Adobe of March 20, 2000), I discussed the deepening rift between aesthetically focused web designers and those primarily concerned with creating good experiences online:

More and more web designers seem less and less interested in web design.

Over the past 18 months or so, many of the best practitioners in the industry seem to have given up on the notion that a low-bandwidth, less than cutting-edge site is worth making. Much of the stuff they’ve been making instead has been beautiful and inspiring. But if top designers wash their hands of the rest of the Web, whose hands will build it, and whose minds will guide it? The possibilities are frightening.

An Imperfect Medium for Perfectionists

Why were many of the leading graphic designers and studios at the time uninterested in web design? For one thing, designers trained to strive for visual perfection found the web’s unpredictability depressing. The article provided clues to the frustrations of the time:

Good designers spend hours tweaking typography in Illustrator and Photoshop. Then visitors with slow connections turn off images.

Of course, where professionals trained in graphic design saw a distressing lack of control, others glimpsed in the infant technology a tremendous potential to help people, pixel-perfection be damned. To reduce the conflict to a cartoon, you might characterize it as David Carson versus Jakob Nielsen—though doing so would trivialize the concerns of both men. Designers already charged with creating websites found themselves somewhere in the middle—barking themselves hoarse reminding clients and managers that pixel-perfect rendering was not a thing on the web, while arguing with developers who told designers the exact same thing.

Visually inspiring websites like K10k showed that the web could, if approached carefully and joyfully, provide aesthetic delight. But many designers (along with organizations like AIGA) were unaware of those sites at the time.

Us and Them

Another source of tension in the medium in 2000 sprang from the discrepancy between the privileged access designers enjoyed—fast connections, up-to-date browsers and operating systems, high-res monitors (at least for the time) offering thousands of colors—versus the slow modems, aging and underpowered computers, outdated browsers, and limited-color monitors through which most people at the time experienced the web.

Which was the real design? The widescreen, multicolor, grid-based experience? Or the 216-color job with pixelated Windows type, a shallow “fold,” and pictures of headline text that took forever to be seen?

To view your masterpiece the way most users experienced it, and at the syrup-slow speed with which they experienced it, was to have an awakening or a nightmare—depending on your empathy quotient. Some designers began to take usability, accessibility, and performance seriously as part of their jobs; others fled for the predictability of more settled media (such as print).

A New (Old) Hope

My March, 2000 article ended on an upbeat note—and a gentle call to action:

For content sites to attain the credibility and usefulness of print magazines; for entertainment sites to truly entertain; for commerce sites and Web-based applications to function aesthetically as well as technically, the gifts of talented people are needed. We hope to see you among them.

That was my hope in 2000, and, all these years later, it remains my vision for this web of ours. For though the browsers, connections, and hardware have changed substantially over the past 24 years, and though the medium and its practitioners have, to a significant extent, grown the Hell up, beneath the surface, in 2024, many of these same attitudes and conflicts persist. We can do better.

Minus the framesets that formerly contained it, you may read the original text (complete with archaic instructions about 4.0 browsers and JavaScript that broke my heart, but which Adobe’s editors and producers insisted on posting) courtesy of the Wayback Machine.

☞  Hat tip to Andrey Taritsyn for digging up the article, which I had long forgotten.

Categories
Authoring Best practices Blogs and Blogging Code Compatibility CSS Design development Free Advice Future-Friendly HTML industry Layout links maturity Off My Lawn! Platforms Rants Responsibility Standards State of the Web The Profession Web Design Web Design History Web Standards wisdom

The More Things Change… (or: What’s in a Job Title?)

I’m not a “[full-stack] developer,” regardless of what my last job title says.

I’m not even a front-end developer, thanks to the JavaScript–industrial complex.

I’m a front-of-the-front-end developer, but that’s too long.

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.

Front-end development’s identity crisis by Elly Loel

See also:

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

The profession that dare not speak its name (2007): “No one has tried to measure web design because web design has been a hidden profession.” – zeldman.com

Categories
Advocacy Announcements arts Best practices bugs content Content First editorial Education engagement Ideas industry Microblogging Off My Lawn! Press Publications Publisher's Note Publishing reportage Reporting Responsibility Standards Wit and Wisdom Working writing

Get it right.

Airship city

“Led” is the past tense of “lead.”

L.E.D. Not L.E.A.D.

Example: “Fran, who leads the group, led the meeting.”

When professional publications get the small stuff wrong, it makes us less trusting about the big stuff. Trust in media is already at an all-time low. Don’t alienate liberal arts majors and obsessive compulsives. We may be the last readers standing.

Categories
"Digital Curation" Advocacy Applications apps automattic Blogroll Blogs and Blogging Brands Community content ethics glamorous Ideas Indieweb industry interface links Microauthoring Microblogging Micropublishing Networks Off My Lawn! Own your content Platforms Publications Publishing Rants social media social networking software State of the Web The Essentials twitter Usability User Experience UX Web Design History Websites Weird writing

In search of a digital town square

Ever since an infantile fascist billionaire (hereafter, the IFB) decided to turn Twitter over to the racially hostile anti-science set, folks who previously used that network daily to discuss and amplify topics they cared about have either given up on the very premise of a shared digital commons, continued to post to Twitter while holding their noses, or sought a new digital place to call their own. This post is for the seekers, to compare notes. 

These are my personal observations; your views may differ (and that’s more than okay). In this quick survey, I’m omitting specialty platforms like Tribel, Post, and Substack. Feel free to comment, if you like.

The platforms

BlueSky: The most beautifully elegant web interface. Also the best features (other than omission of hashtags). What Twitter should have become. I joined late—Jack didn’t invite me, likely a sign that I was no longer industrially relevant. I have few followers there, and my posts so far get little traction, but that could change. It’s so pretty (and the few friends that use it matter so much to me) that I keep using it, and I reserve judgement as to its future potential. https://bsky.app/profile/zeldman.bsky.social

Threads: Currently my primary alternative to Twitter, and the only place besides Twitter where my posts get at least some response. Not as visually refined as BlueSky, and with a curiously restricted single-hashtag-only policy. Although this editorial decision helps focus the mind, and likely also cuts down on spam, it interferes with amplifying multidimensional posts. But I digress.

Rough edges and restrictive tagging aside, Threads feels like the place that’s likeliest to inherit the mantle of default town square—if any social platform can do that in these new times, that is.

Threads got its huge jump start because, while the IFB was busy finding new ways to make Twitter less useful and more dangerous, Meta leveraged its huge installed Instagram base to give users a more or less instant social network hookup. If it’s easy, and comes with a built-in network of people I already follow, it wins—at least initially.

Meta may also blow their opportunity if they pursue misguided policies, such as impeding (by algorithmic fiat) “political speech” when democracies hang in the balance, regional wars threaten to become world wars, and the climate crisis is approaching a point of no return. https://www.threads.net/@zeldman

Mastodon: How do you decentralize a digital town square? Provide universal social connection without locking in participants? Mastodon (and federation generally) are an attempt to do those things.

These are important and noble goals, but Mastodon (and federation generally) are a long shot at replacing a primary walled garden like Twitter because they require a fair degree of geekery to set up, and the price tag of mass acceptance is ease of setup. (Compare Threads—easy set-up, built-in friends and followers if you already use Instagram—versus the learning curve with Mastodon.)

If BlueSky is MacOS and Threads is Windows, Mastodon is Linux: a great choice for techies, but likely too steep a hill for Ma and Pa Normie. A techie friend invited me to join, and I write there frequently, but, for whatever it’s worth, my Mastodon posts get very little in the way of responses. It is, nonetheless, a highly effective network for most who use it. https://front-end.social/@zeldman

Tumblr: A bit o’ the OG weird wacky wonderful web, and a special place for nonconformist creative types. By its nature, and the nature of its fiercely loyal users, it is a cult jam. I was an early and enthusiastic Tumblr fan, but it was never my main axe, probably because, since the dawn of time itself, I have had zeldman.com.

For a while, when the IFB first started wrecking Twitter, an uptick in Tumblr usage suggested that the funky old network just might take over as the world’s town hall, but this hope was unrealistic, as Tumblr was never about being for everybody, and Tumblristas are mostly happy keeping the platform a home for self-selecting freaks, queers, and creatives.

I’ll note that Tumblr is part of the Automattic family, and I work at Automattic (just celebrated my fifth anniversary there!), but my opinions here are mine alone. BTW—in nearly 30 years of blogging, that’s the first time I’ve used that phrase. https://apartness.tumblr.com

LinkedIn: A comparatively safe social network with a huge network built up over years, hence a great place to share work-related news and ideas.

Some early Twitter adopters of my acquaintance—especially those who mainly write about work topics like UX—have made LinkedIn their primary social home. For most working folks, it is undoubtedly a place to post and amplify at least some of the content that matters to you. OTOH, it’s not a place where I’d share deep takes on CSS (that’s probably Mastodon), cosplay (Tumblr), or personal true confessions (one’s blog, Threads, Twitter before the IFB took over). https://www.linkedin.com/in/zeldman

Twitter itself: During its heyday, before the IFB, and when it was the only game in town, I loved going there to see what clever things my smartest friends were saying, post my own bon mots, and promote content that mattered to me.

I’ll limit my comments on Twitter’s current state to noting that I still post there, from stubbornness as well as habit, and primarily in the (increasingly forlorn) hope that the IFB will eventually tire of his toy, or of the ceaseless financial hemorrhage, and go away, leaving the site to rebirth itself as an open source project or under the care of new, non-fascist owners.

Though the algorithm punishes my posts, and though I’m continually appalled by the MAGA posts, Russian disinformation, racist/ misogynist/ anti-semitic spew, and Trumpian ego of the current owner, I shall, at least for now, continue to defend my tiny turf there.

8 responses to “In search of a digital town square”

  1. L. Jeffrey Zeldman Avatar
    L. Jeffrey Zeldman

    Psst. Comments are back. This is a test.

  2. dusoft Avatar
    dusoft

    I follow you on Mastodon and even when usually don’t respond to bunch of posts, I can still appreciate people being there. Since I use RSS, I get to read your posts that way usually coming to your website.

  3. Zeldman on Web and Interaction Design Avatar
    Zeldman on Web and Interaction Design

    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…

  4. letture suggerite del 3 marzo 2024 » kOoLiNuS ☞ il blog

    […] In search of a digital town square – L. Jeffrey Zeldman, non l’ultimo dei fessi sul web, cerca di fare il punto sullo stato dell’arte del self publishing oggi; […]

  5. suggested reads for March 3, 2024 – /home/kOoLiNuS

    […] In search of a digital town square – L. Jeffrey Zeldman, talks about the state of the art on mantaining a presence on the web today, with the available tools. […]

  6. Weekly Links 02.26–03.03 – ntdln

    […] In search of a digital town square (Jeffrey Zeldman) […]

  7. Zeldman on Web and Interaction Design Avatar
    Zeldman on Web and Interaction Design

    Bluesky introduces open-source, collaborative moderation for federated social media websites: Bluesky was created to put users and communities in control of their social spaces online.…

  8. Zeldman on Web and Interaction Design Avatar
    Zeldman on Web and Interaction Design

    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…

To respond on your own website, enter the URL of your response which should contain a link to this post’s permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post’s URL again. (Find out more about Webmentions.)

Mentions

  • 💬 Zeldman on Web and Interaction Design
  • 💬 Zeldman on Web and Interaction Design
  • 💬 Zeldman on Web and Interaction Design
Categories
A List Apart Career Community Coudal Partners creativity Design Designers glamorous Happy Cog™ Indieweb links Mentoring Off My Lawn! Products Small Business social media State of the Web User Experience UX Web Design History wisdom

Fly, my designers, fly!

A bat signal symbolizes a designer putting themselves out there as being willing to take on work.
Illustration by Fabio Benê

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 State of UX in 2024

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,

When You Are Your Own Client, Who Are You Going To Make Fun Of At The Bar?

by Jim Coudal (2005),

Starting a Business: Advice from the Trenches

by Kevin Potts (2003), and

THIS WEB BUSINESS, Part One

by Scott Kramer (2000, one of four terrific ALA articles by Scott on that subject).

That widespread, intoxicating entrepreneurial impulse led to a cornucopia of internet content 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.

Read: The State of UX in 2024.

Categories
Best practices blogger Blogs and Blogging Community content Content First Content-First creativity editorial findability Free Advice Ideas Indieweb industry links Marketing Off My Lawn! Own your content Platforms Publications Publishing Search Standards State of the Web Teapot The Essentials The Profession Wah! writing

Algorithm & Blues

Examining last week’s Verge-vs-Sullivan “Google ruined the web” debate, author Elizabeth Tai writes:

I don’t know any class of user more abused by SEO and Google search than the writer. Whether they’re working for their bread [and] butter or are just writing for fun, writers have to write the way Google wants them to just to get seen.

I wrote extensively about this in Google’s Helpful Content Update isn’t kind to nicheless blogs and How I’m Healing from Algorithms where I said: “Algorithms are forcing us to create art that fits into a neat little box — their neat little box.”

So, despite Sullivan’s claims to the contrary, the Internet has sucked for me in the last 10 years. Not only because I was forced to create content in a way that pleases their many rules, but because I have to compete with SEO-optimized garbage fuelled by people with deep pockets and desires for deep pockets.

Is the Internet really broken?

For digital creators who prefer to contain multitudes, Tai finds hope in abandoning the algorithm game, and accepting a loss of clout, followers, and discoverability as the price of remaining true to your actual voice and interests:

However, this year, I regained more joy as a writer when I gave upon SEO and decided to become an imperfect gardener of my digital garden. So there’s hope for us yet.

As for folks who don’t spend their time macro-blogging—“ordinary people” who use rather than spend significant chunks of their day creating web content—Tai points out that this, statistically at least a more important issue than the fate and choices of the artists formerly known as digerati, remains unsolved, but with glimmers of partially solution-shaped indicators in the form of a re-emerging indieweb impulse:

Still, as much as I agree with The Verge’s conclusions, I feel that pointing fingers is useless. The bigger question is, How do we fix the Internet for the ordinary person?

The big wigs don’t seem to want to answer that question thoroughly, perhaps because there’s no big money in this, so people have been trying to find solutions on their own.

We have the Indieweb movement, the Fediverse like Mastodon and Substack rising to fill the gap. It’s a ragtag ecosystem humming beneath Google’s layer on the Internet. And I welcome its growth.

For more depth and fuller flavor, I encourage you to read the entirety of “Is the internet really broken?” on elizabethtai.com. (Then read her other writings, and follow her on our fractured social web.)


“The independent content creator refuses to die.” – this website, ca. 1996, and again in 2001, paraphrasing Frank Zappa paraphrasing Edgar Varese, obviously.

Hat tip: Simon Cox.

Categories
Advocacy Archiving Browsers Community Design glamorous HTML industry javascript launches links Off My Lawn! people Publications Responsive Web Design Standards State of the Web Stories The Profession W3C Web Design Web Design History Web Standards Websites

He Built This City: The Return of Glenn Davis

You may not know his name, but he played a huge part in creating the web you take for granted today. 

As the first person to realize, way back in 1994, that the emerging web could be a playground, he created Cool Site of the Day as a single-focused blog dedicated to surfacing interesting sites, thereby demonstrating the web’s potential while creating its first viral content. (As an example, traffic from his followers, or, as we called them back then, readers, brought NASA’s web server to its knees.)

He co-founded The Web Standards Project, which succeeded in bringing standards to our browsers at a time when browser makers saw the web as a software market to be dominated, and not a precious commons to be nurtured.

He anticipated responsive web design by more than 20 years with his formulation of Liquid, Ice, and Jello as the three possible ways a designer could negotiate the need for meaningful layout vis-a-vis the unknowns of the user’s browsing environment.

He taught the web DHTML through his educational Project Cool Site. 

And then, like a handful of other vital contributors to the early web (e.g. Todd Fahrner and Dean Allen), he vanished from the scene he’d played so large a role in creating.

He’s ba-ack

Glenn Davis wasn’t always missed. Like many other creators of culture, he is autistic and can be abrasive and socially unclueful without realizing it. Before he was diagnosed, some people said Glenn was an a**hole—and some no doubt still will say that. I think of him as too big for any room that would have him. And I’m talking about him here because he is talking about himself (and the history of the early web) on his new website, Verevolf.

If you go there, start with the introduction, and, if it speaks to you, read his stories and consider sharing your own. That’s how we did it in the early days, and it’s still a fine way to do it—maybe even the best way.

I knew Glenn, I worked with him and a lot of other talented people on The Web Standards Project (you’re welcome!), and it’s my opinion that—if you’re interested in how the web got to be the web, or if you were around at the time and are curious about a fellow survivor—you might enjoy yourself.

Categories
An Event Apart Appearances art direction better-know-a-speaker books Career conferences Design Designers Education events Genius glamorous Illustration industry Interviews New York City NYC Off My Lawn! speaking Stories Surviving Teaching The Profession UX Web Design Web Design History work

My Night With Essl

Mike Essl and I discuss his portfolio.
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. 

Mike Essl

So ended Day 2 of An Event Apart Online Together Fall Summit 2021. Day 3 begins in less than two hours. You can still join us … or watch later On Demand.

Categories
Advocacy art direction Design Designers Ideas industry interface IXD Jason Santa Maria links Off My Lawn! Redesigns Responsive Web Design State of the Web Tech The Profession User Experience UX Web Design Web Design History webfonts

The Web We Lost: Luke Dorny Redesign

Thumbnails from Luke Dorny’s recently redesigned personal site.

Like 90s hip-hop, The Web We Lost™ retains a near-mystical hold on the hearts and minds of those who were lucky enough to be part of it. Luke Dorny’s recent, lovingly hand-carved redesign of his personal site encompasses several generations of that pioneering creative web. As such, it will repay your curiosity.

Details, details.

Check Luke’s article page for textural, typographic, and interactive hat tips to great old sites from the likes of k10k, Cameron Moll, Jason Santa Maria, and more. 

And don’t stop there; each section of the updated lukedorny.com offers its own little bonus delights. Like the floating titles (on first load) and touchable, complex thumbnail highlights on the “observer” (AKA home) page. 

And by home page, I don’t mean the home page that loads when you first hit the site: that’s a narrow, fixed-width design that’s both a tribute and a goof.

No, I mean the home page that replaces that narrow initial home page once the cookies kick in. Want to see the initial, fixed-width home page again? I’m not sure that you can. Weird detail. Cool detail. Who thinks of such things? Some of us used to.

And don’t miss the subtle thrills of the silken pull threads (complete with shadows) and winking logo pull tab in the site’s footer. I could play with that all day.

Multiply animated elements, paths, and shadows bring life to the footer of Luke Dorny’s newly redesigned website.

Now, no site exactly needs those loving details. But danged if they don’t encourage you to spend time on the site and actually peruse its content. 

There was a time when we thought about things like that. We knew people had a big choice in which websites they chose to visit. (Because people did have a big choice back in them days before social media consolidation.) And we worked to be worthy of their time and attention.

Days of future past

We can still strive to be worthy by sweating details and staying alive to the creative possibilities of the page. Not on every project, of course. But certainly on our personal sites. And we don’t have to limit our creative love and attention only to our personal sites. We pushed ourselves, back then; we can do it again.

In our products, we can remember to add delight as we subtract friction.

And just as an unexpected bouquet can brighten the day for someone we love, in the sites we design for partners, we can be on the lookout for opportunities to pleasantly surprise with unexpected, little, loving details.

Crafted with care doesn’t have to mean bespoke. But it’s remarkable what can happen when, in the early planning stage of a new project, we act as if we’re going to have to create each page from scratch.

In calling Luke Dorny’s site to your attention, I must disclaim a few things:

  • I haven’t run accessibility tests on lukedorny.com or even tried to navigate it with images off, or via the keyboard.
  • Using pixel fonts for body copy, headlines, labels, and so on—while entirely appropriate to the period Luke’s celebrating and conceptually necessary for the design to work as it should—isn’t the most readable choice and may cause difficulty for some readers.
  • I haven’t tested the site in every browser and on every known device. I haven’t checked its optimization. For all I know, the site may pass such tests with flying colors, but I tend to think all this beauty comes at a price in terms of assets and bandwidth. 

Nevertheless, I do commend this fine website to your loving attention. Maybe spend time on it instead of Twitter next time you take a break?

I’ll be back soon with more examples of sites trying harder.

Simulcast on Automattic Design

Categories
Best practices CSS HTML industry Markup Off My Lawn! Responsibility Standards State of the Web The Essentials The Profession

Kiss My Classname

SORRY. I disagree. Nonsemantic classnames that refer to visual styles will always be a bad idea.

I’m sure you’re a good coder. Probably much better than I am these days. I know most of you weren’t around for the standards wars and don’t know how much damage non-semantic HTML and CSS did to the web.

I’ve worked on big sites and I understand how bloated and non-reusable code can get when a dozen people who don’t talk to each other work on it over a period of years. I don’t believe the problem is the principle of semantic markup or the cascade in CSS. I believe the problem is a dozen people working on something without talking to each other.

Slapping a visually named class on every item in your markup may indeed make your HTML easier to understand for a future developer who takes over without talking to you, especially if you don’t document your work and create a style guide. But making things easier for yourself and other developers is not your job. And if you want to make things easier for yourself and other developers, talk to them, and create a style guide or pattern library.

The codebase on big sites isn’t impenetrable because developers slavishly followed arbitrary best practices. The codebase is broken because developers don’t talk to each other and don’t make style guides or pattern libraries. And they don’t do those things because the people who hire them force them to work faster instead of better. It starts at the top.

Employers who value quality in CSS and markup will insist that their employees communicate, think through long-term implications, and document their work. Employers who see developers and designers as interchangable commodities will hurry their workers along, resulting in bloated codebases that lead intelligent people to blame best practices instead of work processes.

The present is always compromised, always rushed. We muddle through with half the information we need, praised for our speed and faulted when we stop to contemplate or even breathe. Frameworks built on newish worst practices seem like the way out, but they end up teaching and permanently ingraining bad habits in a generation of web makers. Semantics, accessibility, and clarity matter. Reusability is not out of reach. All it takes is clarity and communication.

Categories
A Book Apart A List Apart Advertising Advocacy An Event Apart architecture automattic Blogs and Blogging business Career client services clients climate change Code Community conferences content Coudal Partners creativity CSS Design Designers development DWWS engagement eric meyer Future-Friendly glamorous HTML Ideas industry Jason Santa Maria launches Ma.gnolia My Back Pages Off My Lawn! parenting peachpit Publications Publisher's Note Publishing Redesigns Self-Employment software Standards Startups State of the Web Stories studio.zeldman The Essentials The Profession Usability User Experience UX Web Design Web Design History Web Standards Websites wordpress Working writing Zeldman zeldman.com

Ten Years Ago on the Web

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.

 

 

Categories
Best practices Code Compatibility Content First content strategy Content-First Design Free Advice HTML Illustration Images IXD maturity Mobile mobile Multi-Device Off My Lawn! Performance photography Responsibility Responsive Web Design Standards State of the Web The Essentials The Profession Told you so tweets Usability User Experience UX Web Design Web Design History Web Standards Websites

The Year in Design

  • Mobile is today’s first screen. So design responsively, focusing on content and structure first.
  • Websites and apps alike should remove distractions and let people interact as directly as possible with content.
  • 90 percent of design is typography. And the other 90 percent is whitespace.
  • Boost usability and pleasure with progressive disclosure: menus and functions that appear only when needed.
  • One illustration or original photo beats 100 stock images.
  • Design your system to serve your content, not the other way around.
  • Remove each detail from your design until it breaks.
  • Style is the servant of brand and content. Style without purpose is noise.
  • Nobody waits. Speed is to today’s design what ornament was to yesterday’s.
  • Don’t design to prove you’re clever. Design to make the user think she is.

Also published in Medium

Translated into German (also here) by Mark Sargent

Translated into French by Jean-Baptiste Sachsé

Translated into Turkish by omerbalyali.

Translated into Spanish by Tam Lopez Breit.

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