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
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
Design development editorial Medium Publisher's Note Publishing Redesigns Responsive Web Design State of the Web Told you so

The Nation, America’s oldest weekly news magazine, launches responsive, large-type redesign.

ON ITS 150th anniversary, The Nation (“a magazine of ideas and values”) relaunches its website, created in partnership with Blue State Digital and Diaspark. As one would expect of an editorially focused web entity in 2015, the new site is responsive, and uses big type and clean layouts designed for readability. It also incorporates social media innovations first seen in Medium, such as the ability to tweet or email any brief passage of text you select.

Executive Editor Richard Kim’s mini-article introducing the new site explains how the editorial process has changed—and how it has stayed the same—since the launch of the magazine’s first site in 1997:

Back then, writing for the magazine was a comparatively monastic experience. You’d work for weeks on an article, defend its arguments against vigorous but loving critiques from the editors, and gratefully accept changes from fact-checkers and copy editors. Finally, the issue would ship to the printer. And then: the vast silence. If you were lucky, a few weeks later, someone might approach you at a party and say how much they liked (or hated) your piece. Some letters from impassioned subscribers would eventually come in via the Postal Service, but encounters with actual readers were rare and cherished events.

We continue to publish the print magazine under these rigorous standards, and it will remain an essential part of our identity, offering readers a considered and curated take on matters of critical interest. The digital revolution, however, has allowed us to connect to vastly more people, and to get to know them better. Today, The Nation publishes about 70 articles a week online, which go out to more than 420,000 Twitter followers, almost 290,000 Facebook fans, and 200,000 e-mail subscribers. And believe me, we always hear back from you….

There’s also a multi-tiered approach to reading and commenting:

For the next few months, there’s no paywall: All of our articles will be free to everyone—our gift to you in The Nation’s 150th-anniversary year. Later, we’ll introduce a metered system that continues to put The Nation in front of new readers, but also asks our regular visitors to contribute to the cost of independent journalism. Finally, only subscribers will be able to leave comments—and they’ll be asked to identify themselves with a first and last name. We realize this will be controversial to some, but keeping the comments free of trolls and bots has taken an increasing amount of effort. We think it’s only fair that commenters stand by what they write, and give something to the community in return.

Categories
art direction Authoring Best practices business CSS Design Platforms Publications Publishing Responsibility Startups State of the Web The Essentials Told you so

Readability 2.0 is disruptive two ways

RELEASED LAST WEEK, Arc90’s Readability 2.0 is a web application/browser extension that removes clutter from any web page, replacing the typical multi-column layout with a simple, elegant, book-style page view—a page view that can be user customized, and that “knows” when it is being viewed on a mobile device and reconfigures itself to create an platform-appropriate reading experience.

In so doing, Readability focuses the user’s attention on the content, creating an enhanced—and often much more accessible—reading experience. It also subverts the typical web browsing design paradigm, where each website offers a different visual experience. Instead, to the Readability user, all web content looks the same, once she has clicked a button to engage the Readability view.

If Readability did only this, it would represent a significant directional departure for the web and for site owners, in that, for the first time in the history of designed websites, branded look and feel is subordinated to a user-focused content experience that transcends the individual site.

Of course, this was always supposed to be possible in HTML, and it always was possible for users of some assistive devices and for CSS experts who felt like creating intricate personal style sheets, but those are edge cases, and Readability is for everyone.

Readability 1.0 was released as open source. Apple used its code for the “Reader” view in Safari. The creators of Flipboard used its code too. And the creators of the open-source Treesaver swapped code and rights with the makers of Readability to enhance both products. I’ve never seen a humble open-source project, created by a not-terribly-well-known shop get so quickly accepted and absorbed by companies like Apple and by the creators of cutting-edge web and hybrid apps.

That was Readability 1.0. What Readability 2.0 adds to the mix is automatic payment for content creators. How it works is simple: I pay a small fee each month to use Readability. Most of that money gets divided between the creators of the web pages I’ve viewed in Readability. This makes Readability 2.0 disruptive two ways:

  1. As mentioned earlier, for the first time, branded look and feel is secondary to the user’s desire to engage with written content in a visually comfortable environment. (That Readability 1.0 premiered around the same time as the iPad is not coincidental.)
  2. For the first time, content monetization is no longer the problem of content creators. Writers can stop being salespeople, and focus on what they do best: creating compelling content. The better the content, the more people who engage with it via Readability, the more money writers will make—with no bookkeeping, no ad sales, and no hassle. This is a huge subversion of the ad paradigm.

Many of us who watched Arc90 develop Readability worried that short-sighted publishers and site owners would misunderstand and reject the app, maybe even sic’ing their lawyers on it. But in the hectic two weeks just ending, publishers have had time to absorb what Readability 2.0 does and what it could mean to them—and according to Readability creator and Arc90 founder Rich Ziade, the reaction is positive.

Have publishers suddenly grasped the web? Perhaps not. But it’s a rare publisher who’d say no to extra money, risk-free. We are in a wait-and-see, try-it-and-see phase of publishing and the web—past the initial Web 2.0 euphoria and into the hard business of creating great stuff (and finding new ways to keep old great stuff, like great writing and reporting, alive). No one is quite sure what will work. And publishers risk nothing by participating in the Readability program. If the program succeeds, they make additional revenue for their content. If it fails, it’s no skin off their budget.

I’ve interviewed Rich Ziade on The Big Web Show and I’m an advisor on the project but it was only last night, when Rich was addressing my MFA Interaction Design class at School of Visual Arts, that I realized for the first time how profoundly disruptive—and powerful—Readability 2.0 really is. (Video of that class session is available.)

If you love reading and the web, I urge you to give Readability 2.0 a try.