Downloaded 906 times
Uploaded byKaren McGrane
Adapting Ourselves to Adaptive Content
The document discusses the challenges and strategies of managing adaptive content across multiple platforms, emphasizing the need to create content that is reusable and platform-independent. It highlights the importance of semantic content publishing systems and effective metadata in improving content workflows and user experience. Various examples from NPR illustrate the successful implementation of these concepts, showcasing the growth and flexibility achieved through their API and mobile strategy.
More Related Content
Similar to Adapting Ourselves to Adaptive Content
Adapting Ourselves to Adaptive Content
- 1. ADAPTING OURSELVES TO ADAPTIVE CONTENT @karenmcgrane
- 3. “ Fragmenting our contentacross different “device-optimized” experiences is a losing proposition, or at least an unsustainable one. —Ethan Marcotte Responsive Web Design
- 4. “ You can’t affordto 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
- 10. We’re about tousher in a golden age of PDFs on the iPad. Paul Ford, @ftrain
- 11. “ Existing art andproduction 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
- 12. All I seeis an entire organization screaming, “WE WANT IT TO BE THE EIGHTIES GODDAMMIT.” Condé Nast Is Experiencing Technical Difficulties
- 13. COPE: CREATE ONCE, PUBLISH EVERYWHERE COPE: Create Once, Publish Everywhere
- 14. C O N T E N T P R O V I D E R S M U S I C P A R T N E R S NPR, Open Content and API’s, O’Reilly Oscon 14
- 15. NPR.ORG NPR Digital Media Examples NPR, OpenCOPE and API’s, O’Reilly Oscon of Content
- 16. NPR.ORG PLAYER NPR Digital Media Examples of COPE
- 17.
- 18.
- 19. NPR ADDICT IPHONE APP Producedby a public user, based entirely on the NPR API
- 20. NPR ON THE PUBLICRADIO PLAYER
- 21.
- 22.
- 23.
- 24.
- 26.
- 27.
- 28.
- 29. 31,000 2010 iPAD ISSUE SALES 22,000 13,000 11,000 10,500 8,700 4,300 2,775 Sept. Nov. Sept. Nov. Sept. Nov. Sept. Nov.
- 30. NPR PAGE VIEWS 88 Million 43 Million
- 31. “ Over the lastyear, 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
- 32. “ The biggest impactthat 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!
- 33. Our goalis buildinga once isall together to have Bringing it to publish into Instead of Our aim ultimate and a workflow to flexibility and a cohesive workflow has product and distributetake a piece everywhere. we’rea realto trying for been able challenge to support, we’re of content and put —on 15 us. It’s been tough it flip that to build a different lot moreand still there’s a screens work.to workflow and a system have a very consistent look support these multiple and feel. design outputs: Adaptive Content.
- 34. THE FUTURE OF ADAPTIVECONTENT
- 35. Intelligent Flexible Structured Nimble Agile Adaptive Atomized Semantic
- 36. MOBILE WEB MOBILE WEBSITE APPS SOCIAL TABLET MEDIA APPS CONTENT MICROSITES PRINT BLOGS EMAIL INTRANET
- 37.
- 43.
- 47. WHY ARE NEWSORGANIZATIONS THE INNOVATORS?
- 48. 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. •Nut graf Lede: Lead, as in leading paragraph, usually the first sentence, or in some cases the first two Captions are photo headlines •Nutshell paragraph sentences, ideally 20-25 words in length. An Cutlines are the words (under the effective lead is a brief, sharp statement of the caption, if there is one) describing the •Summarizes the story's essential facts. photograph or illustration. story's content •Often bullet- Lorem ipsum dolor sit amet, consectetuer pointed adipiscing elit, sed diam nonummy nibh euismod •Sometimes set tincidunt ut laoreet dolore magna aliquam erat off in a box 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.
- 49. It’s scary tothink about your package devolved into different content elements. It takes imagination and understanding to take that apart. And courage. Sarah Chubb Sauvayre, Condé Nast
- 50. THE PRIMACY OFPRINT
- 54. Thinking about wherecontent will “live” on a “web page” is pretty 1999. Lisa Welchman, @lwelchman
- 55. MOBILE WEB MOBILE WEBSITE APPS SOCIAL TABLET MEDIA APPS PRINT MICROSITES PRINT BLOGS EMAIL INTRANET
- 56. MOBILE WEB MOBILE WEBSITE APPS SOCIAL TABLET MEDIA APPS WEB MICROSITES PRINT BLOGS EMAIL INTRANET
- 57. MOBILE WEB MOBILE WEBSITE APPS SOCIAL TABLET MEDIA APPS MOBILE MICROSITES PRINT BLOGS EMAIL INTRANET
- 58. MOBILE WEB MOBILE WEBSITE APPS SOCIAL TABLET MEDIA APPS CONTENT MICROSITES PRINT BLOGS EMAIL INTRANET
- 59. THE MARRIAGE OF CONTENTAND FORM
- 60. “ Traditional publishing andcontent management systems bind content to display and delivery mechanisms, which forces a recycling approach for multi-platform publishing. —Dan Willis
- 61. “ A semantic contentpublishing 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.
- 62. WHAT DO WENEED TO GET THERE?
- 63.
- 64. WRITE FOR THECHUNK, NOT THE PAGE DEMYSTIFY METADATA BETTER CMS WORKFLOW
- 68. TRUNCATION IS NOTA CONTENT STRATE...
- 70.
- 71.
- 72. Page Title Example: Widget-o-Rama: FancyWidget No. 5 PRODUCT DESCRIPTION—ANSWERS THE QUESTION “WHAT IS IT?” Product Name Product Line Short Guidelines: Two sentences. The product description should answer the questions Description “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 Example description: Widget-o-Rama’s FancyWidget product. 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. PRODUCT BENEFITS—ANSWERS THE QUESTION “WHY SHOULD I BUY IT?” Benefit/Feature Guidelines: Benefits are about the customer Pairs 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 Examples: specific benefit, followed by the feature or Reduces maintenance costs by up to 50% by features that make it possible. Use concrete replacing delicate gremlin studs with a robust spiral terms whenever you can. 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.
- 73. CSS Display Styles ADAPTIVE CONTENT Data Content Model Wrangling CMS CONTENT STRATEGY
- 74.
- 75.
- 76. Metadata is thenew art direction. Ethan Resnick, @studip101
- 77.
- 80.
- 81.
- 82. Content admins hateall the fields. But the reason they hate all the fields is the workflow is bad. Jason Pamental, @jpamental
- 83. CMS IS THEENTERPRISE SOFTWARE THAT UX FORGOT
- 87. CONTEXTUAL INQUIRY USER PERSONAS USERSCENARIOS TASK ANALYSIS WORKFLOW MAPPING CARD SORTING CONTENT MODELING ITERATIVE PROTOTYPING USABILITY TESTING ANALYTICS DATA
- 88. “ The happier peopleare, the better their content will be, the more content they’ll produce. —Patrick Cooper, NPR
- 89. “ Beautiful software, evenfor 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
- 90. USE MOBILE ASA WEDGE.
- 91. The more structureyou put into content the freer it will become. Rachel Lovinger, @rlovinger
- 92. SEPARATION OF CONTENT FROMDISPLAY. (FOR REAL THIS TIME.)
- 93. The future ofcontent management systems is in their ability to capture the content in a clean, presentation-independent way. Daniel Jacobson, NPR
- 94. DESIGN WITH ANDFOR STRUCTURED CONTENT.
- 95. I’ve never seenanyone regret having flexibility in how they deploy content. Jeff Eaton, @eaton
- 96.
Editor's Notes
- #2 One of the biggest problems facing our work is how to adapt to this proliferation of new devices. You’re going to see a lot of great presentations from people talking about how to deal with mobile: Ethan talking about responsive design next, Luke and Josh Clark tomorrow. I’m going to look at this from a content perspective, talk about what we need to do to get our content onto all these different devices.\n\n\n
- #3 I do a lot of work with publishers: magazines like The Atlantic, Fast Company, and The Week, and newspapers like the New York Times. I think the challenges that publishers face have a lot of relevance to every business that is struggling to create, manage, and gain business value from their content. Publishers are like the canary in the coal mine: they feel the pain more immediately, and they have to respond more quickly to advances in digital publishing.\n\n
- #4 Ethan frames the problem that we can’t expect to support different designs and different codebases for every single platform and device.\n
- #5 So if designers and developers are telling us that we can’t afford to develop multiple “device optimized” interfaces, content people are saying the same thing: we can’t afford to create content for a single platform. \n\nAs Nic Newman says here, the solution on the content side is to put more structure into your content objects so that they can be more effectively reused.\n\n[twitter]The Nimble report by @rlovinger of @razorfish is a prescient look at why publishers need more structured content. http://nimble.razorfish.com[/twitter]\n
- #6 NPR is America’s National Public Radio\n\nConde Nast is the large magazine publisher of titles like Vogue, the New Yorker, and Lucky. \n\nConde has invested heavily in developing custom apps for the iPad for some of their flagship titles like\n
- #7 \n
- #8 \n
- #9 \n
- #10 They are not just repurposing their content! They are repurposing the art direction!\n\nWhen the iPad first launched, I was talking about it with the great Paul Ford, formerly of Harpers, and he said: we’re about to usher in a golden age of PDFs on the iPad.\n
- #11 And maybe Conde Nast would be better of if that’s what they did. Instead, they’re investing in even more art direction, using their print staffers to create two custom layouts each month, one for portrait and one for landscape. \n\n[twitter]Why aren’t you reading @ftrain? If you like the internet, you’ll like this: http://www.ftrain.com/wwic.html[/twitter]\n
- #12 To me, this looks like an organization desperately clinging to what it knows best: believing that the art direction, the layout, the design, the production values are what will make them successful in digital. Or, as one commenter said,\n\n[twitter]More about Conde Nast's iPad strategy from the New York Observer: http://www.observer.com/2011/07/scott-dadich-ipad-conde-nast/[/twitter]\n
- #13 It’s like they are hearkening back to a time in the 1980s when print advertising rates were at an all time high, everyone had limos pick them up to take them to work, mid-afternoon a guy with would come through the aisle, pushing a cart loaded with cocaine.\n\nThe 80s are gone, and custom art-directed apps aren’t going to bring them back.\n
- #14 So, let’s contrast that strategy with how NPR has approached the problem. NPR has invested in something that’s not nearly as sexy as what Conde Nast is doing. It’s an API which supports something they call “COPE”: Create Once, Publish Everywhere. It’s the exact opposite direction: instead of investing time in custom layouts and art direction, they’re investing in true separation of content from form.\n\n[twitter]Fittingly, NPR shares information about its API and publishing strategy openly. For an overview: http://blog.programmableweb.com/2009/10/13/cope-create-once-publish-everywhere/[/twitter]\n
- #15 So, let’s contrast that strategy with how NPR has approached the problem. NPR has invested in something that’s not nearly as sexy as what Conde Nast is doing. It’s an API which supports something they call “COPE”: Create Once, Publish Everywhere. It’s the exact opposite direction: instead of investing time in custom layouts and art direction, they’re investing in true separation of content from form.\n\n[twitter]Fittingly, NPR shares information about its API and publishing strategy openly. For an overview: http://blog.programmableweb.com/2009/10/13/cope-create-once-publish-everywhere/[/twitter]\n
- #16 So, let’s contrast that strategy with how NPR has approached the problem. NPR has invested in something that’s not nearly as sexy as what Conde Nast is doing. It’s an API which supports something they call “COPE”: Create Once, Publish Everywhere. It’s the exact opposite direction: instead of investing time in custom layouts and art direction, they’re investing in true separation of content from form.\n\n[twitter]Fittingly, NPR shares information about its API and publishing strategy openly. For an overview: http://blog.programmableweb.com/2009/10/13/cope-create-once-publish-everywhere/[/twitter]\n
- #17 What this means is that they can easily take content, whether created in-house or provided by partners, and push it out through their API to an amazing variety of devices and platforms. \n\nSo here you can see the exact same story about Winnie The Pooh, which includes both text and audio, on:\n
- #18 \n
- #19 \n
- #20 \n
- #21 \n
- #22 \n
- #23 An iPhone app that offers streaming audio from more than 500 public radio stations streams across the United States.\n
- #24 WBUR in Boston\n
- #25 MPR in Minneapolis\n
- #26 \n
- #27 ITunes desktop app\n
- #28 TV browsing (via Xbox, for example)\nThis, perplexingly, also needs to be thought about under the guise of “mobile”\n
- #29 Made possible by a CMS that is set up to guide content creators through developing different sizes and formats for content, and that presumably people like using\n
- #30 And an API, which makes it possible to separate content from presentation. \n\nIt means that all the various websites and mobile websites and mobile apps and desktop apps that I just showed you can access this content, and then the designers for each platform make their own decisions about how to visually present it.\n
- #31 So, how well have each of these strategies paid off?\n
- #32 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #33 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #34 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #35 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #36 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #37 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #38 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #39 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #40 Compared with print editions that sell hundreds of thousands of copies every month, the Conde Nast iPad apps aren’t doing so well. The numbers released for Fall 2010 show consistent declines, and the fact that they haven’t released more positive numbers for 2011 suggests things haven’t gotten better.\n\nGlamour is often described as the most lucrative title within Condé Nast with 1.85 million subscribers and average newsstand sales of 453,707\n\nPotentially the numbers for the new Apple Newsstand will be better, but we’ll have to see.\n\n[twitter]All the numbers about Conde Nast's iPad issue sales, from Adweek: http://www.adweek.com/news/technology/breaking-down-cond-nasts-e-sales-133807[/twitter]\n
- #41 NPR, on the other hand, has seen a dramatic increase in the number of pages that get viewed, which presumably means a lot more people are engaging with it. In fact, they’ve seen their page views go up 80%.\n\n[twitter]Lots of stats about the success of NPR’s API in this presentation at the Wolfram Data Summit: http://www.slideshare.net/danieljacobson/npr-presentation-at-wolfram-data-summit-2010[/twitter]\n
- #42 The reason their page views have gone up 80%? They attribute it directly to their API. But more important, they’re saving time and money because they don’t have to do custom development so every new platform can access the content, which means that the time to design and launch each new app is much lower.\n\nI don’t tell you this story because I’m here touting APIs. In fact, I’m really afraid that someone is going to come up to me after this talk and ask for advice on implementing an API, and my response is going to be “I like cake.” There are other people here who are way smarter about actually doing this than I am.\n
- #43 I’m talking about this because understanding how structured content will give us more flexibility in the future is the key to understanding how we’re going to deal with this crazy multi-device landscape.\n\nNot because art direction and interaction design aren’t important. Because they ARE important.\n
- #44 [twitter]Conde Nast is seeking a cost-effective publishing model for a growing number of devices: http://paidcontent.co.uk/article/419-conde-nast-aims-to-unify-tablet-and-mobile-magazine-production/[/twitter]\n
- #45 [twitter]Conde Nast is seeking a cost-effective publishing model for a growing number of devices: http://paidcontent.co.uk/article/419-conde-nast-aims-to-unify-tablet-and-mobile-magazine-production/[/twitter]\n
- #46 [twitter]Conde Nast is seeking a cost-effective publishing model for a growing number of devices: http://paidcontent.co.uk/article/419-conde-nast-aims-to-unify-tablet-and-mobile-magazine-production/[/twitter]\n
- #47 [twitter]Conde Nast is seeking a cost-effective publishing model for a growing number of devices: http://paidcontent.co.uk/article/419-conde-nast-aims-to-unify-tablet-and-mobile-magazine-production/[/twitter]\n
- #48 [twitter]Conde Nast is seeking a cost-effective publishing model for a growing number of devices: http://paidcontent.co.uk/article/419-conde-nast-aims-to-unify-tablet-and-mobile-magazine-production/[/twitter]\n
- #49 [twitter]Conde Nast is seeking a cost-effective publishing model for a growing number of devices: http://paidcontent.co.uk/article/419-conde-nast-aims-to-unify-tablet-and-mobile-magazine-production/[/twitter]\n
- #50 [twitter]Conde Nast is seeking a cost-effective publishing model for a growing number of devices: http://paidcontent.co.uk/article/419-conde-nast-aims-to-unify-tablet-and-mobile-magazine-production/[/twitter]\n
- #51 So, what is it going to take to make this happen? And what will the future look like?\n
- #52 The future is old. People, particularly in the tech comm community have been talking about structured content for years.\n\n[twitter]Ann Rockley is a passionate advocate for structured content, what she calls “Intelligent Content.” Go buy her new book: http://www.amazon.com/Managing-Enterprise-Content-Unified-Strategy/dp/032181536X/ref=ntt_at_ep_dpt_1[/twitter]\n
- #53 Whatever you call it, what it means is that we have a flexible, structured base of content that can be used to publish out to whatever channel you need to: web, mobile, tablets, even intranets. Even print.\n\n[twitter]We should be platform-agnostic for content, platform-aware for user experience, says @stephenhay. http://www.slideshare.net/stephenhay/structured-content-first[/twitter]\n
- #54 What I like to call a “reusable content store.”\n\n[twitter]We’re moving toward a web that’s more fluid, less fixed, and on a multitude of devices, says @sara_ann_marie: http://www.alistapart.com/articles/future-ready-content/[/twitter]\n\n
- #55 \n
- #56 \n
- #57 \n
- #58 \n
- #59 \n
- #60 \n
- #61 \n
- #62 \n
- #63 \n
- #64 \n
- #65 \n
- #66 \n
- #67 \n
- #68 \n
- #69 \n
- #70 \n
- #71 Why is it NPR that is innovating on developing an API? Why is it the Boston Globe that can launch an innovative responsive design site? Is it a coincidence that it’s news organizations, and not other types of publishers?\n
- #72 News organizations already have structured content. They have existing frameworks for thinking about how to write in chunks that pre-date the web. They even have their own names for these chunks: hed, dek, lede, nut graf. They have people who already think this way, they are taught to do this, they know how to write like this.\n\n\n
- #73 News organizations already have structured content. They have existing frameworks for thinking about how to write in chunks that pre-date the web. They even have their own names for these chunks: hed, dek, lede, nut graf. They have people who already think this way, they are taught to do this, they know how to write like this.\n\n\n
- #74 News organizations already have structured content. They have existing frameworks for thinking about how to write in chunks that pre-date the web. They even have their own names for these chunks: hed, dek, lede, nut graf. They have people who already think this way, they are taught to do this, they know how to write like this.\n\n\n
- #75 News organizations already have structured content. They have existing frameworks for thinking about how to write in chunks that pre-date the web. They even have their own names for these chunks: hed, dek, lede, nut graf. They have people who already think this way, they are taught to do this, they know how to write like this.\n\n\n
- #76 News organizations already have structured content. They have existing frameworks for thinking about how to write in chunks that pre-date the web. They even have their own names for these chunks: hed, dek, lede, nut graf. They have people who already think this way, they are taught to do this, they know how to write like this.\n\n\n
- #77 News organizations already have structured content. They have existing frameworks for thinking about how to write in chunks that pre-date the web. They even have their own names for these chunks: hed, dek, lede, nut graf. They have people who already think this way, they are taught to do this, they know how to write like this.\n\n\n
- #78 For most companies, figuring out how to structure their content is freakishly hard. It’s scary. \nIt’s painful to think about what it means to dismember your beautifully integrated package into little content chunks.\nBut if we’re going to survive in the future, we have to do it. It will take imagination and insight and courage.\n\nSo I had a dinner, I had dinner with some representatives from a major magazine publisher a couple weeks ago.  And over the course of our conversation we talked about their organizational challenges, you know, the difficulty that they have in explaining how digital works to their existing staffers, the challenges that they face in their internal org structure, their internal workflows, their internal processes. And listening to them talk it was like a lightbulb went off over my head, like it hit me so hard.  It wasn't that I hadn't thought of this before, but it was like it really drove home the problem, which is that they are still thinking about writing for print.  Their whole organization, everything about it is figuring out how they can write for print, and then take that print content and shove it onto a webpage, and then figuring out how they can take that content and shove it into a mobile device. Everything that they're thinking about, all of their processes, all of their goals, all of their values are still print, print, print, print, print.  Their entire mindset, their entire value system, their entire workflow, their entire culture is all still organized around print.  \n
- #79 They are still thinking about writing for print, and then trying to figure out how to take “print” content and get it onto other devices. Their entire mindset, values system, workflow, and culture all are rooted in the notion that what matters is writing for print.\n\n[twitter]Print, the only mode of content delivery for so long, has become the mode of content creation as well. http://scholarlykitchen.sspnet.org/2010/05/24/when-did-print-become-an-input/[/twitter]\n
- #80 The NY Times, when they launched their new Sunday Review section recently, figured out what they wanted to do for the print edition, and then got te digital team involved late in the game, to figure out how to put it online.\n\n\n
- #81 And it’s easy to be judgmental about these dinosaurs, right? I mean, everyone can look 5 or 10 years out and know that print isn’t going to win this one. And so it’s easy to feel superior, like we in the digital side wouldn’t fall into the same trap. Right? RIGHT?\n\n\n
- #82 \n
- #83 \n
- #84 \n
- #85 \n
- #86 \n
- #87 \n
- #88 \n
- #89 Well of course we are! We moved from letting content creators think about where something would live in a book or a document to letting them think about where it would live on a webpage. And, as Lisa Welchman says, thinking about where something “lives” on a “web page” is pretty 1999.\n\n
- #90 So, when I talk about adaptive content, a reusable content store, I don’t mean that we start with print content and then push it out to other platforms.\n\n
- #91 But I ALSO don’t mean we start with web pages and then figure out how to reformat them for different screens.\n
- #92 And no, I don’t even mean we start with mobile first and then figure out how to progressively enhance our content.\n\n
- #93 When we say start with content first, what we mean is start with content. Clean, well structured, flexible content that can be used across a variety of channels and platforms and contexts, because it was planned that way from the start. Because it wasn’t created with any one channel in mind.\n\n[twitter]Embrace the unpredictable, fluid, fragile nature of the web, and design from the content out, says @markboulton: http://www.netmagazine.com/interviews/mark-boulton-designing-websites-using-content-out[/twitter]\n
- #94 Now to do that, we have to deal with a vexing problem, which is the tight coupling of content with form.\nWeb standards has made great strides in trying to separate content from form, but we have to get to the root of the problem, which is that we have \nVertically integrated CMS\nCombines content management with content publishing\nThat’s the reason people need an API\n
- #95 \n
- #96 [twitter]The better solution is to structure content only once, but in a way that it can be used anywhere, says @uxcrank. http://dswillis.com/uxcrank/?p=378[/twitter]\n
- #97 So, what has to change to make this happen? 3 things.\n
- #98 \n
- #99 This is the outline for the next section\nWhat do I mean by writing for the chunk?\n
- #100 This is the outline for the next section\nWhat do I mean by writing for the chunk?\n
- #101 This is the outline for the next section\nWhat do I mean by writing for the chunk?\n
- #102 \n
- #103 \n
- #104 \n
- #105 \n
- #106 \n
- #107 Now, Amazon actually has structured content! They have their stuff broken into fields. \nBut, the problem is that it isn’t written for reuse, it’s written for a web page and then crammed onto a mobile device.\nBulleted list\n73 words on this screen, and 23 of them are repeating the product title. 5 of them are “make memories and share joy.” I need you to sell me a camera, not on the benefits of photography.\nOh, look, the product name. Again.\nEven these headings, which are okay in the context of a web page, start to seem meaningless when used as navigation. What’s the difference between all these things.\nWant to be clear about this: This is Amazon’s PRODUCT PAGE.\nThis is one of the most intensely designed and tested pages on the internet.\nAnd on mobile, it’s like we just asked the robots to shovel in text without thinking about it.\n
- #108 Now, Amazon actually has structured content! They have their stuff broken into fields. \nBut, the problem is that it isn’t written for reuse, it’s written for a web page and then crammed onto a mobile device.\nBulleted list\n73 words on this screen, and 23 of them are repeating the product title. 5 of them are “make memories and share joy.” I need you to sell me a camera, not on the benefits of photography.\nOh, look, the product name. Again.\nEven these headings, which are okay in the context of a web page, start to seem meaningless when used as navigation. What’s the difference between all these things.\nWant to be clear about this: This is Amazon’s PRODUCT PAGE.\nThis is one of the most intensely designed and tested pages on the internet.\nAnd on mobile, it’s like we just asked the robots to shovel in text without thinking about it.\n
- #109 Now, Amazon actually has structured content! They have their stuff broken into fields. \nBut, the problem is that it isn’t written for reuse, it’s written for a web page and then crammed onto a mobile device.\nBulleted list\n73 words on this screen, and 23 of them are repeating the product title. 5 of them are “make memories and share joy.” I need you to sell me a camera, not on the benefits of photography.\nOh, look, the product name. Again.\nEven these headings, which are okay in the context of a web page, start to seem meaningless when used as navigation. What’s the difference between all these things.\nWant to be clear about this: This is Amazon’s PRODUCT PAGE.\nThis is one of the most intensely designed and tested pages on the internet.\nAnd on mobile, it’s like we just asked the robots to shovel in text without thinking about it.\n
- #110 Now, Amazon actually has structured content! They have their stuff broken into fields. \nBut, the problem is that it isn’t written for reuse, it’s written for a web page and then crammed onto a mobile device.\nBulleted list\n73 words on this screen, and 23 of them are repeating the product title. 5 of them are “make memories and share joy.” I need you to sell me a camera, not on the benefits of photography.\nOh, look, the product name. Again.\nEven these headings, which are okay in the context of a web page, start to seem meaningless when used as navigation. What’s the difference between all these things.\nWant to be clear about this: This is Amazon’s PRODUCT PAGE.\nThis is one of the most intensely designed and tested pages on the internet.\nAnd on mobile, it’s like we just asked the robots to shovel in text without thinking about it.\n
- #111 Now, Amazon actually has structured content! They have their stuff broken into fields. \nBut, the problem is that it isn’t written for reuse, it’s written for a web page and then crammed onto a mobile device.\nBulleted list\n73 words on this screen, and 23 of them are repeating the product title. 5 of them are “make memories and share joy.” I need you to sell me a camera, not on the benefits of photography.\nOh, look, the product name. Again.\nEven these headings, which are okay in the context of a web page, start to seem meaningless when used as navigation. What’s the difference between all these things.\nWant to be clear about this: This is Amazon’s PRODUCT PAGE.\nThis is one of the most intensely designed and tested pages on the internet.\nAnd on mobile, it’s like we just asked the robots to shovel in text without thinking about it.\n
- #112 Now, Amazon actually has structured content! They have their stuff broken into fields. \nBut, the problem is that it isn’t written for reuse, it’s written for a web page and then crammed onto a mobile device.\nBulleted list\n73 words on this screen, and 23 of them are repeating the product title. 5 of them are “make memories and share joy.” I need you to sell me a camera, not on the benefits of photography.\nOh, look, the product name. Again.\nEven these headings, which are okay in the context of a web page, start to seem meaningless when used as navigation. What’s the difference between all these things.\nWant to be clear about this: This is Amazon’s PRODUCT PAGE.\nThis is one of the most intensely designed and tested pages on the internet.\nAnd on mobile, it’s like we just asked the robots to shovel in text without thinking about it.\n
- #113 Now, Amazon actually has structured content! They have their stuff broken into fields. \nBut, the problem is that it isn’t written for reuse, it’s written for a web page and then crammed onto a mobile device.\nBulleted list\n73 words on this screen, and 23 of them are repeating the product title. 5 of them are “make memories and share joy.” I need you to sell me a camera, not on the benefits of photography.\nOh, look, the product name. Again.\nEven these headings, which are okay in the context of a web page, start to seem meaningless when used as navigation. What’s the difference between all these things.\nWant to be clear about this: This is Amazon’s PRODUCT PAGE.\nThis is one of the most intensely designed and tested pages on the internet.\nAnd on mobile, it’s like we just asked the robots to shovel in text without thinking about it.\n
- #114 Now, Amazon actually has structured content! They have their stuff broken into fields. \nBut, the problem is that it isn’t written for reuse, it’s written for a web page and then crammed onto a mobile device.\nBulleted list\n73 words on this screen, and 23 of them are repeating the product title. 5 of them are “make memories and share joy.” I need you to sell me a camera, not on the benefits of photography.\nOh, look, the product name. Again.\nEven these headings, which are okay in the context of a web page, start to seem meaningless when used as navigation. What’s the difference between all these things.\nWant to be clear about this: This is Amazon’s PRODUCT PAGE.\nThis is one of the most intensely designed and tested pages on the internet.\nAnd on mobile, it’s like we just asked the robots to shovel in text without thinking about it.\n
- #115 The idea that we can just show the first few lines of what we put on a desktop site is foolish. We have to get people writing for reuse and creating smaller content elements.\n
- #116 The problem is we have CMSes that permit — encourage — creating undifferentiated blobs of content. \nWe let people get away with having a “Microsoft Word-like” interface” with a WSIWYG toolbar. \nThis prevents people from creating content structures and couples content with form. \nA page created with a CMS like this will look exactly the way you want it to... in the context you created it for.\n\n[twitter]Your WYSIWYG editor does indeed suck. @rachelandrew tells it like it is: http://www.rachelandrew.co.uk/archives/2011/07/27/your-wysiwyg-editor-sucks/[/twitter]\n
- #117 To me, this is the war between blobs of undifferentiated content, and chunks of well structured content.Support the chunks! Don’t let the blobs win!\n
- #118 Structured content is made possible by a CMS that is set up to guide content creators through developing different sizes and formats for content, and that presumably people like using\n
- #119 One thorny problem is that for initial content creation, we often have an offline step.\nThis is an example taken from Erin Kissane’s ALA article on content templates, which are used to help gather content from people in a business. \nEven if we’re doing a great job in soliciting well structured content, it’s not always the case that these fields make it into the CMS. The CMS might take all this hard work of chunking and store it as a blob.\n\n[twitter]Content templates can help improve consistency across the website, says @kissane: http://www.alistapart.com/articles/content-templates-to-the-rescue/[/twitter]\n
- #120 TRANSITION:\nThings have changed, but the more they change, the more they stay the same.\nContent strategy reminds me of nothing so much as the early days of IA\nHelpful to remember a couple of things that we did right, things that are happening right now with CS.\n
- #121 When I talk about metadata, I mean it in the broadest possible sense. \nSecond thing we have to do is make metadata seem sexy. Okay, if not sexy, then at least not so scary.\nExplain to people why they need to add extra fields to their content, or extra markup for semantic tags.\n
- #122 Get people to wrap their heads around how to use metadata and business rules to build pages dynamically\nWhen people go from custom crafting a landing page\nTo being told that now, the landing page will build itself\nIt’s confusing, hard to wrap your heads around\n
- #123 The best summation of this concept comes from a guy named Ethan Resnick, who explained “Metadata is the new art direction.” \n\nWhat this means is that the art of constructing pages or sites or apps is now not just about making custom designed layouts. It’s about figuring out how to to use logic, business rules, search queries and metadata to build dynamically generated pages. \n\n[twitter]Use structured content and rule-based art direction for multi-platform styling, says @studip101: http://www.mymorguefile.com/blog/ruleBasedArtDirection.html[/twitter]\n
- #124 One of the challenges that we have in thinking about different devices and platforms\nMaking good decisions about how to prioritize information: what’s important, and what’s not?\nHow to handle the juxtaposition of content on different screens\nWith editorially generated metadata, we can get some insights about importance\n
- #125 Guardian has dynamically generated topic pages\nMartin Belam said that one problem they had was that the main story couldn’t just be the most recent\nYou’d wind up with random stuff there\nSo they had to start creating editorial priorities, and now the top story is selected via an algorithm that looks at both importance and recency\n
- #126 We’ve been talking a lot about how structured content can support different device contexts\nWhat’s really exciting is that if we learn how to write more structured content, create more flexible content chunks\nThen we can actually deliver on the promise of personalization\nWe’ve been talking about that forever, when I first heard about it my immediate thought was “well who’s going to write all that text?”\nAdvertising is way ahead of us on this, we can do better.\n
- #127 If we’re going to deliver on this promise, we need better CMS interfaces.\nThe future of mobile, the future of personalization, the future of content\nAll runs through the future of better content management.\n\nMost of my best insights about where this field needs to go come from me looking back on times in my career where I’ve screwed up. In this case, I’m working for a major magazine conglomerate on a number of projects, including redesigns of many of their properties, and putting in a new CMS. I was leading the UX team for the engagement, and I would sit in all these executive presentations in the fancy conference room. The executives would sit over here, and I’d outline my vision for the new user experience, and the projector screen was over here, and we’d show them what that would look like. \n
- #128 Creating structured content means having a bunch of fields for chunks and metadata in the interface.\nPeople bitch about this. They hate it. They beg for a blob and a WYSIWYG toolbar.\nThe solution isn’t to give in and make it more like Microsoft Word.The solution is to fix the CMS workflow problems.\n[twitter]Baby got backend: content administrators are users too! My talk with @eaton about improving the author experience. http://www.archive.org/details/drupalconchi_day2_baby_got_backend[/twitter]\n
- #129 UX would never be content to deliver software, even enterprise software, that wasn’t designed around the user.\nWell, for a CMS, the user is the content creator, and we need to do better.\n\nBecause, see, if you are in the business of creating content — and these days, who isn’t? — then the efficiency of your content workflow directly contributes to value for your business. \n
- #130 Do you know anyone who’s looking at analytics data on the performance of their CMS? I don’t.\nIf you were running an ecommerce site, you would optimize the hell out of those workflows. Delays, dropoffs, timeouts, errors: all result in lost revenue.\nIf you're a content-focused business, your content workflow is like an ecommerce workflow. And we have to start doing a better job of designing CMS interfaces for the people who use them.\n\n
- #131 This means we need to evaluate potential CMSes based on more than technical architecture, feature checklists, more than just the system requirements, security requirements and support requirements.\n
- #132 We have to stop talking about “usability” in CMSes as being about having a WYSIWYG toolbar, cute interface widgets, or an attractive font and color palette. Those things are nice, but true usability comes from understanding the complexity of the workflow: how the content is structured, what metadata is in place, and how pages get built dynamically based off business rules.\n
- #133 We have all kinds of tools in our UX toolkit that we can put to work on designing better content management interfaces and workflows.\n
- #134 I’m not saying we need to do this just because I care about the people who create content — though I do, I want them to be happy.\n
- #135 I’m saying this because if you give people better tools to use, if you remove the pain points from their daily workflow, they will do better work. They will create more and better content. And that means value to the business.\n\n[twitter]CMS requires continual investment, development. No matter how small or large your org is, your CMS has to evolve. http://www.poynter.org/how-tos/digital-strategies/134791/4-ways-content-management-systems-are-evolving-why-it-matters-to-journalists/[/twitter]\n
- #136 Not writing for mobile\nNot writing for web\nNot writing for print\nWriting flexible, adaptive, reusable content\n
- #137 Not constraining, freeing.\nFreed up to appear on a variety of devices.\nYOU as designers will be freer to make good design decisions that are the right ones for the platform\nBecause you won’t be repurposing a design from print, or a design from the web\nYou’ll be working off of a content base and then making the right design decisions.\n
- #138 You want this. I want this. We need this.\n
- #139 Get the formatting out of the CMS. Better designed CMS interfaces and workflows will make it possible for us to have clean, well-chunked content, not blobs of text with formatting mixed in. \n\nThe future of design that supports different platforms is better CMS.\n\n[twitter]Web content management is for losers: http://jonontech.com/2009/12/16/visions-of-jon-wcm-is-for-losers/[/twitter]\n
- #140 Ongoing conversations about how to structure content and what that means for design. \nHow do semantic tags relate to styles? To different interactions? How do you art direct with metadata?\n[twitter]Start with the structure, not the words, to design for fluidity, says @markboulton: http://www.markboulton.co.uk/journal/comments/structure-first-content-always[/twitter]\n
- #141 I know there’s sometimes the sense that content is somebody else’s problem.\nThat the CMS is a black box that you’d rather not look inside.\nWhat I hope you can see is that we all need to care about this,\nbecause if our designs are going to adapt across different platforms, our content has to too.\n
- #142 [twitter]Want more from me on the subject of adaptive content? Check out my roundup of links, interviews and presentations: http://karenmcgrane.com/2011/12/14/mobile-content-strategy/[/twitter]\n