Adapting Ourselves to Adaptive Content

96
ADAPTING OURSELVES TO ADAPTIVE CONTENT @karenmcgrane

description

Full transcript available here: http://karenmcgrane.com/2012/09/04/adapting-ourselves-to-adaptive-content-video-slides-and-transcript-oh-my/ For years, we've been telling designers: the web is not print. You can't have pixel-perfect layouts. You can't determine how your site will look in every browser, on every platform, on every device. We taught designers to cede control, think in systems, embrace web standards. So why are we still letting content authors plan for where their content will "live" on a web page? Why do we give in when they demand a WYSIWYG text editor that works "just like Microsoft Word"? Worst of all, why do we waste time and money creating and recreating content instead of planning for content reuse? What worked for the desktop web simply won't work for mobile. As our design and development processes evolve, our content workflow has to keep up. Karen will talk about how we have to adapt to creating more flexible content.

Transcript of Adapting Ourselves to Adaptive Content

Page 1: Adapting Ourselves to Adaptive Content

ADAPTING OURSELVES TO ADAPTIVE CONTENT

@karenmcgrane

Page 2: Adapting Ourselves to Adaptive Content
Page 3: Adapting Ourselves to Adaptive Content

“Fragmenting our content across different “device-optimized” experiences is a losing proposition, or at least an unsustainable one.

—Ethan Marcotte Responsive Web Design

Page 4: Adapting Ourselves to Adaptive Content

“You can’t afford to create a piece of content for any one platform. Instead of crafting a website, you have to put more effort into crafting the description of the different bits of an asset, so they can be reused more effectively, so they can deliver more value.

—Nic Newman, BBC

Page 5: Adapting Ourselves to Adaptive Content
Page 6: Adapting Ourselves to Adaptive Content
Page 7: Adapting Ourselves to Adaptive Content
Page 8: Adapting Ourselves to Adaptive Content
Page 9: Adapting Ourselves to Adaptive Content
Page 10: Adapting Ourselves to Adaptive Content

We’re about to usher in a golden age of PDFs on the iPad.

Paul Ford, @ftrain

Page 11: Adapting Ourselves to Adaptive Content

“Existing art and production staffers from the print side would be responsible for making two iPad layouts (one in portrait and one in landscape) on Adobe’s platform.

—Condé Nast Is Experiencing Technical Difficulties

Page 12: Adapting Ourselves to Adaptive Content

All I see is an entire organization screaming,

“WE WANT IT TO BE THE EIGHTIES GODDAMMIT.”

Condé Nast Is Experiencing Technical Difficulties

Page 13: Adapting Ourselves to Adaptive Content

COPE: Create Once, Publish Everywhere

COPE:CREATE ONCE,PUBLISH EVERYWHERE

Page 14: Adapting Ourselves to Adaptive Content

CONTENT

PROVIDERS

MUSIC

PARTNERS

NPR, Open Content and API’s, O’Reilly Oscon 14

Page 17: Adapting Ourselves to Adaptive Content

NPR NEWS iPHONE APP

Page 18: Adapting Ourselves to Adaptive Content

NPR MOBILE WEB SITE

Page 19: Adapting Ourselves to Adaptive Content

NPR ADDICT IPHONE APPProduced by a public user, based entirely on the NPR API

Page 20: Adapting Ourselves to Adaptive Content

NPR ON THE PUBLIC RADIO PLAYER

Page 21: Adapting Ourselves to Adaptive Content

NPR ON WBUR

Page 22: Adapting Ourselves to Adaptive Content

NPR ON MPR

Page 23: Adapting Ourselves to Adaptive Content

NPR ON iGOOGLE

Page 24: Adapting Ourselves to Adaptive Content

NPR IN iTUNES

Page 25: Adapting Ourselves to Adaptive Content
Page 26: Adapting Ourselves to Adaptive Content

NPR’S CMS

Page 27: Adapting Ourselves to Adaptive Content

NPR’S API

Page 28: Adapting Ourselves to Adaptive Content

BUSINESS VALUE?

Page 29: Adapting Ourselves to Adaptive Content

Sept. Nov. Sept. Nov. Sept. Nov. Sept. Nov.

2,775

8,700

11,000

22,000

4,300

10,500

13,000

31,000

2010 iPAD ISSUE SALES

Page 30: Adapting Ourselves to Adaptive Content

NPR PAGE VIEWS

43 Million

88 Million

Page 31: Adapting Ourselves to Adaptive Content

“Over the last year, NPR’s total page view growth has increased by more than 80%. How did we get that much growth? Our API.

—Zach Brand, Senior Director Technology, NPR

Page 32: Adapting Ourselves to Adaptive Content

“The biggest impact that the API has made, however, is with our mobile strategy. The API has enabled NPR product owners to build specialized apps on a wide range of platforms and devices, liberating them from being dependent on custom development to access the content. Through this process, we built our iPhone and iPad apps, mobile sites, Android app and HTML5 site, some of which were turned around in a matter of weeks!

