Your SlideShare is downloading. ×
0
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Mobile CMS Has Arrived!
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Mobile CMS Has Arrived!

126

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
126
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Our #1 priority is polishOur #2 priority should be mobile…here is why.
  • Our #1 priority is polishOur #2 priority should be mobile…here is why.
  • Our #1 priority is polishOur #2 priority should be mobile…here is why.
  • Create a Store Locator
  • Our #1 priority is polishOur #2 priority should be mobile…here is why.
  • Our #1 priority is polishOur #2 priority should be mobile…here is why.
  • Transcript

    • 1. Mobile CMS Has ArrivedSitefinity 6.0Telerik
    • 2. Gabe SumnerTelerik | 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 addressmobile?
    • 5. Mobile is on course to overtake desktops2009 2015E2,0001,6001,200800400
    • 6. This is clearly reflected in today’s headlines
    • 7. And the “payoff” is becoming evidentNumerous businesses are enjoying the benefits of mobile engagement.
    • 8. And we’re working out the “kinks”* Source ForeseeMobile experiences arenearly 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 curveWe are here. And tools historically help bridge thisgap.CMS needs do more than “talk” about mobile
    • 15. Lack of tooling has resurrected the “webmaster”Your IdeaDeveloperExecution(Everything related to mobile must go through a “technology” gatekeeper)
    • 16. HOW can CMS address mobile?
    • 17. Responsive Website Mobile AppMobile WebsiteDevice-AgnosticExperienceDevice-SpecificExperienceThere are three mobile strategies tochoose from(Each has pros/cons and there are reasons to combine
    • 18. Responsive WebsiteResponsive GridsCSS3 Media QueriesMobile AppHTML5 Mobile AppsCloud ServicesMobile WebsiteDevice DetectionDevice RedirectionDevice-AgnosticExperienceDevice-SpecificExperienceAnd behind each strategy arenumerous technologiesCMS must evolve to help create & manage these technologies
    • 19. How can CMS addressResponsive Websites?Onewebsite that adapts toALLdevices.
    • 20. Responsive Websites adapt to any screen
    • 21. This technique is based on adaptive gridsThis allows 2-columns tobecome 2-rows for small screens
    • 22. And there are numerous frameworks for this taskHowever, theseframeworks existoutside the scope of theCMS
    • 23. Instead, these grids should be infused into the WCMThis makes the WCM aware of contentAND layouts
    • 24. These layouts can then be adapted for differentdevicesOnce the WCM is aware of the layouts, it can act on this information
    • 25. Transformations can happen at a site-level or page-levelThis enables different pages (or sections) of the website totransformdifferently.
    • 26. Or hidden from specific devicesAll of this is happening in the CMS, not in source code
    • 27. And previews create awareness of the resultThis gives content creators context about the mobile experience beingcreated.
    • 28. Responsive Website Mobile AppMobile WebsiteDevice-AgnosticExperienceDevice-SpecificExperienceThere are three mobile strategies tochoose from(Each has pros/cons and there are reasons to combine
    • 29. How can CMS addressMobile Websites?Speciallypreparedwebsiteforspecificdevices.
    • 30. Specialized experiences for specific devices(DesktopExperience) (SmartphoneExperience)
    • 31. Device Detection & RedirectionRedirect specific devices to aspecially prepared website
    • 32. Browse the entire website using a mobile simulatorThis allows the overall mobile experience to be tested in avariety ofdevices.
    • 33. Responsive Website Mobile AppMobile WebsiteDevice-AgnosticExperienceDevice-SpecificExperienceThere are three mobile strategies tochoose from(Each has pros/cons and there are reasons to combine
    • 34. How can CMS addressMobile Apps?Deployable tomobile app stores
    • 35. MobileApps fetch data through Web ServicesThis “structured content” becomes accessible through a RESTFULWebAPI’s
    • 36. These data types should be established in the CMSAnd the WCM should automatically generate WebAPI’s for accessing thisdata
    • 37. MobileApps can then be generated for this dataScaffold a CRUD-style MobileApp based on CMS-managed ContentTypes
    • 38. Cloud Synchronization should be “built in”MobileApps interact with cloud services instead of on-premise infrastructureCloudServices
    • 39. Publish once to everywhereResponsive WebsiteDevice PreviewDevice SimulatorLayout TransformationsHidden LayoutsMobile AppModule BuilderHybrid App BuilderDevelopmentEnvironmentCloud IntegrationMobile WebsiteDevice PreviewDevice SimulatorDevice DetectionSite RedirectionDevice-AgnosticExperienceDevice-SpecificExperienceHow can CMS address mobile?
    • 40. Try it for yourself atwww.sitefinity.com/trySitefinity CMSTelerikOr contact us for a live demo at sales@sitefinity.com

    ×