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

Of Books and Conferences Past

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

Just as nobody who marries spends their wedding day planning their divorce, almost nobody starts a business contemplating what rocks it will eventually splinter and break upon, and how to build a life raft for themselves.

I take that back. Some folks I know, who played pivotal roles in the evolution of the web, actually started their businesses with a clear goal of selling them to somebody bigger. Like Typekit was designed to sell to Adobe. Or Blogger was designed to sell to Google.

Such folks, several of whom are now post-economy wealthy, lived in the Bay Area in the 1990s and early 2000s, where building to flip was widely discussed and accepted.

Meanwhile, in NYC…

I, on the other hand, live in New York. So I started my web businesses (like Happy Cog™ design studio) to serve clients, as NYC creatives have always done, and with no understanding that I would one day need to leave the company and should have an exit plan. Why would I exit? Why would I ever stop doing work that brought excitement and meaning to my life?

Similarly, I started my personal site with its “Ask Dr. Web” tutorials in 1995, and co-founded my web design publication, A List Apart, in 1997, for the sheer joy of sharing knowledge, with no concept of making money, let alone of one day selling the business.

Eventually, despite my naivete, and mostly thanks to Jim Coudal and Jason Fried, A List Apart began making money by running one carefully screened ad per page. I used that money, as you will expect, to pay our writers, editors, and producers. And when it came time to stop running ads, I slowed our publication schedule, paid writers out of my own pocket, and worked with a small crew of fellow volunteers, who published ALA because we believed in the mission. (Still do.)

If I had come of business age in San Francisco, I likely would have sold A List Apart to somebody like O’Reilly, but that was never my plan because I make toys to play with, not to give away.

An ecosystem apart

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

We published HTML5 For Web Designers the day after Steve Jobs, waving an iPhone on the world’s biggest stage (okay, sitting at his desk), announced that Flash was dead because HTML5 would bring app-like dynamism to the web using open standards instead of proprietary code. It (our first book, I mean) sold brilliantly. “Gee, publishing isn’t that hard” I naively told myself. (No, I knew it was hard. My favorite publishers had been laying off my favorite editors for ten years before my partners and I took the plunge. But the early success did make me think the books we published about web design would always find a large, eager audience. In time, I would learn otherwise.)

And while we began the publishing house by relying on the best writers we knew personally to write about the topics they were most passionate about, I’m proud to say that, as we went along, we also discovered brilliant first-time book authors, helping them create perfectly polished, fluff-free manuscripts that made genuine contributions to our readers’ understanding of UX and all it entails. (And not just to our readers. The insights they brought to their work after digesting our books rubbed off on their colleagues.)

In giving these brilliant writers a platform, we not only helped them take their careers to the next level, we also helped people who create web content think and work better, which in turn helped the people who used the websites, applications, and products our readers designed and built. Of that, I am proud.

Stay hungry

An Event Apart (RIP) was also a damned fine early success. Web designers liked our innovation of a multi-day, single-track conference, with a holistic approach to web design, code, and content, and unifying themes between the individual talks. Our freaking-amazing speakers debuted Huge Ideas including Mobile First and Responsive Web Design—ideas which, like perfect contextual menus in UX, arrived at the very moment designers needed them.

Not only that, but these humble geniuses also sat in the auditorium with our audience for all three days of each conference event: listening to each other’s presentations, and updating their own presentations to better bounce off each other’s ideas and the evolving themes of that particular show. 

I could spend hours telling you how our producer Toby M. made miracles happen at every show, or how person-in-charge Marci E. brought joy to our community. How many of our speakers became authors. How some “graduated” from An Event Apart as newcomers replaced them. How the diversity of our speaking line-up, which wasn’t terrific in 2008, improved greatly each year. (Not that we ever said, “We need another black speaker” or “We need a trans speaker” or what-have-you. Just that we learned to swim outside the pool we came from, and discover great talent everywhere.) Our speakers were also almost uniformly Just Nice Good People, which doesn’t always happen when you’re collecting the greatest minds in an industry. 