Page 33: Adapting Ourselves to Adaptive Content

Bringing it all together into a cohesive workflow has been a real challenge for us. It’s been tough — there’s a lot more work.

Our goal is to have ultimate flexibility and we’re able to take a piece of content and put it on 15 different screens and still have a very consistent look and feel.

Our aim is to publish once and distribute everywhere.Instead of building a product and a workflow to support, we’re trying to flip that to build a workflow and a system to support these multiple design outputs: Adaptive Content.

Page 34: Adapting Ourselves to Adaptive Content

THE FUTURE OF ADAPTIVE CONTENT

Page 35: Adapting Ourselves to Adaptive Content

SemanticAtomized

Intelligent

Adaptive

Nimble Agile

Structured

Flexible

Page 36: Adapting Ourselves to Adaptive Content

CONTENT

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 37: Adapting Ourselves to Adaptive Content

REUSABLE CONTENT STORE

Page 38: Adapting Ourselves to Adaptive Content
Page 39: Adapting Ourselves to Adaptive Content
Page 40: Adapting Ourselves to Adaptive Content
Page 41: Adapting Ourselves to Adaptive Content
Page 42: Adapting Ourselves to Adaptive Content
Page 43: Adapting Ourselves to Adaptive Content

MULTIPLE SIZESMEANINGFUL METADATAWRITTEN FOR REUSE

Page 44: Adapting Ourselves to Adaptive Content
Page 45: Adapting Ourselves to Adaptive Content
Page 46: Adapting Ourselves to Adaptive Content
Page 47: Adapting Ourselves to Adaptive Content

WHY ARE NEWS ORGANIZATIONS THE INNOVATORS?

Page 48: Adapting Ourselves to Adaptive Content

Masthead

Hed: Headline, heading, head or title of a story, rarely a complete sentence.Dek: Deck, blurb, or article teaser or sub-headline. A phrase or two between the headline and the body of the article that explains what the story is about.

Lede: Lead, as in leading paragraph, usually the first sentence, or in some cases the first two sentences, ideally 20-25 words in length. An effective lead is a brief, sharp statement of the story's essential facts.

Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.

Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

•Nut graf

•Nutshell paragraph

•Summarizes the story's content

•Often bullet-pointed

•Sometimes set off in a box

Captions are photo headlinesCutlines are the words (under the caption, if there is one) describing the photograph or illustration.

Page 49: Adapting Ourselves to Adaptive Content

It’s scary to think about your package devolved into different content elements. It takes imagination and understanding to

take that apart. And courage.

Sarah Chubb Sauvayre, Condé Nast

Page 50: Adapting Ourselves to Adaptive Content

THE PRIMACY OF PRINT

Page 51: Adapting Ourselves to Adaptive Content
Page 52: Adapting Ourselves to Adaptive Content
Page 53: Adapting Ourselves to Adaptive Content
Page 54: Adapting Ourselves to Adaptive Content

Thinking about where content will “live” on a “web page” is pretty 1999.

Lisa Welchman, @lwelchman

Page 55: Adapting Ourselves to Adaptive Content

PRINT

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 56: Adapting Ourselves to Adaptive Content

WEB

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 57: Adapting Ourselves to Adaptive Content

MOBILE

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 58: Adapting Ourselves to Adaptive Content

CONTENT

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 59: Adapting Ourselves to Adaptive Content

THE MARRIAGE OF CONTENT AND FORM

Page 60: Adapting Ourselves to Adaptive Content

“Traditional publishing and content management systems bind content to display and delivery mechanisms, which forces a recycling approach for multi-platform publishing.

—Dan Willis

Page 61: Adapting Ourselves to Adaptive Content

“A semantic content publishing system creates well-defined chunks of content that can be combined in whatever way is most appropriate for a particular platform. All display issues are addressed by delivery applications, rather than by a content management system earlier in the process.

Page 62: Adapting Ourselves to Adaptive Content

WHAT DO WE NEED TO GET THERE?

Page 63: Adapting Ourselves to Adaptive Content

MULTIPLE SIZESMEANINGFUL METADATAWRITTEN FOR REUSE

Page 64: Adapting Ourselves to Adaptive Content

WRITE FOR THE CHUNK, NOT THE PAGEDEMYSTIFY METADATABETTER CMS WORKFLOW

Page 65: Adapting Ourselves to Adaptive Content
Page 66: Adapting Ourselves to Adaptive Content
Page 67: Adapting Ourselves to Adaptive Content
Page 68: Adapting Ourselves to Adaptive Content

TRUNCATION IS NOT A CONTENT STRATE...

Page 69: Adapting Ourselves to Adaptive Content
Page 70: Adapting Ourselves to Adaptive Content

