Swiss SharePoint Club

Creating product-centric sites using cross-site
collection publishing
Marius Constantinescu
[MVP Sh...
1. Introducing Content catalogs

2. How does it work ?
3. Search-driven applications
Introducing Content Catalogs
What are these and why do we need them?
Separate presentation from storage
•Different teams w...
Information Architecture 1/2
Authoring sites / Published sites

1. Authoring vs. Publishing sites
 For multilingual solut...
Information Architecture 1/2
Navigation, Content types, fields
Prod uct
Code
Title
Description
Price

All from Product +

...
Documents
Pages
Digital Assets
Catalogs
SharePoint Content

Variations

Content & Authoring

FAST Search

Publishing
Page ...
List columns, Managed properties, Refiners
Journey from list field to crawled > managed and rendering (refiner / display )...
Metadata driven navigation
Consistent navigation across site collections

Managed Metadata driven vs.
Structural navigatio...
Metadata driven navigation, cont.
Centrally managed with designated term sets
3
1



Linked
terms

Reused terms
between t...
Configuring Metadata-driven navigation
Demo
Category pages and product item pages
Category page

Catalog-Item Page
Refiners – why use them?
What are they and why we need them?

1. Refiners are filters narrowing

search results
2. They co...
Design Templates
1. To eliminate the for designers

Giant step towards modern web

Why the
need for
new
concepts?

Editing...
Applying display templates to a result source
Demo
Which Cont rol Di splay
Template

Control Display
Template
Upcoming SlideShare
Loading in …5
×

Building Product Centric sites using Cross-Site publishing and Search [Swiss SharePoint Club, 22nd meeting]

1,110 views

Published on

This presentation presents few considerations for creating product centric SharePoint 2013 sites using newest WCM features, such as cross-site publishing and search.

Published in: Technology, Design
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,110
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
18
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • One of the enduring challenges for most Web content management tools is the conflict between the physical nature of storing content and the logical relationship between much of that content on a website. The SharePoint collaboration and content management platform is no exception.This physical hierarchy representsthe foundation of navigation and, effectively, the information architecture of any SharePoint-based application. While it is generally considered a tried-and-true approach, there are many circumstances where physically locating content in a specific navigation branch causes problems for SharePoint 2013 search tasks when structural navigation shows its limits. Ever since its introduction in SharePoint 2010, the Term Store manager and the enablement of building Taxonomies, has changed the way we classify and ultimately access content, improving findability of tagged content.For example, on content driven sites, various product pages need to appear under different navigational headings because they can be associated with multiple product categories.
  • Building Product Centric sites using Cross-Site publishing and Search [Swiss SharePoint Club, 22nd meeting]

    1. 1. Swiss SharePoint Club Creating product-centric sites using cross-site collection publishing Marius Constantinescu [MVP SharePoint Server] blue-infinity SA 22nd meeting
    2. 2. 1. Introducing Content catalogs 2. How does it work ? 3. Search-driven applications
    3. 3. Introducing Content Catalogs What are these and why do we need them? Separate presentation from storage •Different teams working on content •Different design could be applied on authoring vs. publishing sites Step by Step procedure: Identify authoring sites and publishing sites 1.    2.    Flexible and dynamic 3. 4.  Breaking down site collection boundaries •Reuse content across site collections or even farms •Not available [yet] on Office 365   5.    Eliminate large list thresholds •Take advantage of search high performance •Not needed to keep all content in a single location Allows flexible & dynamic publishing Site(-s) where content is authored Site(-s) where content is published Shared Content Identify lists to surface catalog content Add content for each searchable field Tag content (at least 1 column must be Managed Metadata) Configure list(-s) as Catalogs (via List settings) Run Full Crawl Establish Catalog Connections On Publishing sites enable metadata-driven navigation Connect to catalog-enabled lists Define Navigation settings, friendly-URLs User Interface Configure Category and Item pages Customize Display templates Configure Filters (custom properties and refiner web parts) Monitor and improve 6.  Use Search analytics reports to continuously improve
    4. 4. Information Architecture 1/2 Authoring sites / Published sites 1. Authoring vs. Publishing sites  For multilingual solutions plan authoring sub-sites to match variations labels  Different branding & design can be applied for Authoring vs. Publishing sites 2. Shared resources (images, scripts, etc.)  Apply least-privileged principles – e.g. use shared location (such as another common site collection)  Use Global Termsets if planning to reuse terms in authoring sites (integrated vs. linked)
    5. 5. Information Architecture 1/2 Navigation, Content types, fields Prod uct Code Title Description Price All from Product + Television Code Title Description Price Display Type (LCD, LED, Plasma) HD-Ready (720P, 1080P, UHD) Screen Size (40, 55, 60, 77) Com p ut er Code Title Description Price Hard drive CPU RAM Screen Size (13, 14, 15, 17) Camera Code Title Price Description Type (DSLR, Point'n'Shoot) Resolution (in MegaPixels) Optical Zoom (24x) Digital Zoom (12x) Lens Type Storage Format (SDHC, SD) Columns in Content types & Site columns are automatically promoted as managed properties in Search schema (but only as Text) 1. Identify catalog lists  What information you wish to publish (content sources) ?  Which columns should be searchable, used for filters, etc.  At least 1 column should help uniquely identify each «product item»  What information will be used in the Navigation hierarchy 2. Define content types  Shared (Reusable) Columns (prefer Site columns vs. List columns) 3. Identify data facets = future refiners (filters)  Could be different per “product” (catalog item)
    6. 6. Documents Pages Digital Assets Catalogs SharePoint Content Variations Content & Authoring FAST Search Publishing Page Framework Query Display Templates www Ext. CMS REST/OData LOB + more User Behavior (+custom events) External Content User Experience
    7. 7. List columns, Managed properties, Refiners Journey from list field to crawled > managed and rendering (refiner / display ) Televisions [Catalog] Computers [Catalog] Cameras [Catalog] Cr aw led Pr oper t ies M anaged Pr op er ties ows_q_TEXT_ProductCatalogGroupNumber Single line of text Brand Publis hingImage ows_q_CHCS_Devic eScreenSize Devic eScreenSizeOWSCHCS Refiners Content Search Web Part  Managed Metadata DeviceScreenSize owstaxIdProductCatalogItemCategory ows_r_IMGE_Publis hingRollupImage Title ProductCatalogGroupNumberOWSTEXT ows_taxId_ProductCatalogItemCategory Site Column Type ProductCatalogItemNumberOWSTEXT Content Search Web Part Title ows_q_TEXT_ProductCatalogItemNumber Site Column Title Choice Content Search Web Part 1 2 3 4 Refiners  Make sure data exists for each column before a Full Crawl [New] Site Collection Admins can trigger reindex
    8. 8. Metadata driven navigation Consistent navigation across site collections Managed Metadata driven vs. Structural navigation Centrally managed Can be used to drive global navigation  In multilingual scenarios you need to access via the Site collection Term store, not via Global.   Managed Metadata navigation Structural navigation • (+) Centrally managed in global term store • (+) Additional term sets can be injected at any location • [+] Support for Friendly URL • [+] Imperative for Catalogs • [-] Requires Publishing sites • [-] Still bound to a single Site Collection • (-) Confined to its site collection • (-) Cannot be controlled centrally
    9. 9. Metadata driven navigation, cont. Centrally managed with designated term sets 3 1  Linked terms Reused terms between term sets  2 Pinned terms Blocks changes to linked terms (read-only)
    10. 10. Configuring Metadata-driven navigation Demo
    11. 11. Category pages and product item pages Category page Catalog-Item Page
    12. 12. Refiners – why use them? What are they and why we need them? 1. Refiners are filters narrowing search results 2. They come in different types and shapes – tightly related to underlying data type  [New] Range-based (sliders) and multi-valued refiners are available 3. Only managed properties can be configured  [New] Use «Yes latent» a Farm Administrator can delegate to a Site Collection administrator the possibility to decide. 4. [New] Refinement web parts can now be configured individually inpage (horizontal or vertical)
    13. 13. Design Templates 1. To eliminate the for designers Giant step towards modern web Why the need for new concepts? Editing XSLT is a cumbersome - even for the veterans Modern Web requires Standardization – empower Power-Users Client-side "templating" techniques are current trends (e.g. Knockout, Kendo UI, Razor) Re-usable Styles Files for your Content based & Search Results Web-Parts Where does one use "Design templates" ? What are design templates? and power users to work with XSLT (& the use of ddwrt JavaScript functions) each time they a new look & feel is needed, SharePoint 2013 introduces Design Templates. 2. Each display template consists of two files (in Master Page library under Display templates):  Search Results & Web parts, Catalog reuse web parts Access to Master Page library Your favorite web development tool (even Notepad) to create them  What does one need to create a new template ?   An HTML file (.html) - the actual template JavaScript File (.js) - the script that makes the magic happen – automatically generated jQuery supported, or custom Javascript and CSS Custom managed properties can be displayed (from search results)
    14. 14. Applying display templates to a result source Demo Which Cont rol Di splay Template Control Display Template

    ×