Web Templates of SharePoint

BY: SHAHZAD

Audience: Starter/beginner levelPRESENTATION AGENDA1. INTRODUCTION TO SP132. SP ON PREMISES VS ONLINE (O 365)3 . WEB TEMPLATE VS SITE DEFINITION VS SITE TEMPLATES4. WEB TEMPLATE DEVELOPMENT VIA VISUAL STUDIO5. BUILD IN WEB TEMPLATES

Collaboration1.1 Team Site1.2 Blog1.3 Developer Site1.4 Project Site1.5 Community Site

Enterprise2.1 Document Center2.2 eDiscovery Center2.3 Record Center2.4 BI Center ( N/C)2.5 Enterprise search center(N/C)2.6 My Site Host(N/C)2.7 Community Portal2.8 Basic Search Center(N/C)2.9 Visio Process Repository(N/C)

Publishing3.1 Publishing Portal3.2 Enterprise Wiki3.3 Product Calalog(N/C)

SP Online Vs On primisesEnd User perspectiveNo difference , both over SSL/HTTP pipeIT Manager perspectiveIT infrastructure and related tasks (servers, hardware, licensing, backup, disaster/recovery, building, etc.) - No need in cloud SLA promises a system availability > 99.9% Developer perspective• Using the browser functionalities are

same• Using SharePoint Designer, customize

pages, integrate data from external applications (through web services), manage workflows

• Third party or self- made webpart, feature or solution - Not allowed

• Custom in specific plans - using MSOCAF

• SP Online ( Office 365) have plans• SP on premises( Foundation +

Standard + Enterprise )

Key conceptsWeb vs SitePublic web site vs Private site collectionWeb Part vs AppApp vs App part Wiki Page, web part page , application page vs Publishing Page

Site Definations

Classic WebTemp*.xml and onet.xml combination, which are located in the file system of server.

WebTemp*.xml file is used to introduce the template for SharePoint and onet.xml file contains the actual instruction or definitions concerning which features to activate when site is created.

Used to provision out of the box sites. only deploy site definitions using farm solutions Default available throughout the farm in every application, unless we

limit the visibility either using AvailableWebTemplates attribute for publishing sites or more generally available VisibilityFeatureDepency attribute in the WebTemp*.xml file

Demo

Web templates

New feature element available in SharePoint 2010, which provides us flexible way to define definition (onet.xml file), which will be used only on provisioning time, when the site is created. There are no references to the definition on runtime, which provide easy maintainability for the definition. Two files for each of the web templates: Other one is empty element (is VS2010 is used) for defining

the actual WebTemplate element Other one is completely similar onet.xml file as for site

definitions, with few exceptions

Web templates

Feature, which will be responsible of deploying the web template. WebTemplate element is supported in two scopes, which are Farm and Site.

One big advantage of the web templates is the fact that since they are feature based and there won’t be any files stored in file system, those are completely supported usually by the cloud services, like MS Online (BPOS).

Web templates compared to the site templates is the fact that we can utilize the publishing features in web templates

Demo

Onet XML file Specifies the web-scoped and site collection-scoped Features that are built-in to websites Specifies the list types, pages, files, and Web Parts that are built-in to websites Defines the top and side navigation areas that appear on the home page and in list views

for a site definition Specifies the list definitions that are used in each site definition Specifies document templates that are available in the site definition for creating document

library lists in the UI, and specifies Defines the base list types from which default SharePoint Foundation lists

Feature stapling

Ways to extend the site definition Create a site from the definition and subsequently deploy your

features to the site. Include the features in the site definition (onet.xml) before using it to

create sites. Use feature stapling to associate your features to the site definition.

Feature stapling

To extend and customize existing site definitions. (Out of box plus custom site definition)

Stapled features are only activated on provisioning time, so if there’s any existing sites already provisioned, those won’t be affected automatically just by deploying new stapling definitions.

Doesn’t work if you are provisioning sites using site templates or web templates, even though these both options refers to root site definition.

Demo

Site Template

