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
Accessibility Advocacy architecture Authoring Best practices development ethics industry Performance Platforms Responsibility Standards State of the Web Usability User Experience UX W3C Web Standards

CAPTCHA excludes disabled web users

What’s widely used, no longer particularly effective, and makes web content inaccessible to many people with disabilities? It’s our old friend CAPTCHA! In a group note dated 16 December 2021, the W3C explains how CAPTCHA excludes disabled users, and suggests alternatives which may be kinder and more reliable:

Various approaches have been employed over many years to distinguish human users of web sites from robots. The traditional CAPTCHA approach asking users to identify obscured text in an image remains common, but other approaches have emerged. All interactive approaches require users to perform a task believed to be relatively easy for humans but difficult for robots. Unfortunately the very nature of the interactive task inherently excludes many people with disabilities, resulting in a denial of service to these users. Research findings also indicate that many popular CAPTCHA techniques are no longer particularly effective or secure, further complicating the challenge of providing services secured from robotic intrusion yet accessible to people with disabilities. This document examines a number of approaches that allow systems to test for human users and the extent to which these approaches adequately accommodate people with disabilities, including recent non-interactive and tokenized approaches. We have grouped these approaches by two category classifications: Stand-Alone Approaches that can be deployed on a web host without engaging the services of unrelated third parties and Multi-Party Approaches that engage the services of an unrelated third party.

W3C: Inaccessibility of CAPTCHA: Alternatives to Visual Turing Tests on the Web

We can do better!

Tell your friends. Tell your boss. Tell your clients.

Tip o’ the blue beanie to Adrian Roselli.

Categories
State of the Web W3C Web Standards

Heal an ailing web

On the occasion of the web’s 35th anniversary, its inventor had this to say:

5 years ago, when the web turned 30, I called out some of the dysfunction caused by the web being dominated by the self-interest of several corporations that have eroded the web’s values and led to breakdown and harm. Now, 5 years on as we arrive at the Web’s 35th Birthday, the rapid advancement of AI has exacerbated these concerns, proving that issues on the web are not isolated but rather deeply intertwined with emerging technologies. 

There are two clear, connected issues to address. The first is the extent of power concentration, which contradicts the decentralised spirit I originally envisioned. This has segmented the web, with a fight to keep users hooked on one platform to optimise profit through the passive observation of content. This exploitative business model is particularly grave in this year of elections that could unravel political turmoil. Compounding this issue is the second, the personal data market that has exploited people’s time and data with the creation of deep profiles that allow for targeted advertising and ultimately control over the information people are fed.

How has this happened? Leadership, hindered by a lack of diversity, has steered away from a tool for public good and one that is instead subject to capitalist forces resulting in monopolisation. Governance, which should correct for this, has failed to do so, with regulatory measures being outstripped by the rapid development of innovation, leading to a widening gap between technological advancements and effective oversight.

The future hinges on our ability to both reform the current system and create a new one that genuinely serves the best interests of humanity. 

Marking the Web’s 35th Birthday: An Open Letter from Tim Berners-Lee
Categories
A List Apart art direction Design Standards State of the Web Web Design Web Design History Web Standards webfonts Websites webtype

The Next Generation of Web Layouts

Who will design the next generation of readable, writerly web layouts?

Layouts for sites that are mostly writing. Designed by people who love writing. Where text can be engaging even if it isn’t offset by art or photography. Where text is the point.

With well considered flexible typesettingmodular scaling, and readable measures across a full range of proportions and devices. With optional small details that make reading screens of text a pleasure instead of a chore. With type sizes that are easy to read without needing to zoom in. And with a range of interesting sans and serif fonts (including variable fonts) that support reading and encourage creative exploration where headlines are concerned.

Well? How did we get here?

The web has come along way since design meant crafting UIs in Photoshop and exporting them as sliced GIFs. Flash. SiFR. Table layout. Rebellion and rethinking. Liquid layout. Semantic HTML and CSS layout. Adaptive layout. Responsive layout. Intrinsic layout. Web fonts. Big type and super lightweight UX emphasizing readability was new (and controversial!) in 2012. We’ve long since accepted and improved upon it. Today’s news, magazine, and blog pages are more flexible, readable, and refined than ever before.

