Fat client, CMS as API

9
Fat client, CMS as API DrupalCamp Helsinki 2.6.2012 @TomiMikola

description

This is slides from DrupalCamp Helsinki session, from track Drupal & Mobile. With the rising diversity of client platforms and use cases we'll have to search for approaches that don't work only as Web Publishing System, but as Content Management System.

Transcript of Fat client, CMS as API

Page 1: Fat client, CMS as API

Fat client, CMS as APIDrupalCamp Helsinki 2.6.2012

@TomiMikola

Page 2: Fat client, CMS as API

WEB IN 90’s - 00’sLOOSELY LINKED SITESPOINT2POINTINTEGRATION

http://www.flickr.com/photos/tarynmarie/218965633

Page 3: Fat client, CMS as API

WEB IN 2012MOBILERADID DEVELOPMENTFLOW OFSHARED DATA

http://www.flickr.com/photos/robbie_v/6746487971

Page 4: Fat client, CMS as API

DISTINCT PROCESSES

CONTENT CREATION

http://www.flickr.com/photos/rachel_s/2407733396

CONTENT MGMT

CONTENT DELIVERY

CONTENT CONSUMING

Page 5: Fat client, CMS as API

TECH IMPACTSSaaS MANAGEDAPIs

http://www.flickr.com/photos/spettacolopuro/3813556085

CMS APIs

RWD WEB APPS MOBILE SDKs

Page 6: Fat client, CMS as API

MOBILE WEB APPSNATIVE APP

http://www.flickr.com/photos/merlijnhoek/2841785343

HTML 5

Page 7: Fat client, CMS as API

APPS & DRUPAL

CONTENT POLLUTED WITHPRESENTATIONAL DATA

http://www.flickr.com/photos/macieklew/351554256

CONTENT EDITING& FORM API

THEME LAYER

MENU SYSTEMWPS

Page 8: Fat client, CMS as API

DEMO

TWITTER BOOTSTRAPhttp://www.flickr.com/photos/br0wser/708269315

SERVICES MODULE

ANGULAR JS

Page 9: Fat client, CMS as API