content first cope made easy
DESCRIPTION
Although NPR socialised the COPE (Create Once, Publish Everywhere) acronym, the concept has been around for a couple of decades. There are two basic COPE variants, which work in very different ways. Learn the differences and application for each type, in five easy minutes. Presented as a Lightning Talk at Together London, Feb 2014.TRANSCRIPT
Content First: COPE Made Easy
*The explanation, not the implementation
*
Rahel Anne BailieIntentionalDesign.ca@rahelab
What is COPE?
CreateOncePublishEverywhere
FindabilityThere’s what you see. And then… There’s what search engines see.
Know which content is right for each user
Personalisation
Different users, different keys
Multiple delivery channels
Tablet Tap the X…
eBook (Uh, figure it out for yourself…)
Phone or or
Laptop Press Escape…
Omni-channel experience• Seamless approach
to multi-channel customer experience
• Also called conversational marketing
OK, got it. So how do you COPE?
There are two basic ways, but first …• Use semantic
structure for your content.
• Write for a COPE environment.
• Know your tech.
Structure to COPEReturning an ItemYou can return any item within thirty days. 1. Pack the the item in its
original packaging/2. Address the box to
[address]Note: Postage and packing costs are your responsibility.
<Title>Text here</title><ShortDesc>Text here </shortdesc><Step>
<Cmd>Text here</cmd></step><Step>
<Cmd>Text here</cmd></step><Note>Text here</note>
<p>Get your item soon.</p>
<p>Standard shipping and handling charges apply.</p>
<p>Or get your item sooner with US Postal Express.</p>
<p>Get your item soon.</p>
<p=AU>Standard postage and handling rates apply.</p>
<p=UK>Standard postage and packaging rates apply.</p>
<p>=US,CA>Standard shipping and handling rates apply.</p>
<p>Or get your item sooner with [RAP-express service].</p>
Write to COPE
Specific to United States Varied for 3 more markets
Know your tech
• Technical standards• What are the applicable content standards?• Which one ones should we use?
• Technology choices• What are the right choices?• Do we have the right ones?• Do we customize or trade up?
Two ways toward a COPE architecture
Method 1: Technology driven“Baked”
• Developer codesrules into WCMS.
• Author enters content into forms.
• CMS delivers content as per rules.
Method 2: Author driven“Fried”
• Author creates content components.
• CCMS manages components.
• Content transformed for output as per rules.
Method 1My view
Public view
Method 1
Method 1
Presentation
AnalyticsHTML editorDatabaseStorageSecurity
Method 1
Advantages• Easy for authors
• Can use common content management software
Disadvantages• Brittle: rules are “baked in”
• Depend on developers to customize or, later, make changes
• Can be costly and complex to change
Two ways toward a COPE architecture
Method 1: Technology driven“Baked”
• Developer codesrules into WCMS.
• Author enters content into forms.
• CMS delivers content as per rules.
Method 2: Author driven“Fried”
• Author creates content components.
• CCMS manages components.
• Content transformed for output as per rules.
Method 2
Method 2
EditorXML authoringTransclusionRepository (interface, metadata)Database
Method 2
EditorXML authoringTransclusionRepository (interface, metadata)Database
Method 2
Advantages• Agility: content can be “fried”
• Authors have more control
Disadvantages• Authors need writing
discipline
• Authors need to understand technical side of content
• Need specialty software