That’s not even to mention the incredible people who attended our shows, some of whom became lifetime friends for me.

So why, given the joy these businesses brought to everyone connected to them, including me, would my partners and I have even conceived of an exit strategy? We wanted the Good Times to roll on forever.

But of course they never do.

Things end

COVID did in An Event Apart. Some conferences survived, of course. Different priorities, different overheads, different business models. Some that survived do not pay their speakers. Others, where the conference is an adjunct to a bigger business, laid off or reassigned conference staff while the pandemic made live events impossible. Others that survived mostly rely on volunteer labor, whereas we had paid staff. They were worth their weight in platinum, and we’d have paid them more (because they were worth more) if the pandemic and six-figure hotel contracts hadn’t made continuing the show impossible. My partner and I earned nothing during the business’s last five years, and got personally stuck with a six-figure debt when the event closed. It is what it is.

Although books should be COVID-proof, multiple financial problems eventually beset our publishing house as well. For most of the run of the business, my partner and I earned nothing beyond the glow of contributing to our community’s knowledge. We paid our CEO, authors, and editors, kept nothing for ourselves, and tried, oh how we tried, to keep the business going as its revenues tanked.

Speaking only for myself, I’ve learned that I am good at starting businesses and keeping them going creatively, as long as somebody else figures out the money. I suck at that, and I’m obsessed with the notions of fairness and self-sacrifice that were drummed into me by a narcissistic family that valued me for taking on the roles they were emotionally incapable of handling—such as bringing up my baby brother in my father’s absence, which no child is  equipped or should be asked to do, and yet it happens all the time. Growing up this way made me put my own self-interest last. Which is also why it never occurred to me to plan an exit. And by the time I needed to do so, the businesses were not in shape to sell.

Closing a conference is bad, but attendees can go to other conferences, and speakers can speak at other conferences; closing a conference doesn’t end a community. It sucks for the business but doesn’t strand participants.

But closing a publishing house hurts like hell, and you feel you let everybody down. I know how much our closing hurt some of our authors, and I think about that, instead of the good we achieved, when I look back. 

No doubt when my partner and I write the large personal checks to cover our deceased business’s outstanding debts, we’ll be regretting the harm our closing caused, not basking in the warm glow of how many careers we changed for the better. Like the standup comedian who obsesses about the guy who’s frowning at table 3, and doesn’t hear the laughter of the rest of the crowd. We also, hopefully, won’t focus too closely on our financial wreckage. Just pay the bill, and move on.

Anyway, I hadn’t publicly addressed the endings of these businesses, so I figured it was time to do so. I’m sharing my experience only. If you ask any of the people I worked with on these projects, they might have a different story to tell. And that would be their story, and it would be every bit as valid as anything I’ve said here.

I also didn’t ask permission of my partners, speakers, or authors before sharing these thoughts. Probably I should have. But, hey. As I’ve said. I’m speaking here only for myself.

So, anyway.

Parting gift

Is it worth the risk of starting a web-related business that isn’t a venture-backed startup? I still think it is, and I applaud all who try. Heck, I might even do so myself someday. If you’re doubtful because of (((gestures at everything))), it might be worth noting that I started Happy Cog™ during the dot-com crash, when studios were closing all around me. And we launched A Book Apart during the world financial crisis of late 2008. Don’t let (((all this))) deter you from trying something bold. Let me know when you do. I’ll keep watching the skies.

P.S. Under swell third-party ownership and management, Happy Cog is still going strong. Check it out!

Categories
A Book Apart Design HTML5 Publications Publisher's Note Publishing

Foreword to HTML5 for Web Designers, 2nd Edition

HTML5 for Web Designers, 2nd Edition

