The document discusses the need for content management systems to embrace flexibility and adaptability to allow content to be published across different interfaces. It introduces Novius OS as a content management system built with this principle in mind, allowing content created once to be published everywhere through its use of "content nuggets" that are separated from presentation and can be reused across different applications and channels like blogs and social media. The system is demonstrated with an example of content flowing from a database to a blog post to Twitter.

1. Create Once
Publish Everywhere…
Anytime
The future of web
content management
Antoine Lefeuvre
CIO – Novius
@jiraisurfer – novius-os.org
#dilyon25
1/43

2. Contents
Web content: back to the
future
Is your content management
system future-ready?
Our take on adaptive content
management: Novius OS
#dilyon25
2/43

3. Interfaces fly …
Credits: Google, Amstrad, Tobii, DoCoMo, Nintendo, Microsoft, Corning, Xerox & Apple (©)
#dilyon25
3/43

4. … content remain.
Credits: Amazon, Simon & Schuster, Wikipedia, A List Apart (©)
#dilyon25
4/43

5. 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.
Jonathan Stark, #bdconf (2012)
#dilyon25
5/43

6. 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).
#dilyon25
6/43

7. #dilyon25
7/43

8. “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.”
Tim Berners-Lee, Long Live the Web (2010)
#dilyon25
8/43

9. You cannot test all possibilities
(©)
Credits: Anna Debenham for A List Apart (©).
#dilyon25
9/43

10. “The web is responsive on its
own—by default. ”
Andy Hume (2011)
#dilyon25
10/43

11. So why is it our starting point?
Credits: Adobe (©).
#dilyon25
11/43

12. Credits: Andrea Balzano on Flickr (CC).
#dilyon25
12/43

13. “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.”
John Allsopp, The Dao of Web Design (2000)
#dilyon25
13/43

14. A designer must know the raw material
Credits: Subduction desk, Paul Venaille (©). Credits: El Naturalista (©).
#dilyon25
14/43

15. The web is made of code
#dilyon25
15/43

16. Design for flexibility = content without form?
#dilyon25
16/43

17. Design for flexibility = another form
Credits: Nicolas Torres pour WD Friday (©).
#dilyon25
17/43

18. Design for flexibility = another form
Credits: Novius for MS, Samatha Warren for The Examiner (©).
#dilyon25
18/43

19. 1. Acknowledge and embrace
unpredictability.
2. Think and behave in a
future-friendly way.
3. Help others do the same.
Future-Friendly Manifesto
#dilyon25
19/43

20. Contents
Web content: back to the
future
Is your content management
system future-ready?
Our take on adaptive content
management: Novius OS
#dilyon25
20/43

21. “Get your content ready to go
anywhere because it’s going to
go everywhere.”
Brad Frost (2011)
#dilyon25
21/43

22. Separate content and form (front end)
Credits: V G La Rosa, A Lefeuvre (CC).
#dilyon25
22/43

23. Separate content and form (back end)
#dilyon25
23/43

24. “Build content management
systems (CMS), not web
publishing tools (WPT).”
Daniel Jacobson,
Create Once Publish Everywhere (2009)
#dilyon25
24/43

25. Web Publishing Tool
#dilyon25
25/43

26. Content Management System
Credits: Daniel Jacobson pour NPR (©).
#dilyon25
26/43

27. Content Management System
#dilyon25
27/43

28. Contents
Web content: back to the
future
Is your content management
system future-ready?
Our take on adaptive content
management: Novius OS
#dilyon25
28/43

29. Why a new CMS
A 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 …
#dilyon25
29/43

30. Novius OS – COPE CMS
Credits: Novius (©).
#dilyon25
30/43

31. Novius OS – COPE CMS
Credits: Novius (©).
#dilyon25
31/43

32. Novius OS – COPE CMS
#dilyon25
32/43

33. 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
#dilyon25
33/43

34. Content nuggets
For 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.
#dilyon25
34/43

35. Content nuggets
Koko's content nugget, free of any presentation and ready to be
shared.
#dilyon25
35/43

36. Data catchers
The OS - the conductor - now asks: “I've got this content
nugget, who can do something with it?” The applications
equipped with data catchers answer.
#dilyon25
36/43

37. Data catchers
The 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.
#dilyon25
37/43

38. 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.
#dilyon25
38/43

39. Let's keep flowing!
A hashtag added and this nugget is now a tweet.
#dilyon25
39/43

40. 1. From a customer-
specific database 2. To a
blog post
3. And on
to Twitter
#dilyon25
40/43

41. The road ahead of us
The 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.
#dilyon25
41/43

42. Thank you!
Questions and
comments are
welcome.
Antoine Lefeuvre
CIO – Novius
@jiraisurfer – novius-os.org
#dilyon25
42/43

43. Sources and resources
Jonathan 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/
#dilyon25
43/43