Adapting ourselves to adaptive content

68
ADAPTING OURSELVES TO ADAPTIVE CONTENT MobX @karenmcgrane

Transcript of Adapting ourselves to adaptive content

Page 1: Adapting ourselves to adaptive content

ADAPTING OURSELVES TO ADAPTIVE CONTENT

MobX@karenmcgrane

Page 2: Adapting ourselves to adaptive content

2

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, BBCNimble Report, http://nimble.razorfish.com

Page 5: Adapting ourselves to adaptive content

5

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

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

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

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

43M

88M

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

THE FUTURE OF MOBILE IS STRUCTURED CONTENT

Page 34: Adapting ourselves to adaptive content

CONTENT

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 35: Adapting ourselves to adaptive content

REUSABLE CONTENT STORE

Page 36: Adapting ourselves to adaptive content

THE PRIMACY OF PRINT

Page 37: Adapting ourselves to adaptive content

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

Lisa Welchman, @lwelchman

Page 38: Adapting ourselves to adaptive content

PRINT

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 39: Adapting ourselves to adaptive content

WEB

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 40: Adapting ourselves to adaptive content

MOBILE

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

Page 41: Adapting ourselves to adaptive content

CONTENT

EMAIL

INTRANET

SOCIAL MEDIA

MICROSITES

MOBILE WEBWEBSITE

PRINT

TABLET APPS

MOBILE APPS

BLOGS

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

http://dswillis.com/uxcrank/?p=378

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

http://dswillis.com/uxcrank/?p=378

Page 44: Adapting ourselves to adaptive content

WHAT DO WE NEED TO GET THERE?

Page 45: Adapting ourselves to adaptive content

WRITE FOR THE CHUNK, NOT FOR THE PAGEDEMYSTIFY METADATABETTER CMS WORKFLOW

Page 46: Adapting ourselves to adaptive content

46

Page 47: Adapting ourselves to adaptive content

47

Page 48: Adapting ourselves to adaptive content
Page 49: Adapting ourselves to adaptive content

TRUNCATION IS NOT A CONTENT STRATEGY

Page 50: Adapting ourselves to adaptive content
Page 51: Adapting ourselves to adaptive content

BLOBS vs. CHUNKS

Page 52: Adapting ourselves to adaptive content

DEMYSTIFYING METADATA

Page 53: Adapting ourselves to adaptive content

METADATA PROGRAMMATICALLY BUILDS PAGES

Page 54: Adapting ourselves to adaptive content

Metadata is the new art direction.

Ethan Resnick, @studip101

Page 55: Adapting ourselves to adaptive content

METADATA HELPS PRIORITIZE CONTENT

Page 56: Adapting ourselves to adaptive content
Page 57: Adapting ourselves to adaptive content

BETTER CMS WORKFLOW

Page 58: Adapting ourselves to adaptive content

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

is the workflow is bad.

58Jason Pamental, @jpamental

Page 59: Adapting ourselves to adaptive content

CMS IS THE ENTERPRISE SOFTWARE THAT UX FORGOT

Page 60: Adapting ourselves to adaptive content
Page 61: 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

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

Page 62: Adapting ourselves to adaptive content

USE MOBILE AS A WEDGE.

Page 63: Adapting ourselves to adaptive content

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

Rachel Lovinger, @rlovinger

Page 64: Adapting ourselves to adaptive content

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

Page 65: 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 66: Adapting ourselves to adaptive content

DESIGN WITH AND FORSTRUCTURED CONTENT.

Page 67: Adapting ourselves to adaptive content

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

Jeff Eaton, @eaton