SharePoint 2010 Basics for newbies

Sachchin Annam

AgendaSharePoint 2010 OverviewFarmWeb ApplicationSite CollectionSites/SubsitesList & LibrariesPagesBranding in SharePoint using CSS and JavaScriptWebparts

Microsoft's marketing tagline describes SharePoint 2010 as the

"Business Collaboration Platform for the Enterprise and the Web“

and explains that it will: Connect and empower people Cut costs with a unified infrastructure Rapidly respond to business needs

SharePoint can also be described as: Web Platform Collaboration Platform Search Provider Presentation Layer Development Platform Social Networking Platform

SharePoint 2010 Overview

Farm and Web Application FarmSharePoint farm is a logical grouping of SharePoint servers thatshare common resources. A farm will typically operate standalone, but it can also subscribe to functionality from anotherfarm, or provide functionality to another farm. Each farm has itsown central configuration database.

Web applicationsThey are typically the interface through which a user interacts withSharePoint. It is associated with a set of access mappings or URLs which are defined in the SharePoint central management console, then automatically replicated into the IIS configuration of every server configured in the farm. They are independent of each

other,have their own application pools, and can be restarted independently in

IIS.

A SharePoint site collection is a set of sites that can be managed together.

Sites within a site collection have common features, such as shared permissions, galleries for templates, content types, and Web Parts, and they often share a common navigation.

A site collection contains a single top-level site, and any number of subsites can be organized in a hierarchy.

The site collection is typically created using one of the out of the box SharePoint site templates for the root site that is provisioned with it.

Site Collection

Site CollectionSite Collection Templates Category:

Illustration of Site Collection :

Collaboration Site Templates

Meeting Site Templates

Enterprise Site Templates

Publishing Site Templates

Elaboration of each category and its templates

Why to go for Site Collection:There are many reasons why you might chose to create a

site collection in SharePoint:

Unique set of users and permissions Unique and separated content databases are possible,

which allow for multiple large (200GB+) sites Unique shared quotas Upgrade to next version can be done in a phase

approach

Site Collection

A Site/Subsite is a single SharePoint site within a site collection.

A Site/Subsite can inherit permissions and navigation structurefrom its parent site or can be specified and managed independently.

Creation of Site/Subsite can be done by users of a site collection, but creation of site collections must be performed by a service administrator.

List of Site Templates which are provided by SharePoint 2010

http://office.microsoft.com/en-in/sharepoint-server-help/a-preview-of-the-sharepoint-server-2010-site-templates-HA101907564.aspx#_Toc265154586

http://www.dummies.com/how-to/content/sharepoint-2010-site-templates.html

Site / Subsite

SharePoint 2010 provides many kinds of lists that you can use to track information.

SharePoint provides several predefined lists. These lists have columns and forms that make it possible

for you to track everything from contacts to tasks.

SharePoint provides three basic kinds of lists:

Communications lists are used to track announcements, contacts, and discussion boards.

Tracking lists are used to track information such as links, calendars, tasks, issues, and surveys.

Custom lists provide a starting template that you can build on to create a list with the exact columns you need.

Lists in SharePoint

Type of list When to use itAnnouncements To display brief announcements on your site’s home

page.

Contacts To track contacts, especially if you want to use Outlook for data entry.

Discussion Board To create a discussion forum where people can post messages and reply to them.

Links To track hyperlinks.

Calendar To track calendar items.

Tasks To track tasks.

Project Tasks To track work items for a project.

Issue Tracking To track trouble tickets.

Survey To take a poll.

Custom To create a list with columns that you define.

Import Spreadsheet

To create a list based on an existing spreadsheet.

External To create a list based on a data source outside SharePoint.

Types of lists in SharePoint 2010

A library is a container for creating, organizing and managing different types of documents.

It allows us to store files and meta information about the files, so that it can be used among different team members.

Everything that applies to lists also applies to libraries. You can create, store and manage almost every type of

file in different kinds of libraries such as :

etc.

Libraries in SharePoint 2010

Types of Libraries in SharePoint Type of libraries

Description

Asset Library lets you add, browse, share, organize and mange images, audio and video files.

Data Connection Library

Here you can create, browse, share, organize and manage files that contain information about connecting to external data connections.

Document Library

Here you can create, browse, share, organize and manage documents or other files.

