Web Content Management's (WCM) Role in the Quest for Mobile
Download as PPTX, PDF0 likes376 views
This document discusses the necessity for web content management (WCM) to adapt to mobile technology, highlighting the shift from desktop to mobile engagement. It outlines various mobile strategies, including responsive websites, mobile apps, and mobile websites, along with their advantages and disadvantages. The document emphasizes the need for CMS to evolve and manage these mobile technologies effectively to enhance user experiences across devices.
Web Content Management's (WCM) Role in the Quest for Mobile
- 1. Web Content Management's Role in the Quest for Mobile Sitefinity Telerik
- 2. Gabe Sumner Product Manager Telerik | Sitefinity CMS @gabesumner
- 3. This session will answer two questions: WHY does WCM need to address mobile? HOW can WCM address mobile?
- 4. WHY does WCM 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. 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
- 14. Lack of tooling has resurrected the “webmaster” Your Idea DeveloperExecution (Everything related to mobile must go through a “technology” gatekeeper)
- 15. HOW can WCM address mobile?
- 16. 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
- 17. 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
- 18. How can WCM address Responsive Websites? Onewebsite that adapts toALLdevices.
- 19. Responsive Websites adapt to any screen
- 20. This technique is based on adaptive grids This allows 2-columns tobecome 2-rows for small screens
- 21. And there are numerous frameworks for this task However, these frameworks exist outside the scope of the CMS
- 22. Instead, these grids should be infused into the WCM This makes the WCM aware of contentAND layouts
- 23. These layouts can then be adapted for different devices Once the WCM is aware of the layouts, it can act on this information
- 24. Transformations can happen at a site-level or page- level This enables different pages (or sections) of the website totransform differently.
- 25. Or hidden from specific devices All of this is happening in the CMS, not in source code
- 26. And previews create awareness of the result This gives content creators context about the mobile experience being created.
- 27. How can WCM address Mobile Websites? Speciallypreparedwebsiteforspecificdevices.
- 28. Specialized experiences for specific devices (DesktopExperience) (SmartphoneExperience)
- 29. Device Detection & Redirection Redirect specific devices to aspecially prepared website
- 30. Browse the entire website using a mobile simulator This allows the overall mobile experience to be tested in avariety of devices.
- 31. How can WCM address Mobile Apps? Deployable tomobile app stores
- 32. MobileApps fetch data through Web Services This “structured content” becomes accessible through a RESTFULWeb API’s
- 33. These data types should be established in the CMS And the WCM should automatically generate WebAPI’s for accessing this data
- 34. MobileApps can then be generated for this data Scaffold a CRUD-style MobileApp based on CMS-managed Content Types
- 35. Cloud Synchronization should be “built in” MobileApps interact with cloud services instead of on-premise infrastructure Cloud Services
- 36. 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 WCM address mobile?
- 37. Thank You Gabe Sumner @gabesumner www.sitefinity.com Sitefinity CMS Telerik
Editor's Notes
- #3: Our #1 priority is polishOur #2 priority should be mobile…here is why.
- #5: Our #1 priority is polishOur #2 priority should be mobile…here is why.
- #16: Our #1 priority is polishOur #2 priority should be mobile…here is why.
- #19: Our #1 priority is polishOur #2 priority should be mobile…here is why.
- #38: Our #1 priority is polishOur #2 priority should be mobile…here is why.