So what comes next? For writers, one hopes that what’s next is a fresh crop of small, innovative advancements. Improvements that are felt by readers, even when they aren’t always consciously noticed. Layouts that are not merely legible, but actually feel inevitable, at all sizes and in all contexts.

Beyond outside the box

Services like Typetura may point the way. A marriage of type and tech, Typetura is different from other typesetting methods. An intrinsic typography technology, it “enables you to design with more flexibility, while dramatically reducing code.” Disclaimer: I’m friends with, and have long admired the work of, Typetura founder Scott Kellum. Designing With Web Standards readers will recognize his name from the Kellum Image Replacement days of the early 2000s, but that ain’t the half of what he has done for web design, e.g. inventing dynamic typographic systemshigh impact ad formatsnew parallax techniques, and fluid typesetting technology. Scott was also the coder, along with Filipe Fortes, of Roger Black’s late, lamented Treesaver technology. But I digress.

The tech is not the pointexcept in so far as it improves our ability to think beyond our current understanding of what design and layout means. Just as Gutenberg’s printing press was not the point, but it was the point of departure. Initially, the invention of movable type reproduced the writing we already knew (i.e. the King James Bible). But ultimately, by freeing writing and reading from narrow elite circles and bringing it to more (and more diverse) minds, Gutenberg’s invention transformed what writing was and could be—from the invention of newspapers to the fiction of Virginia Woolf to multimedia experiences, and perhaps even to the web.

Let us all to play with Jen Simmons’s intrinsic web layout ideas and Scott Kellum and partners’s Typetura. While we also sketch in pencil and spend time looking at well designed books —printed, bound ones as well as digital publications in various devices. And specifically, not just fabulous coffee table books, but books that you’ve reread over and over, to understand what, beyond the text itself, encourages that reading response. So that, together, we may take the experiences of both reading and writing to the next level.

Appendix: Resources

If you’re new to the interplay between design and code on the open web, or if you just want a refresher, here are some evergreen links for your further learning and pleasure:


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
Advocacy automattic Blogs and Blogging Brands Community Design industry Own your content software Standards Web Design Web Standards wordpress

Enabling Folks to Express Themselves on the Web: State of the Word 2021

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.

—Matt Mullenweg, State of the Word 

In a live address, Automattic’s Matt Mullenweg

  • Introduces Openverse (an opt-in content commons);
  • Announces that WordPress’s beginner-friendly Learn.Wordpress.org is now available in 21 languages;
  • Philosophizes about Web3 and the “decentralized web” —which, despite big company colonization attempts, is really what the web has always been;
  • Extols the virtues of Open Source;
  • And more. 

Watch the 2021 #StateoftheWord annual keynote address on YouTube. It’s two hours long, so bring popcorn.

Selected Additional Reactions & Commentary

Hat tips to Chenda Ngak, Reyes Martínez, and Josepha Haden.

Categories
Accessibility Best practices Blue Beanie Day Design W3C Web Design Web Standards

Blue Beanie Day 2021

Photo of astronaut David Bowman from Stanley Kubrick’s 2001 wearing a blue beanie in support of web standards.

Blue Beanie Day in support of web standards is celebrated around the world on November 30. Hey, that’s today.

So how can you help? Glad you asked! Take a self-portrait wearing a blue beanie (toque, tuque, cap) and post it to your website and social media channels with the hashtag #BlueBeanieDay.

And for that extra extra, slap a blue beanie on your web and social media avatars, as well.

Do this on November 30 as a reminder to design accessible, web-standards-based websites 365 days a year. Thank you. Love you.

Categories
Best practices Browsers Code Design development Future-Friendly HTML Ideas industry Internship IXD Layout links Multi-Device Responsive Web Design software Standards State of the Web User Experience UX Web Design Web Design History Web Standards Websites

Saving Your Web Workflows with Prototyping