Form Library Here you store and manage Microsoft Office InfoPath forms (or XML files for use with Microsoft Office InfoPath) for instance business forms like a status report, purchase orders, etc.

Picture Library Here you can upload and share pictures with others and it includes a built-in image viewer.

Report Library Here you can create web pages and reports to track business metrics, goals, KPIs (Key Performance Indicators) and business intelligence information.

Slide Library It allows you to create a library for storing and sharing Microsoft PowerPoint slides.

Wiki Page Library

It allows you to create and store customizable pages of content that are linked together and can be edited by several people.

Pages in SharePoint For displaying any type of information in SharePoint, we

need pages. SharePoint provides 3 types of pages namely:

Page Default Location Typical Usage Scenario

Publishing Page

Pages library Complete control over look and feel; more granular content management.

Web Part Page None; can reside in any library or folder

To display Web Parts; no content management requirement.

Wiki page Site Pages or in wiki libraries

Displays webparts and page can be edited in browser

How SharePoint Looks like :

Web ApplicationFarm

Web Application

Site Collection

Sites

List and Libraries

Web Application

Site Collection

Site Collection

Site ListsLibrarie

s

SiteListsLibrarie

s

Documents

Items Folders

Permission Types

Full Control – Enables users to have full control of the website.

Design – Enables users to view, add, update, delete, approve, and customize items or pages in the website.

Contribute – Enables user to add, view, update and delete his own item.

Read – Enables user to read item/pages

Permission Levels

• Site level• List or document library level• Folder level• List item level

Permission can also be applied on webparts using Target Audience.

Permissions

Branding in SharePointMaster Page Master pages are a feature of ASP.NET 2.0 that work the

same way in SharePoint. The default master page is located in the Master Page

Gallery. In SharePoint Designer, the Master Page Gallery is the masterpage folder, which is located in the _catalogs folder in the Folder List.

za

Benefits of using master pages: An enhanced experience for editing SharePoint pages Site-level editing Professional-looking sites More consistent pages and an enhanced end-user experience Efficient site management

CSS/JavaScript in Master Page

In SharePoint, the CSS reference is given in 2 ways: <link rel="stylesheet" type="text/css" href="mystyle.css" /> <SharePoint:CssRegistration

name="/CommunityImages/Insight_copy(new).CSS" After="corev4.css" runat="server"/>

Same implies to JavaScript Files <link href="ExtendedItemStyle" lang ="javascript"

name="ExtendedItemStyleJS.js" /> <SharePoint:ScriptLink Language="javascript"

Name="ExtendedItemStyleJS.js" Defer="true" runat="server"/>

Webparts in SharePoint Web Parts are the building blocks of SharePoint pages. They can be as simple as an image Web Part,or as complex

as any custom application. Within SharePoint, among the most common examples

are list-view Web Parts. These are exactly what they sound like — views of SharePoint lists. As soon as a list is created, a list-view Web Part is available to place on a page and configure to meet the user's needs.

When business requirements call for functionality that isn't available with other Web Parts, this functionality can be developed.

Note: Webparts are always placed under Webpart zoneWebpart zone are nothing but widgets which gives provision to add webparts under it.

Quick SummaryBuilding Blocks Definition SharePoint Farm and Web Applications

While not a technically perfect definition, you can think of a SharePoint farm as your whole SharePoint environment and each web application as a URL like http://my.intranet.com or http://sharepoint.intranet.com.

Collection A site collection consists of a top-level site and its sub-sites. It is a logical unit for administration—there are settings that can only be configured at the site collection level (in other words, at the top-level site). Each web application can host many site collections.

Site A site consists of a data repository, visual elements, administration, and almost every other core element of the functionality and experience for the user.

Site Template A template defines what the site will look like, what lists comprise the site initially, how publishing will work on the site, and a number of other settings.

Lists Lists are data repository that can hold columns of data and/or documents. The objects stored in a list are called items. Visually, a list is represented by views or a web part. It is analogous to a database table or Excel worksheet.

Libraries A SharePoint library is a specialized form of SharePoint list that is used to store files and content types rather than items. Libraries are created in much the same way as normal lists and support the same type of functionality such as workflows, alerts, etc.

Items Items are the fundamental data objects that are stored within a list. An example of an item

Thank YouFor queries mail me at:sachchinannam@gmail.com |

sachin.annam@outlook.com

Any Questions ??