Before you read the other chapters or sections of this book, you need to understand what SharePoint is. In this chapter we’ll briefly touch on the major components of building SharePoint sites. Once you’ve completed this chapter, you should have a broad overview of what SharePoint is and what out-of-the-box components it offers you for building sites.
Let’s go ahead and begin looking at what the SharePoint 2010 capabilities are, along with a summary of the functionality associated with the different releases. After that I’ll explain/review the terms that you’ll continue to see throughout this book.
For us to be on the same page and to move forward in the book, I need to define some key terminology. Some people refer to the technology as SharePoint, SharePoint Server, MOSS, SharePoint Foundation, and Office Portal Server. So let’s start up front and get the terms straight. To begin, look at table 2.1 to see the product terminology defined. In section 2.1.5 of this chapter I’ll provide additional tables that define terminology regarding SharePoint sites, the components within a site, and permissions. Let’s get started with the product terms that have been used over the years.
Term |
Meaning |
---|---|
WSS 2.0 | Windows SharePoint Services for 2003. |
SharePoint Portal Server 2003 | Extension of WSS 2.0 with portal functionality for 2003. |
WSS 3.0 | Windows SharePoint Services for 2007. |
MOSS/Microsoft Office SharePoint Server | MOSS is an extension of WSS 3.0 for SharePoint 2007 technologies. The term portal was dropped because it provides greater capabilities than what many users expect from a portal. |
SharePoint Foundation | Windows SharePoint Services for 2010. SharePoint Foundation 2010 is the core functionality of Share-Point 2010 technologies. |
SharePoint Server | SharePoint Server 2010 is an extension of SharePoint Foundation for SharePoint 2010 technologies. The term Office was dropped because it isn’t part of the Office client. |
SharePoint | Umbrella term used for all of the above technologies. If a user says SharePoint, it’s important to clarify what they mean. You can start by asking if they’re using 2003, 2007, or 2010 and then further clarify if it’s just SharePoint Foundation/WSS or one of the server solutions: SharePoint Server 2003, MOSS, or SharePoint Server 2010. |
SharePoint 2010 comprises three main editions: SharePoint Foundation, SharePoint Server Standard, and SharePoint Server Enterprise. From a licensing perspective there are variants of these if you’re buying for an intranet or internet deployment on premises or if you’re considering a deployment using Microsoft’s cloud offerings. We won’t focus on this from a licensing perspective but instead from a basic explanation of the core functionality associated with each edition regardless of the license type you’re purchasing. The basics of the relationship among the three editions are shown in figure 2.1.
As you can see, some editions include the functionality of another edition. For example, SharePoint Foundation is included in SharePoint Server Standard, and SharePoint Server Standard is included in Share-Point Enterprise. SharePoint Server extends the functionality of Share-Point Foundation. Therefore, if you’re running either version of SharePoint Server, you have SharePoint Foundation. But if you’re running SharePoint Foundation, you may not have SharePoint Server. This might sound confusing at first, but by the end of the chapter it should make perfect sense to you.
Let’s look at some examples of SharePoint and go over the six core capabilities that make up SharePoint. Each edition contains aspects of these six core capabilities, with functionality increasing as you go from SharePoint Foundation to SharePoint Server Standard to SharePoint Server Enterprise.
SharePoint is broken into six major categories of functionality that I’ll refer to as capabilities. These capabilities are broken out in table 2.2. The following letters indicate the amount of functionality associated with each capability available with that corresponding edition:
Sites |
Communities |
Content |
Insights |
Composites |
Search |
|
---|---|---|---|---|---|---|
F | F | F | F | F | F | |
F | F | F | IP | IP | IP | |
P | P | P | P | P | P |
Now let’s look at each of the six capabilities in more detail:
Now that you understand the capabilities, we’re going to look at the functionality of these core capabilities in relation to SharePoint Foundation and SharePoint Server.
SharePoint Foundation is free and runs on Windows Server. Specific examples of functionality that you’ll find in this version in relation to their capability are as follows:
Sites
Communities
Content
Insights—Business Connectivity Services (BCS) to connect to external data
Composites
Search
Now that you understand the functionality that’s in SharePoint Foundation, we can build on these functionalities and show what you’ll get in addition to the SharePoint Foundation functionality if you have SharePoint Server.
Microsoft SharePoint Server 2010 is an extension of SharePoint Foundation, which includes the previously discussed features and offers a more comprehensive solution for collaboration. SharePoint supports most intranet, extranet, and web application requirements, enabling your data to be maintained within one integrated platform, making it a truly robust solution for your enterprise information system.
There are two main editions of SharePoint Server available, Standard and Enterprise, with the Enterprise release having the most comprehensive functionality across the six capabilities. Following is a breakdown of the major pieces of functionality offered in SharePoint Server Standard, followed by the components associated with Enterprise.
Standard SharePoint offers all of the SharePoint Foundation functionality and the following additional functionality:
Communities, My Sites
Tags are available to help classify information. Features associated with tags are as follows:
Content
Insights—Business Connectivity Services (BCS) to connect to external data
Composites
Search
Enterprise SharePoint includes all of the above SharePoint Server and SharePoint Foundation functionality and the following additional functionality:
Insights
Composites
Search
You should now understand the different pieces of functionality that compose SharePoint Foundation and SharePoint Server Standard and Enterprise. In the next section, I’m going to break down some of the key terms to make sure we’re all on the same page.
Now we’re ready to move on to some more advanced topics and to discuss components that make up the site architecture of SharePoint. To start I’m going to go over some core terminology with you. I’ve broken the terms into three different tables. Table 2.3 covers the logical breakdown of sites. I then show the components that define a site in table 2.4. The last table, table 2.5, covers the core SharePoint groups for each site and what their permissions are.
Meaning |
|
---|---|
Web application | Web applications contain site collections. |
Site collection | A site collection can’t contain another site collection, but it can have many subsites. A site collection is where you would access core elements across the subsites, such as security, navigation, content types, and galleries for master pages, site templates, list templates, and the like. |
Portal | Generic term that’s often linked to a single site collection. |
Subsite | A site or collection of sites that link to a site collection. |
Site | Site is a generic term that can mean subsite, top-level site, or site collection. |
Workspace | There are six types of workspaces: Document, Basic Meeting, Blank Meeting, Decision Meeting, Social Meeting, and Multi-page Meeting. Workspaces are generally considered ad hoc or temporary. A workspace is a place to quickly work on a document or organize meeting information, but any final deliverables will typically be stored on another site for long-term access. |
Term |
Meaning |
---|---|
Web part | A web part is like a mini application or view of a list or other data source. |
List | Lists are broken into libraries, communication, tracking, and custom. They provide users with different views and functionality for managing information. |
View | A view allows users to access items in a list using different columns, filters, and styles. |
Term |
Meaning |
---|---|
Site collection administrator | A site collection is created by server administrators. A site collection administrator manages core elements across the subsites such as security, navigation, content types, and galleries for master pages, site templates, list templates, and so on. |
Site owners | Subsites can be assigned site owners. The site owner has full control of the site and can manage the permissions, design, lists, and the like. |
Site members | Subsites can be assigned site members. The site members can contribute content to the site. |
Site visitors | Subsites can be assigned site visitors. The site visitors can read content on the site. |
Table 2.3 covers the logical components for sites. It defines what’s needed for the creation of a site and the relationship between those components.
Figure 2.2 will help to explain and show the relationship of the logical components to one another.
Based on the diagram, you can see that a SharePoint deployment can consist of many site collections, which are top-level sites that can host many subsites. The top-level site of the site collection is only one site, but each subsite within the site collection can continue to build out and have additional subsites. Subsites that are within the same site collection can share certain core elements, such as security for people management, navigation, and content types, as well as style components, such as master pages and page layouts.
Learning the main components that cover the logical breakdown of sites and site collections is a good start, but you also need to understand some of the core site components for building your sites. Table 2.4 covers some of the core site tools that are critical to understand in order to effectively build out SharePoint sites.
Table 2.5 covers some of the core groups and permissions that are created by default for your top-level site and subsites. I’ll go into much more detail about permissions later in this book, but as a start, these terms will help you understand how to administer security for your sites.
Permissions can involve much more detail than just site owners, members, and visitors. These are the default groups. But you have the ability to create different groups and permission levels, getting as detailed as deciding who can add, edit, delete, or view versions. This will be covered in detail in chapter 11.
That’s it! Now that you know the core terminology, I’ll quickly summarize what you’ve learned. In the next chapter you’ll get the opportunity to see and understand some of the out-of-the-box functionality of SharePoint.
You now have the foundation of SharePoint sites and what you can get out of the box. You should have a good understanding of the following:
Now we can get into the muscle of SharePoint and discuss what you can do as a power user to customize and create your own site templates. In this chapter you created a site and learned many of the core components that make up the site-creation process. In part 2 of this book you’ll continue learning the fundamentals of SharePoint through a scenario-based approach. This will help you envision the different possibilities and get you on your way to creating customized sites for your own use. The next chapter will go over the out-of-the-box site templates. This is important to understand so you know what’s already available before you create a customized site.
18.119.105.239