WELCOME to the second edition of HTML5 for Web Designers, the book that launched a thousand sites—or apps, if you prefer. It is also the book whose first edition launched our little craft publishing house. And its new edition comes to you when it is needed most, on a web riven by conflicting visions.

For some folks, the web today is what it has always been: namely, the most accessible medium ever devised for sharing content. For others, including the heads of powerful tech companies, the web is a platform for building JavaScript-powered applications whose purpose is to disrupt every industry on earth, chiefly for the benefit of investors.

Adherents of both camps are equally passionate—and both swear by HTML5, which was designed to create both kinds of web. HTML5 has given us a web both more powerful and more divided.

So much has changed over the past five years, it’s hard to remember that many businesses were still betting on Flash as recently as 2009, and still building sites and applications exclusively for the desktop browser. Then, in 2010, Steve Jobs famously declared that his iPhone would not support Flash. Flash was dead, Steve said. HTML5 was the future. A hundred thousand designers, developers, and site owners suddenly asked themselves, “HTML wha—?” The next day, our little book came out, which was good timing for sales, but even better for the industry. And there are still no better guides to the new markup language than Jeremy Keith and Rachel Andrew.

In this book, you will learn what HTML5 is, why it came to be, and how to use it to create sites and applications as powerful as anything you can imagine. Forms, elements, semantics, scripting? It’s all here, guided by a set of principles as straightforward as they are noble—principles that deliver sophisticated web interactivity while remaining true to Tim Berners-Lee’s twenty-five-year-old vision of an open, accessible web that works for all. This book spells out a philosophy that will deepen not only the usability of your projects, but their humanism as well.

HTML5 for Web Designers is a book about HTML like Elements of Style is a book about commas. It’s a book founded on solid design principles, and forged at the cutting edge of twenty-first century multidevice design and development. Jeremy Keith and Rachel Andrew never, for one second, forget what moment of web design history we are in, and how much depends upon our ever bearing in mind not only our users in the wealthiest countries, but also the least of these. I know, admire, and continually learn from the depths of the authors’ belief in humanity and HTML. You will, too.

Jeffrey Zeldman signatureJeffrey Zeldman
Publisher
A Book Apart
February 17, 2016

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
Design glamorous HTML HTML5 industry Interviews Web Design writing Zeldman

Marchgasm!

I’VE BEEN BUSY this month:

And March is only half over.

Categories
Authoring HTML HTML5 State of the Web Web Design Web Design History Web Standards XHTML

Lawson on picture element

Those eager to bash Hixie and the WHATWG are using the new spec as if it were a cudgel; “this is how you deal with Hixie and WHATWG” says Marc Drummond. I don’t think that’s productive. What is productive is the debate that this publication will (hopefully) foster.

Bruce Lawson’s personal site: On the publication of Editor’s draft of the element.

Categories
Design development Formats HTML HTML5 Products software State of the Web Tools

HTML5 Video Player II

JOHN DYER’S MediaElement.js bills itself as “HTML5 <video> and <audio> made easy”—and that’s truly what it is:

For complete information, visit mediaelementjs.com.

Hat tip: Roland Dubois.

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

Leo Laporte interviews JZ

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

Categories
HTML HTML5 Standards State of the Web W3C Web Design History Web Standards

HTML Marches On

IN A LETTER dated July 19, 2012, WHATWG leader and HTML living standard editor (formerly HTML5 editor) Ian Hickson clarifies the relationship between activity on the WHATWG HTML living standard and activity on the W3C HTML5 specification. As my dear Aunt Gladys used to say, you can’t ride two horses with one behind.


Categories
Apple apps Design facebook HTML HTML5 Usability User Experience UX

Facebook goes native

“IF I WERE advising them on these decisions, I would have had them look at what people actually want from Facebook — fast access to their friends’ photos and posts — and … helped them design an HTML5 web experience that actually works for mobile.”

.net magazine: Facebook iPhone app to go native By Tanya Combrinck on June 28, 2012