Our static tools and linear workflows aren’t the right fit for the flexible, diverse reality of today’s Web. Making prototyping a central element of your workflows will radically change how you approach problem solution and save you a lot of headaches – and money. But most importantly, you will be creating the right products and features in a way that resonates with the true nature of the Web. A discourse on processes, flexibility, the Web as a material, and how we build things.

Saving Your Web Workflows with Prototyping – Matthias Ott
Categories
Web Design History Web Standards Websites

A Dao of Responsive Liquid

A liquid page will resize to fit whatever size browser window (within reason) that the user has available. … the real goal in building a website is to provide the user with a seamless interface to information. The site should not intrude on the user’s thought processes, but should gently guide them to their desired destination. If a site doesn’t look right because it doesn’t fit the user’s browser window, then the design has become intrusive to the user.?—?Glenn Davis, quoted in 15 Minutes, sometime in 1997.

TWO DECADES before Responsive Web Design, we dipped our toes in Liquid Layout?—?a similar but necessarily less refined concept. Glenn Davis of Project Cool fame coined the phrase in 1995 or 1996. (Glenn also came up with“Ice” to describe fixed-width layouts, and “Jello” for layouts that combined some fixed with some flexible elements.)

Liquid Layout was mainly what John Allsopp had in mind when he wrote A Dao of Web Design for A List Apart (quite possibly the most influential article we ever published). The most famous paragraph in that famous article explains…

The control which designers know in the print medium, and often desire in the web medium, is simply a function of the limitation of the printed page. We should embrace the fact that the web doesn’t have the same constraints, and design for this flexibility. But first, we must “accept the ebb and flow of things.”

Everything new is old

Modern designers look back at Allsopp’s article and think John must have been a time traveler who had seen the future of responsive design and mobile devices. In fact, though, John was simply a highly skilled (and extremely articulate) mainstream developer. As such, he was familiar with Liquid Design and frequently used it in his work, along with other ideas mentioned in “Dao,” such as not forcing users to see a particular type size or typeface. To a good developer in those days, what mattered was making something that worked for everyone. (That should still be what good developers care most about, right?)

Liquid design was part of a “works for everyone” approach to web design, but it had limitations. For one thing, breakpoints hadn’t been invented. CSS layout was in its infancy, used by almost no one, except in experimental work. The ability to separate content and behavior from presentation was nonexistent, unless you limited “presentation” to setting type in a single column, letting the user override the type setting, and letting the column reshape itself to fit any viewport.

With so few controls available, Liquid design tended to become unusable in certain settings, and was almost always ugly.

Liquid design was Responsive design’s rough draft

Liquid design was immediately popular with developers when they were given permission to just make stuff?—?i.e. when they weren’t constrained by overly rigid Photoshop layouts. Designers almost never used Liquid design because the layouts moved so quickly into ugliness and unusability?—?too wide to read, or too narrow, or with overlapping columns in early CSS layouts. Designers also disdained Liquid layouts because most of us see our job as imposing brilliant order on ugly chaos, and fixed proportions always seemed to be part of that order.

The Web Standards Project – a liquid layout as seen on a wide computer screen.

Fig 1. The Web Standards Project: a liquid layout as seen on a wide computer screen. Designed by Andy Clarke in the early 2000s.

 

Fig 2. The Web Standards Project: a liquid layout as seen on a narrow computer screen. On the narrow screen, type overlaps and the page becomes unusable.

 

Ugly on one side. Unusable on the other. It took a special breed of designer to forge ahead with Liquid Layout anyway.

Were it were not for the iPhone and the phones and tablets that rose quickly in its wake, the W3C would likely not have invented breakpoints. And without breakpoints, there could be no Responsive Web Design. And without Responsive Web Design, created by a visually gifted designer and with tools to satisfy his peers, the idea that drove Liquid design back in the 1990s would not, at long last, have caught on.

It’s easy to view our current design thinking as more evolved than what we practiced in the past. And in some ways, it is. But if you read between the lines, it’s fair to say that our thinking was always advanced. It’s only now that our tools are beginning to catch up.

Read more about Liquid and Responsive Web Design

 

