Structuring and Publishing Websites for All Users

1. Microsoft SharePoint 2013 Structuring and Publishing Websites for All Users SharePoint Practice

2. Module Overview • Website Structure and Navigation Publishing Content Publishing to Mobile Devices Multi-language sites using Variations

3. Lesson 1: Website Structure and Navigation • Typical User Navigation Structured Navigation Managed Navigation Discussion: Navigation Scenarios Publishing and Taxonomy Classes

4. Typical User Navigation • Successful sites require proper navigation • Global-Global, Global-Local, Local-Local • Menus, Treeviews, Breadcrumbs • Navigation elements point to items inside and outside the site • Items include Sites, Pages, Lists, List Items

5. SharePoint Navigation • SharePoint includes two main navigation areas • Global Navigation • Current Navigation • Navigation elements provided by Navigation Providers • Custom providers can be created and used • DelegateControl wraps provider sources • Can be overridden with custom providers

6. Structured Navigation • Structural navigation is based on sites and pages in a site collection • Options to show Sites and Pages • Nodes are automatically added • SharePoint based nodes are security trimmed • Limit to only show a few items • You can manually add items to the list • Navigation Inheritance can be used to have consistent navigation across a site collection • Does not span site collections

7. Managed Navigation • Managed Navigation uses Managed Metadata to generate navigation nodes • Navigation term set must be created • Friendly URLs are generated based on term • Each term has a physical url • Term set can only be used by one site collection at a time • Site Language variations • Same navigation, different language labels • Multiple terms can be associated with same URL • Enables search-driven content

8. Creating Term Sets and Terms • Programmatically creating terms sets and terms require special properties • Term Sets: • termSet.SetCustomProperty("_Sys_Nav_IsNavigationTermSet", "True"); • Terms • term.SetLocalCustomProperty("_Sys_Nav_TargetUrl", "/Pages/Home.aspx"); • term.SetLocalCustomProperty("_Sys_Nav_SimpleLinkUrl", "http://intranet.contoso.com/Pages/Home.aspx");

9. Discussion: Navigation Scenarios • How might you implement navigation in your sites? • Discussion: Determine the best navigation strategy

10. Publishing and Taxonomy Classes • Publishing and non-publishing sites require different navigation classes • Structural Navigation (Non-publishing) uses: • SPNavigation, SPNavigationNodeCollection, SPNavigationNode classes • Structural Navigation (Publishing) uses: • PublishingWeb class • PortalNavigation class • Managed Navigation users: • WebNavigationSettings class • TaxonomyNavigation class

11. Lesson 2: Publishing Content • Publishing Features Publishing Environments Cross-site Publishing Catalogs and Catalog Connections Cross-site Publishing Navigation

12. Publishing Features • Publishing features of SharePoint • Checkin\checkout • Versioning • Content Approval • Approval workflows • Pages and content should be approved before users see it • Example: Internet site with product data should be verified by legal and marketing

13. Publishing Environments • Typical environments include • Development • Quality Assurance (QA) • Staging • Production • SharePoint publishing features may require an “Authoring” environment • Allows for non production editing by content owners • Content can be pushed to production using SharePoint APIs

14. Cross-site Publishing • Cross-site publishing is new way to publish content across site collections • Does not use Content Deployment APIs • Utilizes search and managed navigation • You can publish from one site to another (1:1) or from one site to many (1:N) • Product Catalog site definition is provided as a starting point for working with cross-site publishing

15. Cross-site publishing programming • Cross-site publishing classes are included in the Microsoft.SharePoint.Publishing namespace • PublishingCatalogUtility – used to publish and unpublish lists as catalogs • GetPublishingCatalogs • PublishCatalog • UnPublishCatalog • CatalogCollectionManager – used to consume catalogs • AddCatalogConnection

16. Catalogs and Catalog Connections • Lists must be published as catalogs • Search must index the catalogs lists • Sites must subscribe to catalogs via catalog connections • Once connection is established, page layouts are created • One for category • One for catalog item

17. Cross-site Publishing Navigation • Managed metadata navigation is used in cross-site publishing • Catalog connection creation requires you to select a categorization metadata attribute of the catalog list • Managed navigation terms and page mappings are created automatically using these values

18. Lab A: Structuring a SharePoint Publishing Site • Exercise 1: Creating a Navigation Term Set

19. Lab Scenario Contoso Management has decided that structural navigation will not meet their navigation needs on the intranet site and would like to setup managed navigation. The would like to have some of the more common corporate external links at the top of the page in addition to links that reside in the SharePoint intranet. They would also like these links to be displayed on the various team sites. They have tasked you with writing some code that will allow them to easily add navigation programmatically and in a reliable and replicable manner.

20. Lesson 3: Publishing to Mobile Devices • Mobile Device Capabilities Device Channels Device Channel Panels Demonstration: Defining Device Channels

21. Mobile Device Capabilities • Mobile devices have varying capabilities • Screen size • Touch screen support • Bandwidth • Browser and browser features • SharePoint 2013 provides more support for mobile and non-pc devices • Improved mobile site and list views • Contemporary view • Device channels

22. Device Channels • Device Channels enable dynamic setting of master page targeted at a specific device • Based on User-Agent http header • Master page is modified in the OnPreInit • Device channel mappings are stored in master page gallery • __DeviceChannelMappings.aspx • No supported object model APIs

23. Device Channel Panels • Device Channel Panels allow you to target devices on basic master pages • Good for adding content to a page based on device • Must register the Microsoft.SharePoint.Publishing.WebControls namespace in the master page • Control class name is MobilePanel • Use the IncludedChannels property to target the device channel • Separate with a comma

24. Demonstration: Defining Device Channels

25. Lesson 4: Multi-language sites using Variations • Variations Variation Labels Translating Content Multilingual Navigation

26. Variations • Variations enable multi-language sites • Users are redirected based on browser settings • On-premise up to 209 variations supported • SharePoint Online allows up to 50 • Source variation pages and configured list items are sync’d to target variations

27. Variation Labels • A Variation label is an item in a list that drives the behavior of Variation Timer Jobs • Creation is done via a series of settings pages • Configuration Data is saved to a list • No officially supported method of creating variation labels • A Variation is targeted at a specific locale • Each variation should be created with the target local UI • Requires that you install the proper language packs for the locale

28. Translating Content • Variation pages are copied from source to target in their exact form • No translation occurs • Variation pages must be translated to their target • Human Translation via workflows and tasks • Machine Translation via UI or programmatically • Machine Translation requires the Machine Translation service application • Text is submitted to online Microsoft Translation service

29. Multilingual Navigation • Variations can utilize managed navigation • Upon variation creation, a new term set called “Variations Navigation (LabelName) • Upon page creation, new terms added to term set • Only terms mapped to pages will be created • Term creation is similar to one-time process, some changes will not propagate to variations after initial creation • Translation activities will include the term label in addition to page content • Included in XLIFF export package

30. Lab B: Publishing for Multiple Devices and Languages • Exercise 1: Creating a Device Channel Exercise 2: Using the Device Panel Control Exercise 3: Creating a French Variation

31. Lab Scenario Contoso Management would like to have a more customized experience when using their mobile phones and other devices when browsing the intranet. They have asked you to utilize the out of box device channel feature in SharePoint 2013 to implement the customizations. In addition, Contoso has also recently acquired a French company that will be given access to intranet content, but several individuals are not very familiar with English and they need to create a French version of the intranet in order to get product and human resources information.

32. Lab Review • How might you see your organization using Device Channels, if at all? How might you see your organization using Variations, if at all?

33. Module Review and Takeaways • Review Question(s)