Create Once Publish Everywhere Anytime (version française)
-
Upload
novius-os -
Category
Technology
-
view
583 -
download
2
description
Transcript of Create Once Publish Everywhere Anytime (version française)
![Page 1: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/1.jpg)
1/42#dilyon25
Create OncePublish Everywhere… AnytimeLe futur de la gestion de contenu web
Antoine LefeuvreDirecteur R&D – Novius
@jiraisurfer – novius-os.org
![Page 2: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/2.jpg)
2/42
#dilyon25
Contenu web : retour vers le futur
Votre système de gestion de contenu est-il future-ready ?
Notre proposition : Novius OS
Sommaire
![Page 3: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/3.jpg)
3/42
#dilyon25
Les interfaces s'envolent …
Crédits : Google, Amstrad, Tobii, DoCoMo, Nintendo, Microsoft, Corning, Xerox & Apple (©)
![Page 4: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/4.jpg)
4/42
#dilyon25
… les contenus restent.
Crédits : Amazon, Simon & Schuster, Wikipedia, A List Apart (©)
![Page 5: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/5.jpg)
5/42
#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.”
![Page 6: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/6.jpg)
6/42
#dilyon25
Responsive, la solution ?
Crédits : Site Boston Globe par Ethan Marcotte, Filament Group, Upstatement et équipes internes (©). Montage par Antoine Lefeuvre, Grant Hutchinson, responsivedesign.ca (CC).
![Page 7: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/7.jpg)
7/42
#dilyon25
![Page 8: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/8.jpg)
8/42
#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.”
![Page 9: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/9.jpg)
9/42
#dilyon25
On ne pourra jamais tout tester
(©)
Crédits : Anna Debenham pour A List Apart (©).
![Page 10: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/10.jpg)
10/42
#dilyon25
Andy Hume (2011)
“The web is responsive on its own—by default. ”
![Page 11: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/11.jpg)
11/42
#dilyon25
Mais pourquoi est-ce notre point de départ ?
Crédits : Adobe (©).
![Page 12: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/12.jpg)
12/42
#dilyon25
Crédits : Andrea Balzano sur Flickr (CC).
![Page 13: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/13.jpg)
13/42
#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.”
![Page 14: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/14.jpg)
14/42
#dilyon25
Un designer est un expert de la matière
Crédits : bureau Subduction, Paul Venaille (©). Crédits : El Naturalista (©).
![Page 15: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/15.jpg)
15/42
#dilyon25
Le code est la matière du web
![Page 16: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/16.jpg)
16/42
#dilyon25
Design for flexibility = le fond sans forme ?
![Page 17: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/17.jpg)
17/42
#dilyon25
Design for flexibility = une autre forme
Crédits : Nicolas Torres pour WD Friday (©).
![Page 18: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/18.jpg)
18/42
#dilyon25
Design for flexibility = une autre forme
Crédits : Novius pour MS, Samatha Warren for The Examiner (©).
![Page 19: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/19.jpg)
19/42
#dilyon25
Future-Friendly Manifesto
Acknowledge and embrace unpredictability.Think and behave in a future-friendly way.Help others do the same.
1.
2.
3.
![Page 20: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/20.jpg)
20/42
#dilyon25
Contenu web : retour vers le futur
Votre système de gestion de contenu est-il future-ready ?
Notre proposition : Novius OS
Sommaire
![Page 21: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/21.jpg)
21/42
#dilyon25
Brad Frost (2011)
“Get your content ready to go anywhere because it’s going to
go everywhere.”
![Page 22: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/22.jpg)
22/42
#dilyon25
Séparer fond et forme (front end)
Crédits : V G La Rosa, A Lefeuvre (CC).
![Page 23: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/23.jpg)
23/42
#dilyon25
Séparer fond et forme (back end)
![Page 24: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/24.jpg)
24/42
#dilyon25
Daniel Jacobson,Create Once Publish Everywhere (2009)
“Build content management systems (CMS), not web publishing tools (WPT).”
![Page 25: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/25.jpg)
25/42
#dilyon25
Web Publishing Tool
![Page 26: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/26.jpg)
26/42
#dilyon25
Content Management System
Crédits : Daniel Jacobson pour NPR (©).
![Page 27: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/27.jpg)
27/42
#dilyon25
Content Management System
![Page 28: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/28.jpg)
28/42
#dilyon25
Contenu web : retour vers le futur
Votre système de gestion de contenu est-il future-ready ?
Notre proposition : Novius OS
Sommaire
![Page 29: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/29.jpg)
29/42
#dilyon25
Pourquoi un nouveau CMSUn CMS chef d'orchestre et prêt pour le futur.
Expérience utilisateur : est-on prêt à créer du contenu presentation agnostic ?
Notre ambition : amener au « Create Once Publish Everywhere » sans brusquer, travailler la courbe d'apprentissage.
« Couche Information » alimentée naturellement (Pages, Blog, bases de données spécifiques, etc.)
![Page 30: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/30.jpg)
30/42
#dilyon25
Novius OS – CMS COPE
Crédits : Novius (©).
![Page 31: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/31.jpg)
31/42
#dilyon25
Novius OS – CMS COPE
Crédits : Novius (©).
![Page 32: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/32.jpg)
32/42
#dilyon25
Novius OS – CMS COPE
![Page 33: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/33.jpg)
33/42
#dilyon25
La démo : D'une base de données spécifique à un billet de blog, puis vers Twitter
Découvrez la démo (slide suivant) puis passez au slide 35
pour plus de détails
![Page 34: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/34.jpg)
34/42
#dilyon25
Pépites de contenu (content nuggets)Pour chaque singe, l'application Monkey partage une pépite de contenu. Pourquoi “pépite” ? Petite et de valeur : un contenu suffisamment petit pour être ré-utilisé, mais néanmoins porteur de sens.
![Page 35: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/35.jpg)
35/42
#dilyon25
Pépites de contenu (content nuggets)Voici le content nugget du gorille Koko, prêt à être partagé.
![Page 36: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/36.jpg)
36/42
#dilyon25
Data catchersL'OS, ce chef d'orchestre, demande alors : “J'ai cette pépite de contenu, qui peut en faire quelque chose ?” Les applications équipées de data catchers répondent.
![Page 37: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/37.jpg)
37/42
#dilyon25
Data catchersL'application Blog attrape (catch) la pépite de contenu de Monkey et - hop ! - un billet de blog en moins d'une minute. Juste le temps d'adapter la pépite en news (“Welcome to Koko”).
![Page 38: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/38.jpg)
38/42
#dilyon25
Circulez, circulez !Votre contenu ne va pas s'arrêter là. Du billet de blog est extrait une nouvelle pépite de contenu, qui ne demande qu'à être attrapée.
![Page 39: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/39.jpg)
39/42
#dilyon25
Circulez, circulez !Un hashtag ajoutée (#gorilla) et voici une pépite devenue tweet.
![Page 40: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/40.jpg)
40/42
#dilyon25
1. D'une base de données spécifique 2. À un billet
de blog
3. Puis vers Twitter
![Page 41: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/41.jpg)
41/42#dilyon25
Merci beaucoup !Questions et critiques bienvenues.
Antoine LefeuvreDirecteur R&D – Novius
@jiraisurfer – novius-os.org
![Page 42: Create Once Publish Everywhere Anytime (version française)](https://reader033.fdocuments.in/reader033/viewer/2022052907/55909d071a28ab70148b463e/html5/thumbnails/42.jpg)
42/42
#dilyon25
Sources et ressourcesJonathan Stark, Breaking Development: The Revolution Will Not Be Televised, notes par 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/
Paul Robert Lloyd, The Web Aesthetic, http://www.alistapart.com/articles/the-web-aesthetic/