1. Mobile CMS Has Arrived
Sitefinity 6.0
Telerik

2. Gabe Sumner
Telerik | Sitefinity CMS
@gabesumner

3. This webinar will answer two questions:
WHY does CMS need to address mobile?
HOW can CMS address mobile?

4. WHY does CMS need to address
mobile?

5. Mobile is on course to overtake desktops
2009 2015E
2,000
1,600
1,200
800
400

6. This is clearly reflected in today’s headlines

7. And the “payoff” is becoming evident
Numerous businesses are enjoying the benefits of mobile engagement.

8. And we’re working out the “kinks”
* Source Foresee
Mobile experiences are
nearly on par with desktop

9. However, look more closely…
Onlythetoponlineretailersarereportingtheseresults

10. Other “top” websites paint a different picture
* Source Top 500 Guide – InternetRetailer.com

11. In fact, evidence suggests many of us are struggling
* Source Strangeloop
* Source Econsultancy

12. TheTale of Two Cities…
The opportunity is real.
The path to success is explored.
But many are struggling.
Why?
(The answer is complicated, but lack of tooling is hurting us.)

13. CMS isn’t helping with Mobile

14. We’re still climbing the adoption curve
We are here. And tools historically help bridge this
gap.
CMS needs do more than “talk” about mobile

15. Lack of tooling has resurrected the “webmaster”
Your Idea
DeveloperExecution
(Everything related to mobile must go through a “technology” gatekeeper)

16. HOW can CMS address mobile?

17. Responsive Website Mobile AppMobile Website
Device-Agnostic
Experience
Device-Specific
Experience
There are three mobile strategies to
choose from
(Each has pros/cons and there are reasons to combine

18. Responsive Website
Responsive Grids
CSS3 Media Queries
Mobile App
HTML5 Mobile Apps
Cloud Services
Mobile Website
Device Detection
Device Redirection
Device-Agnostic
Experience
Device-Specific
Experience
And behind each strategy are
numerous technologies
CMS must evolve to help create & manage these technologies

19. How can CMS address
Responsive Websites?
Onewebsite that adapts toALLdevices.

20. Responsive Websites adapt to any screen

21. This technique is based on adaptive grids
This allows 2-columns tobecome 2-rows for small screens

22. And there are numerous frameworks for this task
However, these
frameworks exist
outside the scope of the
CMS

23. Instead, these grids should be infused into the WCM
This makes the WCM aware of contentAND layouts

24. These layouts can then be adapted for different
devices
Once the WCM is aware of the layouts, it can act on this information

25. Transformations can happen at a site-level or page-
level
This enables different pages (or sections) of the website totransform
differently.

26. Or hidden from specific devices
All of this is happening in the CMS, not in source code

27. And previews create awareness of the result
This gives content creators context about the mobile experience being
created.

28. Responsive Website Mobile AppMobile Website
Device-Agnostic
Experience
Device-Specific
Experience
There are three mobile strategies to
choose from
(Each has pros/cons and there are reasons to combine

29. How can CMS address
Mobile Websites?
Speciallypreparedwebsiteforspecificdevices.

30. Specialized experiences for specific devices
(DesktopExperience) (SmartphoneExperience)

31. Device Detection & Redirection
Redirect specific devices to aspecially prepared website

32. Browse the entire website using a mobile simulator
This allows the overall mobile experience to be tested in avariety of
devices.

33. Responsive Website Mobile AppMobile Website
Device-Agnostic
Experience
Device-Specific
Experience
There are three mobile strategies to
choose from
(Each has pros/cons and there are reasons to combine

34. How can CMS address
Mobile Apps?
Deployable tomobile app stores

35. MobileApps fetch data through Web Services
This “structured content” becomes accessible through a RESTFULWeb
API’s

36. These data types should be established in the CMS
And the WCM should automatically generate WebAPI’s for accessing this
data

37. MobileApps can then be generated for this data
Scaffold a CRUD-style MobileApp based on CMS-managed Content
Types

38. Cloud Synchronization should be “built in”
MobileApps interact with cloud services instead of on-premise infrastructure
Cloud
Services

39. Publish once to everywhere
Responsive Website
Device Preview
Device Simulator
Layout Transformations
Hidden Layouts
Mobile App
Module Builder
Hybrid App Builder
Development
Environment
Cloud Integration
Mobile Website
Device Preview
Device Simulator
Device Detection
Site Redirection
Device-Agnostic
Experience
Device-Specific
Experience
How can CMS address mobile?

40. Try it for yourself at
www.sitefinity.com/try
Sitefinity CMS
Telerik
Or contact us for a live demo at sales@sitefinity.com