Illustration by Justin Dauer. Follow me @zeldman. A version of this article appears on Medium. The 11th Annual Blue Beanie Day in support of web standards takes place November 30 on the internet.

 

SaveSave

Categories
Best practices better-know-a-speaker client services Content First Design Designers development industry Interviews Publications Publishing State of the Web The Big Web Show The Profession Web Design Web Design History Web Standards writing

Big Web Show ? 150: Giant Paradigm Shifts and Other Delights With Brad Frost

Brad Frost, photographed at An Event Apart by Jeffrey Zeldman.

BOY, was this show overdue. For the first time ever on The Big Web Show, I chat with my friend, front-end developer extraordinaire Brad Frost, author of the spanking new book, Atomic Design.

We have fun. We go way over time. We kept talking after the show stopped. There was just so much to discuss—including Pattern Lab and style guides, being there for the iPad launch, working with big brands, how to say no and make the client happy you said it, avoiding antipatterns, mobile versus “the real web” (or the way we saw things in 2009), dressing for success, contributing to open source projects, building a community, the early days of Brad’s career, and that new book of his.

Listen to Episode ? 150 on the 5by5 network, or subscribe via iTunes. And pick up Brad’s book before they sell out!

Sponsored by Braintree and Incapsula.

Brad Frost URLS

@brad_frost
http://bradfrost.com
http://patternlab.io/
http://bradfrost.com/blog/
http://bradfrost.github.com/this-is-responsive/
http://wtfmobileweb.com/
http://deathtobullshit.com/
http://wtfqrcodes.com/
http://bradfrost.com/music
http://bradfrost.com/art

Categories
Accessibility Blue Beanie Day Design Web Design Web Design History Web Standards

This year more than ever, Blue Beanie Day matters

Donald Trump mocks reporter with disability. Photo: CNN.

AT FIRST GLANCE, November 2016 has bigger fish to fry than a small, cult holiday celebrated by web developers and designers.

Each day since November 8, 2016 has brought new, and, to some of us, unimaginable challenges to the surface. Half of America is angry and terrified. The other half is angry and celebrating. At a time like now, of what possible use is an annual holiday celebrated mainly on social media by a tiny posse of standards- and accessibility-oriented web developers and designers?

From Blue Beanies to Black Hats

Many web developers have “moved on” from a progressive-enhancement-focused practice that designs web content and web experiences in such a way as to ensure that they are available to all people, regardless of personal ability or the browser or device they use.

Indeed, with more and more new developers entering the profession each day, it’s safe to say that many have never even heard of progressive enhancement and accessible, standards-based design.

For many developers—newcomer and seasoned pro alike—web development is about chasing the edge. The exciting stuff is mainly being done on frameworks that not only use, but in many cases actually require JavaScript.

The trouble with this top-down approach is threefold:

Firstly, many new developers will build powerful portfolios by mastering tools whose functioning and implications they may not fully understand. Their work may be inaccessible to people and devices, and they may not know it—or know how to go under the hood and fix it. (It may also be slow and bloated, and they may not know how to fix that either.) The impressive portfolios of these builders of inaccessible sites will get them hired and promoted to positions of power, where they train other developers to use frameworks to build impressive but inaccessible sites.

Only developers who understand and value accessibility, and can write their own code, will bother learning the equally exciting, equally edgy, equally new standards (like CSS Grid Layout) that enable us to design lean, accessible, forward-compatible, future-friendly web experiences. Fewer and fewer will do so.

Secondly, since companies rely on their senior developers to tell them what kinds of digital experiences to create, as the web-standards-based approach fades from memory, and frameworks eat the universe, more and more organizations will be advised by framework- and Javascript-oriented developers.

Thirdly, and as a result of the first and second points, more and more web experiences every day are being created that are simply not accessible to people with disabilities (or with the “wrong” phone or browser or device), and this will increase as  standards-focused professionals retire or are phased out of the work force, superseded by frameworkistas.

#a11y is Code for “Love Your Neighbor”