Categories
A List Apart Design HTML HTML5 Publications Publishing Standards

Publication Standards

ENJOY A LIST APART’S SPECIAL two-part issue on digital publication standards.

Publication Standards Part 1:
The Fragmented Present

by NICK DISABATO

ebooks are a new frontier, but they look a lot like the old web frontier, with HTML, CSS, and XML underpinning the main ebook standard, ePub. Yet there are key distinctions between ebook publishing’s current problems and what the web standards movement faced. The web was founded without an intent to disrupt any particular industry; it had no precedent, no analogy. E-reading antagonizes a large, powerful industry that’s scared of what this new way of reading brings—and they’re either actively fighting open standards or simply ignoring them. In part one of a two-part series in this issue, Nick Disabato examines the explosion in reading, explores how content is freeing itself from context, and mines the broken ebook landscape in search of business logic and a way out of the present mess.

Publication Standards Part 2:
A Standard Future

by NICK DISABATO

The internet is disrupting many content-focused industries, and the publishing landscape is beginning its own transformation in response. Tools haven’t yet been developed to properly, semantically export long-form writing. Most books are encumbered by Digital Rights Management (DRM), a piracy-encouraging practice long since abandoned by the music industry. In the second article of a two-part series in this issue, Nick Disabato discusses the ramifications of these practices for various publishers and proposes a way forward, so we can all continue sharing information openly, in a way that benefits publishers, writers, and readers alike.


Illustration by Kevin Cornell for A List Apart.

Categories
democracy HTML HTML5 State of the Web The Profession Web Design Web Design History Web Standards

The Unbearable Lightness of HTML5 – or, the priority of constituencies versus the great dictator

LET’S DIG A BIT DEEPER into the latest conflict between web developers who are passionate about the future of HTML, and the WHATWG. (See Mat Marquis in Tuesday’s A List Apart, Responsive Images and Web Standards at the Turning Point, for context, and Jeremy Keith, Secret Src in Wednesday’s adactio.com, for additional clarification.)

The WHATWG was created to serve browser makers, while its product, HTML5, was designed to serve users first, designers (authors) next, browser makers (implementors) last according to the priority of constituencies, which is one of its founding design principles.

There is a tension between this principle of HTML5 (to serve users above designers above browser makers) and the reality of who is the master: namely, browser makers – especially Google, which pays Hixie, the editor of HTML5, his salary. That’s not a knock on Hixie (or Google), it’s just the reality.

One way the tension between principle and reality plays out is in not uncommon incidents like the one we’re reacting to now. According to the priority of constituencies, designer/developer feedback should be welcomed, if not outright solicited. In principle, if there is conflict between what designer/developers advise and what browser makers advise, priority should be given to the advice of designer/developers. After all, their needs matter more according to the priority of constituencies — and designer/developers are closer to the end-user (whose needs matter most) than are browser makers.

Solicitiation of and respect for the ideas of people who actually make websites for a living is what would happen if the HTML5-making activity had been organized according to its own priority of constituencies principle; but that kind of organization (committee organization) echoes the structure of the W3C, and the WHATWG arose largely because browser makers had grown unhappy with some aspects of working within the W3C. In reality, there is one “decider” — the editor of HTML5, Ian Hickson. His decisions are final, he is under no obligation to explain his rationales, and he need not prioritize developer recommendations above a browser maker’s — nor above a sandwich maker’s, if it comes to that. By design, Hixie is a free agent according to the structure he himself created, and his browser maker end-users (masters?) like it that way.

They like it that way because stuff gets done. In a way, browser makers are not unlike web developers, eager to implement a list of requirements. We designer/developers don’t like waiting around while an indecisive client endlessly ponders project requirements, right? Well, neither do browser makers. Just like us, they have people on payroll, ready to implement what the client requires. They can’t afford to sit around twiddling their digits any more than we can. In 2007, the entire world economy nearly collapsed. It is still recovering. Don’t expect any surviving business to emulate a country club soon.

