SharePoint 2013 Web Content Management for Developers TSPUG

{ About.Me() }
https://mvp.support.microsoft.com/profile/Ed.Musters
• Current SharePoint MVP
• Author for two SP 2010 development books
• SharePoint Architect for Infusion
• Speaker at International Conferences on
SharePoint, at user groups, and at
SharePoint Saturdays
• Certified Trainer for the industry leading
SharePoint training from Critical Path
Training
• Telerik “Insider”
• Holds all MS certifications for SharePoint
2010
• Harley-Davidson ™ Enthusiast!

London Kraków Dubai New York Toronto Boston

6
And, yes, I do really have a Black
Belt. 

Prize! Telerik DevCraft Ultimate Collection

Full Trust Solutions
What are Full Trust Solutions?
• Solution Packages (WSPs) are installed to SharePoint
Server
• Typically, compiled .NET code is deployed to GAC
• Files are pushed physically to the SharePoint Root
directory
• More limited cloud scenarios via « SandBox » solutions

Full Trust Solutions
When are they suitable?
• If you have an on-premise deployment of SharePoint
• You have lots of existing solutions in SP 2007 / 2010
– That is, solutions you may want to re-use / migrate
• You are an ASP.NET web forms developer
• Can SandBox for cloud solutions (but deprecated)
• Cannot be app – such as timer job, admin page

Full Trust Solution Development
How are they developed?
• « Traditional » development using Visual Studio /
C#
• Program against the SharePoint Server object model
• Package using VS tools to SharePoint Solution
Packages (WSPs)
• Deploy to Farm, typically using PowerShell.
• SandBox solutions would be uploaded / activated

Solution Packages
• Solution Packages are sets of
functionality deployed to the farm or
site collection (sandbox)
• May contain one or more Features,
assemblies, pages, controls, and
other artifacts
• SharePoint framework handles
installation and configuration of
solution items
• Automated packaging and
deployment in Visual Studio 2010
Web Parts
Assemblies
Mapped
Folders
WSP

Features
• A ‘Feature’ is a defined set of
functionality encapsulated
within a specific format
• Features may be comprised of
any combination of code,
including web parts, workflows,
and site definitions
• Features may be deployed
individually or as a part of the
solution package
Solution
Feature
XML
Receiver
Assembly
Project Item
Web Part Template Workflow

Sample App – Footer Links
• Illustrates a very common development
pattern
1. Define schema: Site Columns and Content Types
2. List Provisioned with attached content types
3. A Web Part that performs a content query against
the content type / SP List

Solution Structure and Dependencies

Using Existing SP 2010 Solutions
Possible To:
• Deploy Existing Solutions
• Will deploy to « 14 » folder in SharePoint 2013
• Add « 14 » property to manifest!
SharePointProductVersion="14.0"

Convert VS Solutions from SP 2010
Possible To:
• Open Solution in VS 2012
• Change to latest Framework Version
• Change SharePoint References
• Add « 15 » property to manifest
SharePointProductVersion="15.0"

Convert VS Solutions from SP 2010
My Strongest Recommendation!
• Create New VS SP 2013 solution
• Ensure Package Name is different (e.g. append 2013)
• Bring in code / files from SP 2010
• Ultimately package structure should be identical
• Ensure feature names and IDs are the same
– OR
• Create with new feature IDs

SP 2013 Full Trust Solution
• Deploy as a WSP file (i.e. solution package)
• Deploy to the Farm
• Suitable for an on-Premises deployment only
• Absolutely a supported model for SP 2013!
• Very similar to developing full trust solutions for
SharePoint 2010

• Design Manager
• Image Renditions
• Device Channels
• Image Renditions
• Multilingual
Web Content Management in SP 2013
• Search Driven Publishing Model
• Content Search Web Part
• Content Catalog
• Managed Navigation
• Cross Site Publishing

Web Content Management in SP 2013
In short, the model we use today for publishing sites in SharePoint 2010 is still “valid”, as
fundamentally publishing works the same way in SharePoint 2013
Deploy solutions to an on-premise farm
Since SharePoint 2013 has a complete “14” folder – it should be possible to “migrate” SP 2010
sites “as is” to a SharePoint 2013 box and have it run in “legacy” mode.
How we do branding in SharePoint 2013 has been completely changed with the introduction of
the Design Manager, making it dramatically easier to create such as master pages and page
layouts.
No more custom “branding solutions” in Visual Studio!
A very compelling Search driven publishing model has been added in SP 2013, making it possible
to create a publishing site featuring content from multiple site collections.
Information Architecture and Site Design become much more interesting!

