Web Content Management's (WCM) Role in the Quest for Mobile


Published on

Mobile Internet access grows daily, yet many organizations continue to struggle with their mobile strategy. This offers a competitive advantage for those offering compelling mobile experiences. But there are many options to consider. Join Telerik to explore how effective web content management can help your organization avoid mobile pitfalls and develop mobile strategies to yield long term success.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

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.
  • 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.
  • Web Content Management's (WCM) Role in the Quest for Mobile

    1. 1. Web Content Managements Role inthe Quest for MobileSitefinityTelerik
    2. 2. Gabe SumnerProduct ManagerTelerik | Sitefinity CMS@gabesumner
    3. 3. This session will answer two questions:WHY does WCM need to address mobile?HOW can WCM address mobile?
    4. 4. WHY does WCM need to addressmobile?
    5. 5. Mobile is on course to overtake desktops2009 2015E2,0001,6001,200800400
    6. 6. This is clearly reflected in today’s headlines
    7. 7. And the “payoff” is becoming evidentNumerous businesses are enjoying the benefits of mobile engagement.
    8. 8. And we’re working out the “kinks”* Source ForeseeMobile experiences arenearly on par with desktop
    9. 9. However, look more closely…Onlythetoponlineretailersarereportingtheseresults
    10. 10. Other “top” websites paint a different picture* Source Top 500 Guide – InternetRetailer.com
    11. 11. In fact, evidence suggests many of us are struggling* Source Strangeloop* Source Econsultancy
    12. 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. 13. We’re still climbing the adoption curveWe are here. And tools historically help bridge thisgap.CMS needs do more than “talk” about mobile
    14. 14. Lack of tooling has resurrected the “webmaster”Your IdeaDeveloperExecution(Everything related to mobile must go through a “technology” gatekeeper)
    15. 15. HOW can WCM address mobile?
    16. 16. Responsive Website Mobile AppMobile WebsiteDevice-AgnosticExperienceDevice-SpecificExperienceThere are three mobile strategies tochoose from(Each has pros/cons and there are reasons to combine
    17. 17. 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
    18. 18. How can WCM addressResponsive Websites?Onewebsite that adapts toALLdevices.
    19. 19. Responsive Websites adapt to any screen
    20. 20. This technique is based on adaptive gridsThis allows 2-columns tobecome 2-rows for small screens
    21. 21. And there are numerous frameworks for this taskHowever, theseframeworks existoutside the scope of theCMS
    22. 22. Instead, these grids should be infused into the WCMThis makes the WCM aware of contentAND layouts
    23. 23. These layouts can then be adapted for differentdevicesOnce the WCM is aware of the layouts, it can act on this information
    24. 24. Transformations can happen at a site-level or page-levelThis enables different pages (or sections) of the website totransformdifferently.
    25. 25. Or hidden from specific devicesAll of this is happening in the CMS, not in source code
    26. 26. And previews create awareness of the resultThis gives content creators context about the mobile experience beingcreated.
    27. 27. How can WCM addressMobile Websites?Speciallypreparedwebsiteforspecificdevices.
    28. 28. Specialized experiences for specific devices(DesktopExperience) (SmartphoneExperience)
    29. 29. Device Detection & RedirectionRedirect specific devices to aspecially prepared website
    30. 30. Browse the entire website using a mobile simulatorThis allows the overall mobile experience to be tested in avariety ofdevices.
    31. 31. How can WCM addressMobile Apps?Deployable tomobile app stores
    32. 32. MobileApps fetch data through Web ServicesThis “structured content” becomes accessible through a RESTFULWebAPI’s
    33. 33. These data types should be established in the CMSAnd the WCM should automatically generate WebAPI’s for accessing thisdata
    34. 34. MobileApps can then be generated for this dataScaffold a CRUD-style MobileApp based on CMS-managed ContentTypes
    35. 35. Cloud Synchronization should be “built in”MobileApps interact with cloud services instead of on-premise infrastructureCloudServices
    36. 36. Publish once to everywhereResponsive WebsiteDevice PreviewDevice SimulatorLayout TransformationsHidden LayoutsMobile AppModule BuilderHybrid App BuilderDevelopmentEnvironmentCloud IntegrationMobile WebsiteDevice PreviewDevice SimulatorDevice DetectionSite RedirectionDevice-AgnosticExperienceDevice-SpecificExperienceHow can WCM address mobile?
    37. 37. Thank YouGabe Sumner@gabesumnerwww.sitefinity.comSitefinity CMSTelerik