Navigation in a Multi Site Collection EnvironmentAlbert-Jan Schot

Albert-Jan Schot

work: Maventionblog: http://www.sharepointappie.nlmail: appie@mavention.nltwitter: @appieschot

Agenda

Why? What? How?

Why

would you use Site Collections?

Why

Why

Scalability Settings

Scalability ‘Less’ limits Can be moved between databases Can be monitored (quota’s)

Limits and boundaries 300 Content Databases per WebApplication 2,000 Site Collections per Content Database

200 GB a Site Collection 250,000 sub sites 5000 (max 50.000) unique permissions per scope (SPList, SPWeb, SPSite)

Settings Shared permissions Shared template galleries Content Types Navigation

What

types of navigation are there?

Click to insert photo.

Top navigation

Left navigation

View selector

Breadcrumb

What

Top navigation<SharePoint:AspMenu ID="TopNavigationMenuV4" Runat="server" EnableViewState="false" DataSourceID="topSiteMap" AccessKey="<%$Resources:wss,navigation_accesskey%>" UseSimpleRendering="true" UseSeparateCss="false" Orientation="Horizontal" StaticDisplayLevels="2" MaximumDynamicDisplayLevels="1" SkipLinkText="" CssClass="s4-tn" />

Left navigation<asp:ContentPlaceHolder id="PlaceHolderLeftNavBarDataSource" runat="server" /><asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat="server" /><asp:ContentPlaceHolder id="PlaceHolderLeftNavBarTop" runat="server"/><asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server” /><asp:ContentPlaceHolder id="PlaceHolderQuickLaunchTop" runat="server“ /><Sharepoint:SPNavigationManager

id="QuickLaunchNavigationManager"runat="server"QuickLaunchControlId="QuickLaunchMenu"ContainedControl="QuickLaunch"EnableViewState="false"CssClass="ms-quicklaunch-navmgr">

View selector<h1 name="onetidProjectPropertyTitle">

<asp:ContentPlaceHolder id="PlaceHolderSiteName" runat="server"><SharePoint:SPLinkButton runat="server" NavigateUrl="~site/" id="onetidProjectPropertyTitle"><SharePoint:ProjectProperty Property="Title" runat="server" /></SharePoint:SPLinkButton></asp:ContentPlaceHolder>

</h1><span id="onetidPageTitleSeparator" class="s4-nothome s4-bcsep s4-titlesep"><SharePoint:ClusteredDirectionalSeparatorArrow runat="server" /> </span><h2>

<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea" runat="server" /></h2>

Breadcrumb<SharePoint:PopoutMenu

runat="server"ID="GlobalBreadCrumbNavPopout"IconUrl="/_layouts/images/fgimg.png"IconAlt="<%$Resources:wss,master_breadcrumbIconAlt%>"IconOffsetX=0IconOffsetY=112IconWidth=16IconHeight=16AnchorCss="s4-breadcrumb-anchor"AnchorOpenCss="s4-breadcrumb-anchor-open"MenuCss="s4-breadcrumb-menu">

How

can managed metadata help you?

“Navigation should be easy, very easy”

How Clients & Projects Document Management Employees work on different clients (and projects)

Collaboration Portal1 site collection / client

1 subsite / project

Webtemplates for both

Only custom code for breadcrumb

How Termset with region / location Location to store info in Template for Clients / projects Custom code for breadcrumb Custom code for ‘overviews’

Demo

Recap ContentType and Pagelayout with term Webtemplate to define navigation settings Custom code to render ‘our’ breadcrumb

Future Term itself does not map to a node No ‘friendly’ urls Will require migration

Still only a basic breadcrumb in 2013

Q&A

Code example

SPConnections13.zip