Top Banner
SharePoint 2013 Web Content Management Features for Developers
18
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Share point 2013 WCM for Developers

SharePoint 2013Web Content Management Features for Developers

Page 2: Share point 2013 WCM for Developers

Agenda• Managed Navigation• Content Search WP• Display Templates• Cross-site Publishing• Product Catalog• Demos

Page 3: Share point 2013 WCM for Developers

Managed Navigation• What ?

o Navigation for Publishing site based on Taxonomy (managed metadata)

• Why ?o Decouple structure of site from Navigationo Helps build clean URLs

• How ?o Choose term Set for Site collection and use additional properties for Navigationo Can be combined with other features such as Cross site publishing

• Drawbackso No version control on termso No publishing workflow on terms

Page 5: Share point 2013 WCM for Developers

Managed Navigation: Pinning Terms

Term Pinning - New in 2013:• Pinning is the ability to attach a term to a target• Similar to Term Reuse in 2010, but is read-only• Allows to reuse the terms and manage it from one central location• Example code for pinning terms:

o https://msdn.microsoft.com/EN-US/library/office/jj163273.aspx

Page 6: Share point 2013 WCM for Developers

Managed Navigation: Pinning Terms

Page 7: Share point 2013 WCM for Developers

Content Search Web Part• New WP in 2013• Similar to CQWP, but is based on search• Has many built-in configuration mechanisms for search query, filter,

etc.• UI can be customized by ‘Display Templates’

Page 8: Share point 2013 WCM for Developers

Content Search WP

Page 9: Share point 2013 WCM for Developers

Content Search WP

Page 10: Share point 2013 WCM for Developers

Display Templates• Templates used by search-based web parts to format query results[Only Search Web Parts can use display templates]

• Controls which properties are shown and how they appear

• Consist of 2 files that are associated: • HTML version which developer uses• JavaScript file which SharePoint uses

o Association causes automatic one-way sync from HTML to JSo Association cannot be broken

Page 11: Share point 2013 WCM for Developers

Display Templates: TypesTwo types• Control templates: Determines the overall structure of how the

results are presented. Includes lists, lists with paging, and slide shows.

• Item templates: Determines how each result in the set is displayed. Includes images, text, video, and other items.

Built-in Display Templates: https://technet.microsoft.com/en-us/library/jj944947.aspx

Page 12: Share point 2013 WCM for Developers

Display Templates: Types

Page 13: Share point 2013 WCM for Developers

Display Templates: Customizing

• Start by copying with existing template(HTML) in ‘Display Templates’ foldero A .js file that has the same name is created in the location where you copied the HTML file.o All markup required by SharePoint Server 2013 is added to the .js file so that the display template

displays correctly.o The HTML file and the .js file are associated, so that any later edits to the HTML file are synched to

the .js file when the HTML file is saved.

• Customizing Information: https://msdn.microsoft.com/en-us/library/office/jj945138.aspx

• Example: http://blogs.technet.com/b/sharepoint_quick_reads/archive/2013/08/01/sharepoint-2013-customize-display-template-for-content-by-search-web-part-cswp-part-1.aspx

Page 14: Share point 2013 WCM for Developers

Cross-site Publishing• What ?

o One or more authoring site collections to author and store content, and one or more publishing site collections to control the design of the site and to show the content

• Why ?o Decouples content from site designo Helps manage permissions

• How ?o Enable libraries and lists in author sites as catalogso Content tagged with metadatao Search is used to crawl and display published content

• Drawbackso Content not shown until it is indexedo Term store does not support versioning

Page 15: Share point 2013 WCM for Developers

Cross-site Publishing

1. Content is created in libraries and lists that are shared as catalogs in the authoring site collection.

2. The search system crawls the content and builds the search index.3. A user views a page on a publishing site, which triggers queries from Search Web Parts.4. Results are returned from the search index, and shown in Search Web Parts on the page.

Page 16: Share point 2013 WCM for Developers

Product Catalog• What ?

o A Site template (for authoring site)o Has features pre-configured for cross-site publishing and managed navigation

• Why ?o Helps to setup a Product-centric websiteo Reduces the hassle for configuring features and web partso Automatically creates Category page and Catalog-item page

• How ?o Create a ‘Product Catalog’ template site for Author siteo Configure for publishingo Consume catalog in Publishing site

Page 18: Share point 2013 WCM for Developers

References• Managed navigation in SharePoint 2013 (https://

msdn.microsoft.com/en-us/library/office/jj163978.aspx) • Configure Search Web Parts in SharePoint Server 2013 (https://

technet.microsoft.com/en-us/library/jj679900.aspx)• SharePoint 2013 Design Manager display templates (

https://msdn.microsoft.com/en-us/library/office/jj945138.aspx)• Overview of cross-site publishing in SharePoint Server 2013 (

https://technet.microsoft.com/en-us/library/jj635883.aspx)• How to set up a product-centric website in SharePoint Server 2013 (

http://blogs.technet.com/b/tothesharepoint/archive/2013/02/14/how-to-set-up-a-product-centric-web-site-in-sharepoint-2013.aspx

)