SharePoint Fest Chicago Web Content Management in SharePoint 2013

Post on 17-Nov-2014

437 views 1 download

description

Slides from a session about the Publishing Infrastructure Features and Cross Site Publishing in SharePoint 2013.

Transcript of SharePoint Fest Chicago Web Content Management in SharePoint 2013

Understanding Web Content Management in SharePoint 2013

Patrick Tucker

patrick.tucker@sharesquared.com

About Me

15 years in the business

SharePoint since 2005

Live in the proud state of KY

Work for ShareSquared

Our Goal Today

Review the SharePoint Publishing Infrastructure features

Understand how to create and publish content

Getting From Here to There…

Two Approaches

Author In PlaceCross Site Publishing

The “Old” Way

Author In Place

Requirements: Publishing Site Template or…

Publishing Infrastructure Site Collection Feature

Publishing Site Feature

A “Pages” library created by the features being activated

Creating Content

Create page from

layout

Add layout metadata as needed

Add content on

page

Check in and publish

Approver completes publishing

Enhancements to Content Creation

You can now set Search Engine Optimization settings on each publishing page (except in Foundation)

Image Renditions allow quick and easy format selection

The “Embed” ribbon item & Script Editor Web Part allow for easier insertion of code

Images, Video, Scripts and Stuff

When adding images, videos, etc. to the Rich HTML field, another library is needed

Site Assets is a great location for this kind of content

Make sure that users who can view pages, also have access to the assets library

Use the Draft Item check before publishing

Demo

The “New” Way

Cross Site Publishing

Requirements: Cross Site Publishing Feature

Enterprise, Enterprise, Enterprise

Creating Content

Content is created in an authoring site

where cross site publishing is

enabled

Content is crawled by the Search

engine

Query results are shown in web parts across publishing site collections

So content is created in one site and viewed in others

But I Don’t Sell Products…

Product Catalog Site may not be what it sounds like

Site Columns, Content Types and a “Products” List are just templates really

Managed properties are a key but will likely be automatic

Setting up Cross Site Publishing

So what do we need? Either a Product Catalog Site or enable the Cross-Site Collection Publishing Feature

“Catalog enabled” lists and/or libraries

A term set with tags to apply to “catalog” items

A crawl of tagged content

A connection from a Publishing Site to the Catalog Site

Configured Content Search web parts

Catalog Lists and Libraries

Can be configured in list or library settings

Up to 5 Item URL fields are defined

A Navigation Hierarchy field is defined to create pinned navigation elements

Making the Connection

When connected to a publishing site collection, a “Result Source” is added

This can be used by the query defined in a “Content Search Web Part”

Category Pages

Special page layouts that are used for displaying structured catalog data

 There are only two pages to maintain here, not several

One for all “categories” and one to show a specific category

You can create a page that just applies to a single URL

Friendly URLs

You are still using a page in the “Pages” library, but mapping category and item URLs

Content Search Web Part

The Content Search Web Part is the piece of the two page templates

The query automatically restricts by the navigation terms

Add a Property Filter to map a managed property to a URL token

Demo

Display Templates

This is how we control the look and feel of results defined by the query

Some display templates are built in

A Closing Thought

The “old way” of publishing uses a pages library to contain multiple pages with their own individual content.

The Pages Library can be catalog enabled.

Maybe we could just have one site containing pages which are then published to all other sites to display. This is kind of like the Content Type Hub.

Questions?

Patrick.Tucker@ShareSquared.comTwitter: @TuckersNet