So, has this latest friction brought us to a tipping point? Will anything change?

In theory, if we are frustrated with Mr Hickson’s arbitrary dictates or feel that they are wrong, we can take our ideas and our grievances to the W3C, who work on HTML5 in parallel with the WHATWG. We should probably try that, although I tend to think things will continue to work as they do now. The only other way things could change is if Hixie wakes up one morning and decides benevolent dictator is no longer a role he wishes to play. If I were in charge of the future of the web’s markup language, with not just final cut but every cut, I’m not sure I’d have the courage to rethink my role or give some of my power away. But perhaps I underestimate myself. And perhaps Hixie will consider the experiment.

Categories
HTML5 reportage Responsive Web Design W3C

Responsive Images and Web Standards at the Turning Point – Mat Marquis in ALA

IN A SPECIAL ISSUE of A List Apart for people who make websites:

Responsible responsive design demands responsive images — images whose dimensions and file size suit the viewport and bandwidth of the receiving device. As HTML provides no standard element to achieve this purpose, serving responsive images has meant using JavaScript trickery, and accepting that your solution will fail for some users.

Then a few months ago, in response to an article at A List Apart, a W3C Responsive Images Community Group formed — and proposed a simple-to-understand HTML picture element capable of serving responsive images. The group even delivered picture functionality to older browsers via two polyfills: namely, Scott Jehl’s Picturefill and Abban Dunne’s jQuery Picture. The WHATWG has responded by ignoring the community’s work on the picture element, and proposing a more complicated img set element.

Which proposed standard is better, and for whom? Which will win? And what can you do to help avert an “us versus them” crisis that could hurt end-users and turn developers off to the standards process? ALA’s own Mat Marquis explains the ins and outs of responsive images and web standards at the turning point.

Categories
apps Code content content strategy CSS Design HTML HTML5 W3C Web Design Web Design History Web Standards

Designing Apps With Web Standards (HTML is the API)

The Web OS is Already Here… Luke Wroblewski, November 8, 2011

Mobile First Responsive Web Design, Brad Frost, June, 2011

320 and up – prevents mobile devices from downloading desktop assets by using a tiny screen’s stylesheet as its starting point. Andy Clarke and Keith Clark.

Gridless, HTML5/CSS3 boilerplate for mobile-first, responsive designs “with beautiful typography”

HTML5 Boilerplate – 3.02, Feb. 19, 2012, Paul Irish ,Divya Manian, Shichuan, Matthias Bynens, Nicholas Gallagher

HTML5 Reset v 2, Tim Murtaugh, Mike Pick, 2011

CSS Reset, Eric Meyer, v 2.0b1, January 2011

Less Framework 4 – an adaptive CSS grid system, Joni Korpi (@lessframework)

Responsive Web Design by Ethan Marcotte, 2011

Adaptive Web Design by Aaron Gustafson, 2011

Web Standards Curriculum – Opera

Getting Started With Sass by David Demaree, 2011, A List Apart

Dive into Responsive Prototyping with Foundation by Jonathan Smiley, A List Apart, 2012

Future-Ready Content Sara Wachter-Boettcher, February 28, 2012, A List Apart

For a Future Friendly Web Brad Frost, March 13, 2012, A List Apart

Orbital Content Cameron Koczon, April 19, 2011, A List Apart

Web standards win, Windows whimpers in 2012, Neil McAllister, InfoWorld, December 29, 2011

Thoughts on Flash – Steve Jobs, April, 2010

Did We Just Win the Web Standards Battle? ppk, July 2006

Web Standards: Wikipedia

The Web Standards Project: FAQ (updated), February 27, 2002

To Hell With Bad Browsers, A List Apart, 2001

The Web Standards Project: FAQ, 1998

The Web Standards Project: Mission, 1998

HTML5 at A List Apart

Mobile at A List Apart

Browsers at A List Apart