The following slides on web content management in SP 2013 courtesy of Microsoft and the SP
2013 Conference
Wanted to give credit where it is due!! 
Acknowledgement!

138
19 13
0
20
40
60
80
100
120
140
160 W3C HTML Markup Validator Errors

Clean URLs http://www.c.com/cars
Home Page Redirects None
Country code top-level
domains (ccTLDs)
http://www.c.com/cars
http://www.c.mx/coches
XML Sitemaps Automatically generated and referenced in
robots.txt
SEO Properties Browser title, Meta description, Meta keywords
Canonical URLs
Webmaster Tools integration Assists with ownership verification

Comps
CSS,
JS, etc.
HTML
Dreamweaver /
Photoshop / etc.
SharePoint Designer

SharePoint
Dreamweaver / etc.
Auto
Convert
Snippet
Gallery
Add controls
Upload
Comps
CSS,
JS, etc.
HTML

0
400
800
1200
1600
2000
2005 2010 2015 2020
INTERNET
USERS
(MM)
Global Mobile vs. Desktop
Internet User Projection,
2007-2015E, by Morgan
Stanley
Mobile Desktop
Customized Design,
Fewer bytes over the wire
… all while maintaining Search Engine
Optimization?

Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0;
Trident/6.0; IEMobile/10.0; ARM; Touch; NOKIA; Lumia 920)

Examples of Search Driven Publishing
“Why wouldn’t
everything be
search driven?”
or in other words
“Are there times we
might not use
Search Driven
Publishing model?”
News
Commerce
Support
Knowledge Base
Internet
Intranet
Extranet
Mobile
Articles
Pictures
Video

Advantages of a Search Driven Publishing Model
Breakdown site
collection
boundaries
Eliminate large
list thresholds
Allows for
flexible &
dynamic
publishing
Separate
presentation
from storage

What makes it “Search Driven”
Q: “Don’t most
web sites already
have Search?”
A: Yes
“It’s not about searching
what we have published,
it about publishing,
republishing and
targeting content that we
have crawled…”

Index
SharePoint Content
Search
Publishing
External

What goes into making the Search Driven
Publishing Model?
Content
Search Web
Parts
Display
Templates
Query Builder
Query Rules
Content
Catalogs
Managed
Navigation

Audio
Cameras
Computers
Home appliances
Phones
TV and video
Adaptive experiences empower web developers to create portals
based on managed navigation and a few dynamic pages
Audio
Cameras
Computers
Home appliances
Phones
TV and video
Friendly URL
http://contoso.com/cameras
Use page
maincategory.aspx
Microsoft Confidential
Search
CONTENT SEARCH WEB PART
TERM STORE
NAVIGATION
TAXONOMY
Filter query by
CATEGORY: Cameras

Audio
Cameras
Computers
Home appliances
Phones
TV and video
TERM STORE
NAVIGATION
TAXONOMY
Friendly URL
http://contoso.com/computers
Use page
maincategory.aspx
Adaptive experiences empower web developers to create portals
based on managed navigation and a few dynamic pages
Search
CONTENT SEARCH WEB PART
Filter query by
CATEGORY: Computers

Content Search Web Part Content
Search
Web Parts

Display Templates
Make your own
in HTML &
JavaScript
Many ship Out-
of the-Box

Query Builder
IW focused
UI based
Allows
“advanced
mode”
Provides
Test & Preview
Add Refiners

Query Rules
IW focused
Manipulate
Search Results
UI based

Adaptive experiences powers flexible consumption and re-use by separating content
management and site experience workflows
Combining static and dynamic content through Search
PRODUCT CATALOG JOB OPENINGS
ASSET LIBRARY
ARTICLES NAVIGATION

Adaptive experiences empower business users
with editorial control to maximize business goals

Content Catalogs
Available
across Farms
A settings on a
List or Library
Integrated with
Search
Product
Catalog Site
Template
Define URL
Format
Select Nav
structure
1a. Enable
2. Index 3. Connect
1b. New

Catalog Enabling Catalog Connection

Managed Navigation
New Nav
Provider
Friendly URLS
Product
Catalog
integration
Terms can be
site structures
1:1 binding of
Site Collection
to Term Set

“Create content in an Authoring
environment and use it in any
one of your SharePoint publishing
environments.”
Cross Site Publishing
URL
manipulation
Multi-branding
Authoring and
Production
tiers
Multilingual
Things to know:
1. This is not content
deployment
2. Requires the
Publishing feature
3. Requires a Catalog
Flexibility in
Page Content

Cross Site Publishing
Why XSP?:
1. Need to Publish >1
location
2. Need a multilingual site
3. Need to separate authoring
and publishing

