adapting ourselves to adaptive content

92
ADAPTING OURSELVES TO ADAPTIVE CONTENT DIWD 2011 @karenmcgrane #DIWD

Upload: karen-mcgrane

Post on 11-Jan-2017

14.895 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Adapting ourselves to adaptive content

ADAPTING OURSELVES TO ADAPTIVE CONTENT

DIWD 2011@karenmcgrane#DIWD

Page 2: Adapting ourselves to adaptive content

RESPONSIVE DESIGN

2

ADAPTIVE

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

3

Page 4: Adapting ourselves to adaptive content

STRUCTURED CONTENT

4

ADAPTIVE

Page 5: 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

5Nimble Report, http://nimble.razorfish.com

Page 6: Adapting ourselves to adaptive content

6

Page 7: Adapting ourselves to adaptive content

7

Page 8: Adapting ourselves to adaptive content

8

Page 9: Adapting ourselves to adaptive content
Page 10: Adapting ourselves to adaptive content

10

Page 11: Adapting ourselves to adaptive content

11

content

content

content

content

content

content

content

Page 12: Adapting ourselves to adaptive content

http://www.flickr.com/photos/filamentgroup/5149016958/

Page 13: Adapting ourselves to adaptive content

13

FRAGMENTED CMS TOOLSFRAGMENTED INTERNAL PROCESSESFRAGMENTED DEVICES + PLATFORMS

Page 14: Adapting ourselves to adaptive content

A TALE OF TWO PUBLISHERS

14

Page 15: Adapting ourselves to adaptive content

15

Page 16: Adapting ourselves to adaptive content
Page 17: Adapting ourselves to adaptive content
Page 18: Adapting ourselves to adaptive content
Page 19: Adapting ourselves to adaptive content
Page 20: Adapting ourselves to adaptive content

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

20Paul Ford, Ftrain.com

Page 21: 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

21http://www.observer.com/2011/07/scott-dadich-ipad-conde-nast/?show=all

Page 22: Adapting ourselves to adaptive content

All I see is an entire organization screaming,

“WE WANT IT TO BE THE EIGHTIES GODDAMMIT.”

22Condé Nast Is Experiencing Technical Difficulties

Page 24: Adapting ourselves to adaptive content

CONTENT

PROVIDERS

MUSIC

PARTNERS

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

Page 27: Adapting ourselves to adaptive content

NPR NEWS IPHONE APP

27

Page 28: Adapting ourselves to adaptive content

NPR MOBILE WEB SITE

28

Page 29: Adapting ourselves to adaptive content

NPR ADDICT IPHONE APP

29

Produced by a public user, based entirely on the NPR API

Page 30: Adapting ourselves to adaptive content

NPR ON THE PUBLIC RADIO PLAYER

30

Page 31: Adapting ourselves to adaptive content

NPR ON WBUR

31

Page 32: Adapting ourselves to adaptive content

NPR ON MPR

32

Page 33: Adapting ourselves to adaptive content

NPR ON iGOOGLE

33

Page 34: Adapting ourselves to adaptive content

NPR IN iTUNES

34

Page 35: Adapting ourselves to adaptive content

NPR’S CMS

35

Page 36: Adapting ourselves to adaptive content

NPR’S API

36

Page 37: Adapting ourselves to adaptive content

BUSINESS VALUE?

37

Page 38: Adapting ourselves to adaptive content

38

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 39: Adapting ourselves to adaptive content

39

NPR PAGE VIEWS

43M

88M

Page 40: 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.

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, open sourced Android app and HTML5 site, some of which were turned around in a matter of weeks!

—Zach Brand, Senior Director Technology, NPR40

Page 41: Adapting ourselves to adaptive content

41

WHY ARE NEWS ORGANIZATIONS THE INNOVATORS?

Page 42: Adapting ourselves to adaptive content

42

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 43: Adapting ourselves to adaptive content

43

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 44: Adapting ourselves to adaptive content

THE FUTURE OF ADAPTIVE CONTENT

44

Page 45: Adapting ourselves to adaptive content

45

CONTENT

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 46: Adapting ourselves to adaptive content

REUSABLE CONTENT STORE

46

Page 47: Adapting ourselves to adaptive content

SemanticAtomized

47

Intelligent

Adaptive

Nimble Agile

Structured

Flexible

Page 48: Adapting ourselves to adaptive content

48

WHAT’S STOPPING US?

Page 49: Adapting ourselves to adaptive content

“BUT WE’VE ALWAYS RECYCLED THIS WAY!”

49

Page 50: Adapting ourselves to adaptive content

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

50Lisa Welchman, @lwelchman