Save site as template, SharePoint generates full fledge solution package (WSP file), which can then be moved between any environment containing all site level objects, like libraries and optionally also content.

Not supported when publishing features are enabled. Because Publishing sites have complex references and dependencies.( link is hidden)

Unless you import them to Visual Studio and modify its settings, they are only available on site collection level

Demo to explain, Save as , Deploy on a site collection, Import in Visual studio , deploy on Farm

Using SPWebProvisioningProvider

Create a class which inherits from SPWebProvisioningProvider and implement the Provision method. Use props.Web.ApplyWebTemplate to apply the template to your

web Run your custom code Hookup the class as a provisioning provider in your Configuration

elementDemo

Team Site

Apps in SP 2013 compared to the Lists and Libraries in SP 2010 No Calendar, Task List, or Discussion Board by default "Team collaboration lists" provide the following: Libraries Form Library, Picture Library, Document Library Lists Announcements, Calendar , Contacts, Custom List, Custom List with DataSheet View, Discussion Board , External List , Issue Tracking List , Links Project List , Survey , Tasks

Key conceptsDOCUMENT TEMPLATECOMMON FOLDERS ( WHY 14 N 15)LIST VS LIBRARYWHY FORM LIBRARY

Blog• Based on Collaborative List feature.

• Basically a application based on Collaborative list feature with some web parts, XSLT based view and

custom implementations for navigation, themes elements and business logic for blog general concepts.

Customization• Modify Web part page via Edit web page option by site

administrator• Customize XSLT for current pages presentation in SP

Designer• Add new fields to current four list in blog and customize

add/edit for new fields via SP Designer• Create a new web template based on this template in

visual studio and customize web template in visual studio by adding new web parts, list, or custom logic

• Demos

Developer Site

extensively for App development the corporate App catalog or the Microsoft App Store for distribution , Not Developer site

Project Site

An easy way to manage smaller projects Very Close to Team site template Same features, such as a Documents libraryand same row of tiles available on the Team Site The Project Summary web part with task list Calender list with different views For bigger projects, consider Project Server

Community Site Works as Discussion forums Important list include: categories , community Members, Badges, Discussion list Community settings, site settings

Document Center

Works for : Authoring environment: create and edit thousands of documents or media assets that are stored in a central repository. Content archive:such as a knowledge base, users store or view documents Document ID:

Manage your documents by providing an easy way to track items regardless of their location Configure Document ID Write Custom Document ID provider

Version Control: SP 10 keeps full version of document, SP 13 keeps only changes Compare versions Content Type: specific kind of content together with a group of settings for the content

In place - Record Features

In Place record management By default feature , not enabled record management settings at site level record management settings at Library level Central Record Management Create send to connection ( Options as Copy , Move , move&link)

In Place Hold Feature

Can Enable Hold Feature to site Site settings >>

Configure Hold Define a Hold Definition Define a Hold Report

Central Hold Feature

Document Center

Content OrganizerUsage Route documents to different libraries or folders Upload all documents to a Drop Off Library Manage folder size Manage duplicate submissions Maintain audit logsSite settings: Activate the Content Organizer feature on a site Configure the Content Organizer to route documents

Document Center

Managed Metadata Metadata is information about information.TaxonomyA taxonomy is a formal classification system. A taxonomy groups the words, labels, and terms that describe something, and then arranges the groups into a hierarchy. FolksonomyA folksonomy is an informal classification system. It is evolves gradually as web site users collaborate on words, labels, and terms on a site.By using a folksonomy, content classification can evolve together with changing business needs and user interests.

Document Center

Term SetA Term set is a group of related terms. Different scopeLocal term sets: are created within the context of a site collection, and are available for use (and visible) only to users of that site collection.Global term sets are available for use across all sites that subscribe to a specific Managed Metadata Service application.TermsA term is a specific word or phrase that you associated with an item on a SharePoint site. It is a single item in a term set. A term has a unique ID and it can have many text labels (synonyms). Managed terms Managed terms are terms that are pre-defined. Term Store administrators organize managed terms into a hierarchical term set. Enterprise keywords An enterprise keyword is a word or phrase that a user adds to items on a SharePoint site. The collection of enterprise keywords is known as the Keywords set.