Categories
An Event Apart Appearances CSS CSS3 Design development eric meyer HTML HTML5 Ideas industry Information architecture IXD Platforms Publishing Redesigns Responsive Web Design Scripting Standards State of the Web User Experience UX Web Design Web Standards

CSS & Mobile To The Future | Embrace Users, Constrain Design | An Event Apart Seattle 2012 Day II

TUESDAY, 3 APRIL 2012, was Day II of An Event Apart Seattle, a sold-out, three-day event for people who make websites. If you couldn’t be among us, never fear. The amazing Luke Wroblewski (who leads a day-long seminar on mobile web design today) took excellent notes throughout the day, and shares them herewith:

The (CSS) Future is Now – Eric Meyer

In his The Future is Now talk at An Event Apart in Seattle, WA 2012 Eric Meyer talked about some of the visual effects we can achieve with CSS today. Create shiny new visual elements with no images using progressive enhancement and CSS that is available in all modern browsers.

A Philosophy of Restraint
– Simon Collison

In his A Philosophy of Restraint talk at An Event Apart in Seattle, WA 2012 Simon Collison outlined his design philosophy and how he applies it to web projects. Embrace constraints; simplicity and complexity; design aesthetic; design systems as foundations that prepare us for future projects and complexity; affordances and type; focus and content; audit and pause — prevent catastrophic failures and shine a new light on what you’ve learned with each project.

Touch Events – Peter-Paul Koch (PPK)

In his Touch Events talk at An Event Apart in Seattle, WA 2012 Peter-Paul Koch talked about touch support in mobile browsers and how to handle touch events in web development. Includes a ranking of current mobile browsers; interaction modes in mobile versus desktop (mouse) and keyboard — how do we adjust scripts to work with touch?; touch events; supporting modes; event cascade; and “stick with click.”

Mobile to the Future – Luke Wroblewski

Alas, Luke could not take notes on his own presentation. Here’s what it was about: When something new comes along, it’s common for us to react with what we already know. Radio programming on TV, print design on web pages, and now web page design on mobile devices. But every medium ultimately needs unique thinking and design to reach its true potential. Through an in-depth look at several common web interactions, Luke outlined how to adapt existing desktop design solutions for mobile devices and how to use mobile to expand what’s possible across all devices.Instead of thinking about how to reformat your websites to fit mobile screens, attendees learned to see mobile as way to rethink the future of the web.

What’s Your Problem? – Whitney Hess

In her What’s Your Problem? Putting Purpose Back into Your Projects talk at An Event Apart in Seattle, WA 2012 Whitney Hess outlined the value of learning about opportunities directly from customers. Understand the problem before designing the solution. Ask why before you figure out how. There is no universal solution for all our projects, we need to determine which practices are “best” through our understanding of problems. Our reliance on best practices is creating a world of uniform websites that solve no one’s problem. Leave the desk and interact with people. Rather than the problem solver, be the person who can see the problem.

Properties of Intuitive Pages
– Jared Spool

At An Event Apart in Seattle WA 2012, Jared Spool walked through what makes a design intuitive, why some users need different treatment, and the role of design. Current versus acquired knowledge and how to bridge the gap (how to train users, thus making your site or app “intuitive”). Redesigns and how to avoid disaster. Design skills. The gap between current knowledge and target knowledge is where design happens. Why intuitive design is only possible in small, short iterations.


Day III begins in 90 minutes. See some of you there.

Photos: AEA Seattle Flickr pool or hashtags #aea and #aeasea on Instagram.

Categories
HTML HTML5

HTML5 dumps TIME element

“It’s with great sadness that I inform you that the HTML5 <time> element has been dropped, and replaced by a more generic – and thus less useful – <data> element. The pubdate attribute has been dropped completely, so there is now no simple way to indicate the publication date of a work.”

Much more at Bruce Lawson’s personal site. Hat tip: Stuntbox.