Page 51: Adapting ourselves to adaptive content

51

PRINT

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 52: Adapting ourselves to adaptive content

52

WEB

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 53: Adapting ourselves to adaptive content

53

MOBILE

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 54: Adapting ourselves to adaptive content

THE MARRIAGE OF CONTENT AND FORM

54

Page 55: 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.

A semantic content publishing system, on the other hand, 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.

—Dan Willis55http://dswillis.com/uxcrank/?p=378

Page 56: Adapting ourselves to adaptive content

56http://www.flickr.com/photos/97867906@N00/5913915289/

RDFXML

DITAEXIFXMP

OWLAPI

Page 57: Adapting ourselves to adaptive content

57

IT’S NOT A TECHNOLOGY PROBLEM.IT’S A STRATEGY PROBLEM.WHICH MEANS IT’S A PEOPLE PROBLEM.

Page 58: Adapting ourselves to adaptive content

58

WHAT DO WE NEED TO GET THERE?

Page 59: Adapting ourselves to adaptive content

59

BETTER CMS WORKFLOWWRITE FOR THE CHUNK, NOT THE PAGEDEMYSTIFY METADATA

Page 60: Adapting ourselves to adaptive content

60

BETTER CMS WORKFLOW

Page 61: Adapting ourselves to adaptive content
Page 62: Adapting ourselves to adaptive content

CMS IS THE ENTERPRISE SOFTWARE THAT UX FORGOT

62

Page 63: Adapting ourselves to adaptive content

63

Page 64: Adapting ourselves to adaptive content

64

Page 65: Adapting ourselves to adaptive content

65

Page 66: Adapting ourselves to adaptive content

CONTEXTUAL INQUIRYUSER PERSONASUSER SCENARIOSTASK ANALYSISWORKFLOW MAPPINGCARD SORTINGCONTENT MODELINGITERATIVE PROTOTYPINGUSABILITY TESTINGANALYTICS DATA

66

Page 67: Adapting ourselves to adaptive content

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

Digital newsrooms have moved from shoveling to creating. Those two tasks require very different environments.

—Patrick Cooper, NPR

67http://www.poynter.org/how-tos/digital-strategies/134791/4-ways-content-management-systems-are-evolving-why-it-matters-to-journalists/

Page 68: Adapting ourselves to adaptive content

68

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

http://www.poynter.org/how-tos/digital-strategies/134791/4-ways-content-management-systems-are-evolving-why-it-matters-to-journalists/

Page 69: Adapting ourselves to adaptive content

69

WRITE FOR THE CHUNK, NOT THE PAGE

Page 70: Adapting ourselves to adaptive content
Page 71: Adapting ourselves to adaptive content

BLOBS vs. CHUNKS

71

Page 72: Adapting ourselves to adaptive content

NPR’S CMS

72

Page 73: Adapting ourselves to adaptive content

http://www.alistapart.com/articles/content-templates-to-the-rescue/ 73

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 74: Adapting ourselves to adaptive content

74

Input Templates

Content Model

DisplayStyles

Page 75: Adapting ourselves to adaptive content

75

Page 76: Adapting ourselves to adaptive content

76

Page 77: Adapting ourselves to adaptive content
Page 78: Adapting ourselves to adaptive content

TRUNCATION IS NOT A CONTENT STRATEGY

78

Page 79: Adapting ourselves to adaptive content

DEMYSTIFYING METADATA

79

Page 80: Adapting ourselves to adaptive content

METADATA PROGRAMMATICALLY BUILDS PAGES

80

Page 81: Adapting ourselves to adaptive content

81

Metadata is the new art direction.

Ethan Resnick, @studip101

Page 82: Adapting ourselves to adaptive content

METADATA SUPPORTS PERSONALIZED CONTENT

82

Page 83: Adapting ourselves to adaptive content

ABC Co.

Page 84: Adapting ourselves to adaptive content

METADATA HELPS PRIORITIZE CONTENT

84

Page 85: Adapting ourselves to adaptive content

85

Page 86: Adapting ourselves to adaptive content

USE MOBILE AS A WEDGE.

86

Page 87: Adapting ourselves to adaptive content

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

87Rachel Lovinger, @rlovinger

Page 88: Adapting ourselves to adaptive content

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

88

Page 89: Adapting ourselves to adaptive content

89

This approach of using structured content removes much of the requirement for

formatting tools in the CMS.

Rachel Andrew, Your WYSIWYG Editor Sucks

Page 90: Adapting ourselves to adaptive content

DESIGN WITH AND FORSTRUCTURED CONTENT.

90

Page 91: Adapting ourselves to adaptive content

91

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

Jeff Eaton, @eaton