There are three main types of content pages in SharePoint Server 2010:
Web part pages
Publishing pages are available only in publishing sites. In publishing sites, authors and approvers use the publishing feature to create content and then make it available for site visitors. Usually, a publishing site has an approval workflow enabled, so content is reviewed and approved prior to being published.
Publishing pages are created by using page templates called page layouts. The page layouts provide a consistent structure to all publishing pages in a site collection. Page layouts can be customized to contain fields contributors can use to enter their content, such as text, graphics, rich media, and more.
Publishing pages are the most structured of SharePoint content pages, both in terms of their layout and the process for using them. An organization or department uses a publishing site to ensure that authors follow a business process to release content in a consistent manner. Press releases are a good example of a type of content that’s ideal for a publishing site.
Web Part pages
Web Part pages contain Web Parts that display list data, information, graphics, or rich media in a dynamic Web page. The layout and content of a Web Part page can be set for all users and optionally personalized for individual users. A site owner or a site member with the appropriate permissions can create and customize Web Part pages to add, configure, or remove Web Parts. In a SharePoint 2010 blog, a page for a blog post is a Web Part page.
Sites that support Web Part pages
All SharePoint Server 2010 sites support the use of Web Part pages. In some site templates, such as Social Meeting Workspace, Web Part pages are the only available page type. The SharePoint blog site displays posts by using a Web Part page.
Note: Web Parts are not restricted to use on only Web Part pages. They can also be added to wiki pages and publishing pages.
A Web Part Page is always in one of two views: shared view or personal view. When a Web Part page is in shared view, all users see the same page and any changes you make in shared view are intended for all users to see. When a Web Part page is in personal view, you see any personal changes you have made and any changes you make in this view are intended just for you to see.
Understanding these two page views is important because:
- The contents of the Web Part Page and the values of the Web Part properties are often different in each view.
- The scope and effect of changes you make varies significantly in each view. These changes include adding, modifying, and removing Web Parts, changing the Web Part Page layout, and making connections between Web Parts.
Wiki pages are often edited by multiple people. You might have heard that “wiki” is the Hawaiian word for quick. Speed and flexibility are undeniably the foundation of wiki design. Wiki pages are informal, open for editing by almost anyone in the organization, and, by that token, are often considered works in progress.
Sites that support wiki pages
In SharePoint 2010, wiki pages are everywhere, by default. On many new sites you create, the home page is now a wiki page. On team sites, all new pages that you create are wiki pages by default. Other site templates support the creation of one or more wiki libraries. Enterprise Wiki sites support the creation and use of page layouts with wiki pages. Several default wiki layouts come with the Enterprise Wiki: A basic page, a basic project page, or a redirect page.