Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

P&M302 Real-life building public-facing websites with SharePoint 2013


Published on

SharePoint 2013 ships with a variety of new and improved WCM-capabilities. In this session we will walk through the new SP2013 WCM functionality and discuss how you can apply it in real-world solutions and get the most out of it when building public-facing websites.

Published in: Technology, Design
  • Be the first to comment

P&M302 Real-life building public-facing websites with SharePoint 2013

  1. 1. Real-life building public-facingwebsites with SharePoint 2013P&M302Waldek MastykarzSharePoint MVP
  2. 2.  Waldek Mastykarz, SharePoint MVP Mavention @waldekm
  3. 3. What’s new for public-facingwebsites in SharePoint 2013 SPSiteURLs Device Channels Image Renditions SEO features Design Manager Translation Services Managed Navigation Friendly URLs Search-driven publishing
  4. 4. Passing the F5-stageSetting expectations
  5. 5. What’s new for public-facingwebsites in SharePoint 2013 SPSiteURLs Device Channels Image Renditions SEO features Design Manager Translation Services Managed Navigation Friendly URLs Search-driven publishing
  6. 6. WCM in SharePoint 2013Classic publishing(SP2007/2010) Structural navigation CQWP Site Collection boundary Authored contentSearch-driven publishing(New) Managed Navigation CBS Cross-site publishing Intelligent websitesP&M307: Building intelligent websites with SharePoint 2013Tue: 10:15
  7. 7. Search-driven publishing: Pros Content management flexibility via Cross-sitepublishing Separation of authoring and publishing Separation of responsibilities Content reuse LOB integration Decoupling structure from navigation Dynamic experiences Available through customizations Content targeting Content recommendations Scalability
  8. 8. Search-driven publishing: Cons Required by some new capabilities Cross-site publishing Managed Navigation (Friendly URLs) XML Sitemap May have negative impact on SEO with in-sitecontent A new way of doing things Standard rendering depends on JavaScript Quirks Related queries XSL-based rendering possible but in manual mode
  9. 9. Search-driven publishingPros Content managementflexibility via Cross-sitepublishing Dynamic experiences ScalabilityCons Required by some newcapabilities May have negativeimpact on SEO with in-site content A new way of doingthings Quirks
  10. 10. Search-driven publishing impact Information architecture In-site or catalogs Managed or structural navigation Taxonomy Solution architecture One Site Collection or multiple Assets location Infrastructure architecture Search Knowledge/skillset Search
  11. 11. Cross-site publishingCatalogs: not only for products
  12. 12. Cross-site publishing: short recap Search-driven content publishing Based on Catalogs (Lists) Structured using taxonomies
  13. 13. Catalogs Default configuration for products Product Catalog Site Definition Can be used with any List Definition incl. Pages! Additional configuration required for analytics
  14. 14. Catalogs: for content only Only content published through search Assets Only metadata published through search Files referenced by original URL Think about location!– Must be accessible in all places where thecontent from Catalog is consumed– Take anonymous Catalog publishing intoaccount!
  15. 15. Image Renditions Image Renditions vs. Multi-sitearchitectures Storage location– Suggested Content Browser Locations Permissions Usability– By default limited to current Site Collection– Mavention External Image Renditions Enabler– Mavention Sized Renditions
  16. 16. XML Sitemap Available out of the box ‘Just works’ Based on SharePoint 2013 Search Clever Catalogs Friendly URLs Physical URLs URLs Internet Zone SPSiteURL preference Site Collection URL of the Internet Zone
  17. 17. XML Sitemap Limited No priority No change frequency Not extensible Clever = complex Catalogs Friendly URLs Physical URLs
  18. 18. Managed Navigation vs. in-sitecontent Catalogs vs. in-site content Friendly URLs for in-site content Design for SEO The same content available on multipleURLs– Physical vs. Friendly Use Canonical URL Available through hiddenSearchEngineOptimization Feature
  19. 19. Search-driven publishing with theREST API Great flexibility Publishing content to other systems/apps By default disabled for anonymous Enable: Related content queries
  20. 20. Building user experiencesDisplay Templates Default JavaScript-based New (you will need tolearn) Depends on browserssupported by SP2013 Standard functionalityavailable Refiners Analytics hooksServer Style Sheets Fallback mechanism XSLT-based You might already befamiliar with XSLT No dependencies Manual mode Used on
  21. 21. Building cross-device experiencesDevice Channels Device Management Different HTML for everychannel More management butmore flexibility Can be used forseparating authoring andpublishing experience( Web Design Properties Management Same HTML for everydevice Less management butlimited by CSS and JScapabilities Preferred approach forsearch engines (SEO)
  22. 22. Disaster RecoveryWith great power comes great responsibilityWhere is your content?Where are your search settings?Where is your search analytics data?Catalogs vs. different URLsThe past vs. the future
  23. 23. Summary New and improved WCM-capabilitiesavailable in SP2013 New solution design concepts Great results with less effort
  24. 24. More information Mavention Sized Renditions Mavention External Image Renditions Enabler Mavention Case Study Me @ SharePoint 2013 SharePoint 2013 @ Mavention Mavention
  25. 25. Thank you for attending!