SharePoint App Model
Is this not THE new way to develop for SP?
• This was all that was talked about at the MS
SharePoint Conference!
• No code is deployed to the SharePoint servers
• You may choose any technoloogy, you host it
• Apps are published – coporate store or public
marketplace
• Suitable for on-premise or cloud (Office 365)

SharePoint App Model
When are Apps suitable?
• If your primary purpose is to access data in SharePoint
• Your custom solution is a new one
• App is not ASP.NET – iOS, Win 8, Win Phone, MVC, LAMP
(PhP)
• Leverage pure web dev skills – HTML, CSS, JavaScript
(jQuery)
• You want to be able to move from on-premise to Cloud

App Model Overview
• For On Premise or Cloud Scenarios
• App code never runs on the SharePoint box
• App accesses SharePoint via web services
• Can use a Client Side Object Model approach
or a REST services approach
• Apps deployed to catalog (could be MS Store
or Corporate catalog)
• Have a Site or Tenancy scope

App Hosting
• SharePoint-Hosted Apps
– App resources added to SharePoint host
– Deployed to child site known as app web
– App can have client side code only
• Cloud-Hosted Apps
– App resources deployed on remote server
– Remote site known as remote web
– App can have client and server side code

Client Side Object Model (CSOM)
• Two main kinds:
– Managed CSOM (.NET / C# code)
– Javascript CSOM (aka JSOM)
• Similar to the old-school OM (which it ultimately
calls) but with extra considerations for
– Serializing and downloading only what you need back
from the server
– Minimizing the number of HTTP requests
– Async nature of JavaScript
• Keywords: Object Model

CSOM Improvements
• New APIs with SharePoint Server functionality
– User Profiles
– Search
– Taxonomy
– Feeds
– Publishing
– Sharing
– Workflow
– E-Discovery
– IRM
– Analytics
– Business Data

Search Queries: CSOM
ClientContext clientContext = new ClientContext(siteUrl);
var query = new KeywordQuery(clientContext);
query.QueryText = "Search terms";
SearchExecutor searchExecutor = new SearchExecutor(clientContext);
var resultCollection = searchExecutor.ExecuteQuery(query);
// process results
clientContext.ExecuteQuery();

REST Api
• REpresentational State Transfer
• Language-independent (only requires HTTP)
– I.E. JavaScript or C#
• Formulate an HTTP request to get something back
(GET) or get something done (POST or PUT)
• SharePoint’s REST API obeys OData (Open Data)
specification (well-known standard syntaxes for
querying/filtering, machine-traversable entity
relationships)

Search Queries: REST
• Keywords:
http://[..]/_api/search/query?querytext='{KQL Query}'
• Selecting Properties:
http://[..]/_api/search/query?querytext='test'&selectpr
operties='Title,Rank'
• Sorting:
http://[..]/_api/search/query?querytext='test'&sortlist
='LastModifiedTime:descending'
http://[..]/_api/search/query?querytext='test'&sortlist
='LastModifiedTime:descending,Rank:ascending'

CSOM or REST?
CSOM REST API
JavaScript YES YES
C# YES YES
Translation: 4 possibilities, all technically possible
CSOM REST API
JavaScript MAYBE BEST (Usually)
C# BEST (Usually) MAYBE
Translation: Focus on the 2 combinations that (usually) work best

Conclusion – Full Trust
• Full Trust Solution Development is still cool!
• Tradtional ASP.NET / C# web form
development
• Can “migrate” source code from 2010
Publishing solutions
• Great option for On Premise installation

Conclusion - Apps
• SharePoint Apps are the future direction for
SharePoint development
• Your first choice for new development
• Can be SharePoint or Cloud Hosted
• Suitable for On Premise or Online
• REST is API of choice for SP interaction
• Don’t need a local dev environment!
– Develop against SharePoint Online

Other WCM Considerations
• Migrating your brand to SP 2013 via Design
Manager
• Think Mobile! Responsive Design, Device
Channels, Image Renditions
• Search Driven Cross Site Publishing: Catalog
site, Content by Search Web Part, Metadata
Navigation

Questions? Discussion
• Ed Musters
• emusters@infusion.com
• @TechEdToronto

SharePoint 2013 Web Content Management for Developers TSPUG

More Related Content

What's hot (20)

Viewers also liked (9)

Similar to SharePoint 2013 Web Content Management for Developers TSPUG (20)

More from Ed Musters (11)

Recently uploaded (20)

SharePoint 2013 Web Content Management for Developers TSPUG

Editor's Notes