This third point is important because people with disabilities are already under attack, by example of the U.S. president-elect, and as part of of a recent rise in hate crimes perpetrated by a small but vocal fringe. This fringe group of haters has always been with us, but now they are out of the shadows. They are organized and motivated, and to an unmeasured degree, they helped Donald Trump win the White House. Now that he’s there, people of good will ardently hope that he will condemn the worst bigots among his supporters, and fulfill his executive duties on behalf of all the people. I’m not saying I expect him to do this today. I’m saying I hope he does—and meantime it behooves us to find ways to do more than just hope. Ways to make change.

One small thing designers and developers can do is to make accessibility and usability Job 1 on every project. And to take a broad view of what that means. It means taking people’s messy humanity into account and designing for extreme ends of the bell curve, not just following accessibility authoring guidelines. (But it also means following them.)

In doing those things, we can love our neighbors through action. That—and not simply making sure your HTML validates—is what designing with web standards was always about.

On November 30, I will put on my blue hat and renew my commitment to that cause. Please join me.

 

Also published on Medium.

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 bugsworrying 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 onetwothree, or four, have a look back.

 

 

Categories
Advertising An Event Apart Design State of the Web Web Design Web Design History Web Standards Zeldman

Helvetica With Curves—And Other Updated Classics

Keynotesnaps001

Title card from ‘Designing With Web Standards in 2016,’ An Event Apart presentation by Jeffrey Zeldman. Text is set in Forma, an upcoming face from Font Bureau.


NOT UNLIKE what Mattel has done with Barbie, the typographic geniuses at The Font Bureau are working on a humanist geometric sans-serif that could almost be thought of as Helvetica with curves.

Forma is the name of the as-yet unreleased font family, and you can get a peek at one weight of it in the above image, which is taken from my slide deck for “Designing With Web Standards in 2016,” which is the presentation I’ll premiere next month at An Event Apart Nashville.

This new presentation examines the seemingly ever-deepening complexity of designing for our medium today—a complexity that has driven some longtime web designers I know to declare that web design has become “too hard,” or that “the fun has gone out of it”—and asks what our traditions of designing with web standards can teach us about crafting web experiences for a multi-device, mobile-first world.

Given that my original (unpublished) title for Designing With Web Standards was going to be Forward Compatibility—and given that Forward Compatibility is not so different in concept from today’s phrase, Future-Friendly—I’m guessing that structured, semantically marked-up content, progressive enhancement, and the separation of style from structure and behavior still have a huge role to play in today’s day-to-day web design work.

Oh, dear, I hope that wasn’t a spoiler.

I look forward to sharing these ideas with you in greater detail at An Event Apart. Now celebrating our tenth year of bringing great ideas to our community, and creating a space where the smartest folks in web design and development can meet, mingle, bond, network, and learn together. Follow @aneventapart for show announcements, links to useful web resources, and free giveaways on the 10th of every month in 2016. (This month’s giveaway, ten beautiful fleece comforters monogrammed with the A Decade Apart logo, went to ten lucky winners on February 10th. Keep watching the skies.)

Categories
A Book Apart A List Apart Advocacy An Event Apart Best practices Big Web Show Browsers chrome Code CSS CSS Grid Layout CSS3 Design HTML Layout Standards State of the Web The Big Web Show Web Design Web Design History Web Standards

CSS Grid Layout with Rachel Andrew: Big Web Show

Rachel Andrew

RACHEL ANDREW—longtime web developer and web standards champion, co-founder of the Perch CMS, and author of Get Ready For CSS Grid Layout—is my guest on today’s Big Web Show. We discuss working with CSS Grid Layout, how Grid enables designers to “do something different” with web layout, why designers need to start experimenting with Grid Layout now, how front-end design has morphed into an engineering discipline, learning HTML and CSS versus learning frameworks, and the magic of David Bowie, RIP.

Enjoy Episode ? 141 of The Big Web Show.

Sponsored by A List Apart and An Event Apart.

URLs

rachelandrew.co.uk
Get Ready for CSS Grid Layout
Perch CMS
Writing by Rachel Andrew
Books by Rachel Andrew
@rachelandrew