sp2013 wcm bootcamp - arc01 planning for public-facing websites

Planning for public-facing websitesFredrik Holm Waldek MastykarzSenior Program Manager SharePoint MVP

Microsoft Mavention

ARC01

• SPSiteURLs• Device Channels• Image Renditions• SEO features• Design Manager• Translation Services• Managed Navigation• Friendly URLs• Search-driven publishing

What’s new?

Plan web content management• Publishing• Navigation• Building approach• Caching and performance• Disaster Recovery

Plan for publishing

WCM in SharePoint 2013Classic publishing (SP2007/2010)• Structural navigation• CQWP• Site Collection boundary• Authored content

Search-driven publishing (New)• Managed Navigation• Content Search webpart• Cross-site publishing• Intelligent websites

• Content management flexibility via Cross-site publishing• 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

Search-driven publishing advantages

• May have negative impact on SEO with in-site content

• A new way of doing things• Standard rendering depends on JavaScript

• Quirks• Related queries• XSL-based rendering possible but in manual mode

Search-driven publishing challenges

• 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

Search-driven publishing impact

Sample scenarios

• Leverage new capabilities which require search-driven publishing

• User-centric functionality (intelligent websites)

• Small websites

Search-driven publishing with in-site authoring

Search-driven publishing plus:• Separation of content management

responsibilities• Publication of external content• Content reuse• Centralized management of multilingual

websites• Medium to large websites

Cross-site publishing

Catalogs

• Quick migration of websites from SharePoint 2007 and 2010

Classic publishing model

• Based on requirements choose publishing model• Search-driven publishing• In-site authoring or cross-site publishing?• Consider continuous crawl for content freshness

• Cross-site publishing• Where are the catalogs located?• Will you provide a preview experience?• Where are the assets stored?

• Generic• Information architecture• Workflows• Versioning• Permissions

Plan for publishing

• Determine publishing method and architecturehttp://technet.microsoft.com/en-us/library/jj635878.aspx

• Plan logical architecture for cross-site publishinghttp://technet.microsoft.com/en-us/library/jj635882.aspx

• Plan authoring sites for cross-site publishinghttp://technet.microsoft.com/en-us/library/jj635877.aspx

• Plan publishing sites for cross-site publishinghttp://technet.microsoft.com/en-us/library/jj635879.aspx

• Plan search for cross-site publishinghttp://technet.microsoft.com/en-us/library/jj635875.aspx

Available documentation

Plan for navigation

• Based on the physical structure of the website

• Per-site settings• Inheritance• Show sites• Show pages

• Use with the classic publishing model

Structural navigation

• Defined in the Managed Metadata Service• Decouples the physical structure of the

website from the navigation and URLs• Challenging to combine with subsites!• Use for search-driven publishing

Managed Navigation

ManagedNavigation

• Plan navigation Term Set• Assign responsibilities and permissions• Plan navigation terms• Custom and reused/pinned terms• Friendly URLs• Navigation settings• Term-driven pages

• Plan for SEO• Canonical URLs

Plan for navigation

• Overview of managed navigationhttp://technet.microsoft.com/en-us/library/dn194311.aspx

Available documentation

Plan for website building approach

Websites building approachesSolutions (WSP)• Structured• Repeatable• Costly• More time-consuming• Less error-prone

• De facto business standard for SharePoint

Customizations• Ad-hoc• Some can be exported• Cheaper than Solutions• Shorter time-to-market• More error-prone

• What the rest of the WCM world does

Quiz….

Is public-facing website a business critical solution?

Do you require structured and repeatable deployment for your public-facing website?

Why?

• Less overhead than Solutions• Time• Effort• Money

• Lowers the knowledge bar for the team• More alignment with the lifecycle of a

website

Customization benefits

• Team work• Working space availability• Platform hygiene• Irreversible mistakes• Syncing assets over multiple sites

Customizations challenges

• Choose appropriate approach• Consider leveraging customizations• Plan for all customizations-specific challenges

Plan for website building approach

Plan for caching and performance

• Distributed Cache• BLOB cache• Object cache• Output cache• Anonymous search results cache

Cache types in SharePoint 2013

• Distributed Cache: off limits• BLOB cache: required by Image Renditions• Object cache: custom code• Output cache: optional• Anonymous search results cache:

recommended

Cache types in SharePoint 2013

• Output cache == same content for everyone

• Personalization <> same content for everyone

• Output cache profile on a per-Page Layout basis

Output cache and content personalization

• Everything from SharePoint 2010• Consolidate multiple search queries• Offload complex rendering to the client• Plan for SEO!

Performance considerations

• If performance is important plan for it from day #1

• Plan for static and dynamic content

Plan for caching and performance

• Estimate capacity and performance for WCMhttp://technet.microsoft.com/en-us/library/gg398060.aspx

Available documentation

Plan for disaster recovery

• Where is your content?• Where are your search settings?• Where is your search analytics data?• Catalogs vs. different URLs

Disaster recovery

• Many facets to public-facing websites planning

• Complexity depends on scope• Learn what SharePoint 2013 has to offer to

be successful

Summary

• Mavention Case Studyhttp://blog.mastykarz.nl/go/mavention-case/

• Scenario: Create sites by using cross-site publishinghttp://technet.microsoft.com/en-US/sharepoint/jj872721

• Step-by-step: How to set up a product-centric websitehttp://blogs.technet.com/b/tothesharepoint/archive/2013/02/14/how-to-set-up-a-product-centric-web-site-in-sharepoint-2013.aspx

More information

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.