BLOBS vs. CHUNKS

Page 71: Adapting Ourselves to Adaptive Content

NPR’S CMS

Page 72: Adapting Ourselves to Adaptive Content

Page TitleExample: Widget-o-Rama: FancyWidget No. 5

Product Name

Product Line

Short Description

Example description: Widget-o-Rama’s FancyWidget No. 5 is an inverse reactive current supply mechanism used for operating nofer-trunnions and reducing sinusoidal depleneration when used in conjunction with a drawn reciprocating dingle arm.

Guidelines: Two sentences. The product description should answer the questions “What is it?” “Who is it for?” and “What does it do?” The description must include at least one real, actual noun besides the name of the product.

PRODUCT DESCRIPTION—ANSWERS THE QUESTION “WHAT IS IT?”

PRODUCT BENEFITS—ANSWERS THE QUESTION “WHY SHOULD I BUY IT?”

Benefit/Feature Pairs

Guidelines: Benefits are about the customer and answer the question, “What will this do for me?” Features are about the product and answer the question, “How does the product work?” On the Widget-o-Rama website, they should come in pairs consisting of a very specific benefit, followed by the feature or features that make it possible. Use concrete terms whenever you can.

Examples:Reduces maintenance costs by up to 50% by replacing delicate gremlin studs with a robust spiral decommutator and eliminating the need for drammock oil after phase detractors are remissed.Prevents side fumbling via the addition of pentametric fan consisting of six hydrocoptic marzelvanes fitted to the ambifacient lunar vaneshaft.

Page 73: Adapting Ourselves to Adaptive Content

CMS CONTENT STRATEGY

CSS

ADAPTIVE CONTENT

Content Wrangling

DataModel

DisplayStyles

Page 74: Adapting Ourselves to Adaptive Content

DEMYSTIFYING METADATA

Page 75: Adapting Ourselves to Adaptive Content

METADATA PROGRAMMATICALLY BUILDS PAGES

Page 76: Adapting Ourselves to Adaptive Content

Metadata is the new art direction.

Ethan Resnick, @studip101

Page 77: Adapting Ourselves to Adaptive Content

METADATA HELPS PRIORITIZE CONTENT

Page 78: Adapting Ourselves to Adaptive Content
Page 79: Adapting Ourselves to Adaptive Content
Page 80: Adapting Ourselves to Adaptive Content

METADATA SUPPORTS PERSONALIZED CONTENT

Page 81: Adapting Ourselves to Adaptive Content

BETTER CMS WORKFLOW

Page 82: Adapting Ourselves to Adaptive Content

Content admins hate all the fields.But the reason they hate all the fields

is the workflow is bad.

Jason Pamental, @jpamental

Page 83: Adapting Ourselves to Adaptive Content

CMS IS THE ENTERPRISE SOFTWARE THAT UX FORGOT

Page 84: Adapting Ourselves to Adaptive Content
Page 85: Adapting Ourselves to Adaptive Content
Page 86: Adapting Ourselves to Adaptive Content
Page 87: Adapting Ourselves to Adaptive Content

CONTEXTUAL INQUIRYUSER PERSONASUSER SCENARIOSTASK ANALYSISWORKFLOW MAPPINGCARD SORTINGCONTENT MODELINGITERATIVE PROTOTYPINGUSABILITY TESTINGANALYTICS DATA

CONTEXTUAL INQUIRYUSER PERSONASUSER SCENARIOSTASK ANALYSISWORKFLOW MAPPINGCARD SORTINGCONTENT MODELINGITERATIVE PROTOTYPINGUSABILITY TESTINGANALYTICS DATA

Page 88: Adapting Ourselves to Adaptive Content

“The happier people are, the better their content will be, the more content they’ll produce.

—Patrick Cooper, NPR

Page 89: Adapting Ourselves to Adaptive Content

“Beautiful software, even for back-end users, is becoming an expectation.We’re moving in this direction because we now understand that better content management systems foster better content.

—Matt Thompson

Page 90: Adapting Ourselves to Adaptive Content

USE MOBILE AS A WEDGE.

Page 91: Adapting Ourselves to Adaptive Content

The more structure you put into content the freer it will become.

Rachel Lovinger, @rlovinger

Page 92: Adapting Ourselves to Adaptive Content

SEPARATION OF CONTENT FROM DISPLAY.(FOR REAL THIS TIME.)

Page 93: Adapting Ourselves to Adaptive Content

The future of content management systems is in their ability

to capture the content in a clean, presentation-independent way.

Daniel Jacobson, NPR

Page 94: Adapting Ourselves to Adaptive Content

DESIGN WITH AND FORSTRUCTURED CONTENT.

Page 95: Adapting Ourselves to Adaptive Content

I’ve never seen anyone regret having flexibility in how they deploy content.

Jeff Eaton, @eaton