Document CenterTerm Store Management ToolThe tool that people who manage taxonomies use to create or manage term sets and the terms within them.Managed Metadata column a special kind of column that you can add to lists or libraries. It enables site users to select terms from a specific term set.Enterprise Keywords column column that you can add to content types, lists, or libraries to enable users to tag items with words or phrases that they choose. By default, it is a multi-value column. Social Tags Words or phrases that site users can apply to content to help them categorize information in ways that are meaningful to them.

Record Center

Central repository in which an organization can store and manage all of its records Capabilities:

Vault abilities Information management policy enforcement

Auditing Expiration Barcodes

Record collection programmable interface Record routing Hold

Record CenterRecords management planning File plan Retention schedule Compliance requirements document Formal process for suspending the disposition of records System for monitoring and reporting the handling of records

eDiscovery Center

How records managers and litigators discover content in electronic format. To manage preservation, search, and export of content stored in Exchange and

SharePoint across SharePoint farms and Exchange servers. Minimizes storage space and maximizes efficiency, eDiscovery uses copy on write

to manage identical copies of the same information. Case : eDiscovery case. Associated with a specified SPWeb object Custodian : Represents a custodian associated with a case. For case , 2 steps action:

Identify and Hold Search and Export

eDiscovery Center

In-Place eDiscovery in Microsoft Exchange Server 2013 and Exchange Online can help you perform discovery searches for relevant content within mailboxes.

eDiscovery Center

Theory:Electronic discovery (or e-discovery or ediscovery):to discovery in civil litigation or government investigations which deals with the exchange of information in electronic formatElectronic Discovery Reference Model (EDRM) format for export. Stages of e-Discovery1.Preservation2. Collection3. Processing4. Review5. Production

Publishing Portal

Publishing sites are different from Team sites. Team sites generally have a large amount of contributors while a publishing site's content is controlled by a few contributors and there is a large number of consumers for the site's content. Publishing sites are used for creating internet sites or large divisional intranet sites.

Publishing Architecture

New tab called Publish, and on that tab are Submit, Approve, schedule and Reject buttons. Submit kicks off the workflow by routing the current page to one or more approvers for review.Scheduling button opens a dialog box where you can specify when the page should be published and when, if ever, it should be retired.

Role as : Information Architect , Visual Designer , Developer

Publishing Architecture

On enable the publishing infrastructure feature:At Site Collection Level: Content and Structure Reports list. Used to customize the queries that appear in the View

list in the Site Content and Structure tool Reusable Content list. Contains HTML or text content that can be inserted into Web pages Site Collection Documents library. Stores documents that are used throughout the site

collection Site Collection Images library. Stores images that are used throughout the site collection. At Site Level: Pages library. Stores site pages Images library. Holds images used on site pages Documents library. Contains all documents used on site pages

Publishing Architecture

In a publishing site, the master page is updated to include a Publishing tab(scheduling and workflow buttons )

Content types:Article Page, Project Page, Welcome Page, Enterprise Wiki Page, and Redirect Page. Two additional content types, Reusable HTML and Reusable Text, are added specifically for the Reusable Content list.

Page layouts: Image on Left, Image on Right, and Splash. These page layouts are automatically associated with the content types mentioned above when the publishing features are enabled.

Columns :Page layout columns are Byline and Page Content. Publishing columns added at the site collection level are Article Date, Scheduling Start Date, and Scheduling End Date. A custom Wiki Categories column that uses managed metadata for Wiki pages is also added at the site collection level.

Publishing Architecture

Design ManagerDevicesLocalization build in support (Varaiations)

Enterprise Wiki

Many to many contributor/visitors Wiki wiki means "quick" in Hawaiian. The first wiki was created by Ward Cunnigham in 1995. Unstructured data Lists: Categories, Rating