create once publish everywhere anytime
DESCRIPTION
The future of web content management: - Web content: back to the future - Is your content management system future-ready? - Our take on adaptive content management: Novius OSTRANSCRIPT
1/43#dilyon25
Create OncePublish Everywhere… AnytimeThe future of web content management
Antoine LefeuvreCIO – Novius
@jiraisurfer – novius-os.org
2/43
#dilyon25
Web content: back to the future
Is your content management system future-ready?
Our take on adaptive content management: Novius OS
Contents
3/43
#dilyon25
Interfaces fly …
Credits: Google, Amstrad, Tobii, DoCoMo, Nintendo, Microsoft, Corning, Xerox & Apple (©)
4/43
#dilyon25
… content remain.
Credits: Amazon, Simon & Schuster, Wikipedia, A List Apart (©)
5/43
#dilyon25
Jonathan Stark, #bdconf (2012)
Smart content: you can’t have layout specific information in
your content.
We don’t know what the target device will be so we need to be
presentation agnostic.
6/43
#dilyon25
Responsive design, the solution?
Credits: Site Boston Globe par Ethan Marcotte, Filament Group, Upstatement and internal team (©). Graphic by Antoine Lefeuvre, Grant Hutchinson, responsivedesign.ca (CC).
7/43
#dilyon25
8/43
#dilyon25
Tim Berners-Lee, Long Live the Web (2010)
“The primary design principle underlying the Web’s usefulness and growth is universality. […]
And it should be accessible from any kind of hardware that can connect to the Internet.”
9/43
#dilyon25
You cannot test all possibilities
(©)
Credits: Anna Debenham for A List Apart (©).
10/43
#dilyon25
Andy Hume (2011)
“The web is responsive on its own—by default. ”
11/43
#dilyon25
So why is it our starting point?
Credits: Adobe (©).
12/43
#dilyon25
Credits: Andrea Balzano on Flickr (CC).
13/43
#dilyon25
John Allsopp, The Dao of Web Design (2000)
“The control which designers know in the print medium, and often desire in the web medium, is simply a function of the limitation of the printed page.
We should embrace the fact that the web doesn’t have the same
constraints, and design for this flexibility.”
14/43
#dilyon25
A designer must know the raw material
Credits: Subduction desk, Paul Venaille (©). Credits: El Naturalista (©).
15/43
#dilyon25
The web is made of code
16/43
#dilyon25
Design for flexibility = content without form?
17/43
#dilyon25
Design for flexibility = another form
Credits: Nicolas Torres pour WD Friday (©).
18/43
#dilyon25
Design for flexibility = another form
Credits: Novius for MS, Samatha Warren for The Examiner (©).
19/43
#dilyon25
Future-Friendly Manifesto
Acknowledge and embrace unpredictability.Think and behave in a future-friendly way.Help others do the same.
1.
2.
3.
20/43
#dilyon25
Web content: back to the future
Is your content management system future-ready?
Our take on adaptive content management: Novius OS
Contents
21/43
#dilyon25
Brad Frost (2011)
“Get your content ready to go anywhere because it’s going to
go everywhere.”
22/43
#dilyon25
Separate content and form (front end)
Credits: V G La Rosa, A Lefeuvre (CC).
23/43
#dilyon25
Separate content and form (back end)
24/43
#dilyon25
Daniel Jacobson,Create Once Publish Everywhere (2009)
“Build content management systems (CMS), not web publishing tools (WPT).”
25/43
#dilyon25
Web Publishing Tool
26/43
#dilyon25
Content Management System
Credits: Daniel Jacobson pour NPR (©).
27/43
#dilyon25
Content Management System
28/43
#dilyon25
Web content: back to the future
Is your content management system future-ready?
Our take on adaptive content management: Novius OS
Contents
29/43
#dilyon25
Why a new CMSA CMS which orchestrates content and embraces the adaptable nature of the web.
User experience: are users ready to create presentation agnostic content?
Our mission: bring users to Create Once Publish Everywhere, aim for a smooth learning curve.
Information layer naturally fed with pages, blog posts, customer-specific databases …
30/43
#dilyon25
Novius OS – COPE CMS
Credits: Novius (©).
31/43
#dilyon25
Novius OS – COPE CMS
Credits: Novius (©).
32/43
#dilyon25
Novius OS – COPE CMS
33/43
#dilyon25
Test case: From a customer-specific database to a blog post, and on to Twitter
View the demo (next slide)and move on to slide 35
for further details
34/43
#dilyon25
Content nuggetsFor every ape, the Monkey application shares a content nugget with the OS. Why “nugget”? Small and valuable: a piece of content small enough to be re-used, yet meaningful.
35/43
#dilyon25
Content nuggetsKoko's content nugget, free of any presentation and ready to be shared.
36/43
#dilyon25
Data catchersThe OS - the conductor - now asks: “I've got this content nugget, who can do something with it?” The applications equipped with data catchers answer.
37/43
#dilyon25
Data catchersThe Blog application catches the Monkey content nugget and, voilà, a post created in less than a minute. Just the time to turn the initial nugget into a news piece.
38/43
#dilyon25
Let's keep flowing!Your content won't stop here. From the blog post is extracted a new content nugget. A nugget looking to be caught.
39/43
#dilyon25
Let's keep flowing!A hashtag added and this nugget is now a tweet.
40/43
#dilyon25
1. From a customer- specific database 2. To a
blog post
3. And on to Twitter
41/43
#dilyon25
The road ahead of usThe current version is an early version (0.1). Much is to come!
Along the Media Centre will be added a Content Centre to centralise content nuggets.
New data-catcher-equipped applications: better social media support, SEO, SMO, emailing, etc.
Our long-term goal: provide users with one single tool to create web content and publish it on any channel, present or future.
42/43#dilyon25
Thank you!Questions and comments are welcome.
Antoine LefeuvreCIO – Novius
@jiraisurfer – novius-os.org
43/43
#dilyon25
Sources and resourcesJonathan Stark, Breaking Development: The Revolution Will Not Be Televised, notes by Luke Wroblewski http://www.lukew.com/ff/entry.asp?1629
Tim Berners-Lee, Long Live the Web: A Call for Continued Open Standards and Neutrality, http://www.scientificamerican.com/article.cfm?id=long-live-the-web
Anna Debenham, Testing Websites in Game Console Browsers, http://www.alistapart.com/articles/testing-websites-in-game-console-browsers/
Andy Hume, Responsive by default, http://blog.andyhume.net/responsive-by-default/
John Allsopp, A Dao of Web Design, http://www.alistapart.com/articles/dao/
Nicolas Torres, CSS et Mobile First : procéder par amélioration progressive, http://wdfriday.com/blog/2012/03/css-et-mobile-first-proceder-par-amelioration-progressive/
Samatha Warren, Style tiles, http://styletil.es
Future-Friendly Manifesto, http://futurefriend.ly
Sara Wachter-Boettcher, Future-Ready Content, http://www.alistapart.com/articles/future-ready-content/
Daniel Jacobson, COPE : Create Once, Publish Everywhere, http://blog.programmableweb.com/2009/10/13/cope-create-once-publish-everywhere/
Karen McGrane, Adapting Ourselves to Adaptive Content, http://karenmcgrane.com/2012/09/04/adapting-ourselves-to-adaptive-content-video-slides-and-transcript-oh-my/
Paul Robert Lloyd, The Web Aesthetic, http://www.alistapart.com/articles/the-web-aesthetic/