Chapter 7. Adding, Editing, Connecting, and Managing Web Parts on the Page

A Brief Introduction to Web Parts

Adding Web Parts to a SharePoint Site

Editing and Maintaining Web Parts on a SharePoint Site

Connecting Web Parts in a SharePoint Site

Web Parts on a Web Part Page

Summary

Web portals gained immense popularity in the late 1990s, giving companies an easy way to relate information to both internal and external users. Up until that point in time, content had been largely static and was maintained by a one or more webmasters on a series of HTML webpages. Any content that was generated had to be converted to a webpage by someone with technical skills in HTML, JavaScript, and so on.

One of the key concepts introduced by web portals was the notion of interactivity. Content pages could be assigned to a designated author who could modify content directly. In addition, content could be added, deleted, or moved on a web page by an end user.

In this new model, the webmaster was still responsible for the core site structure as well as the initial layout of content on the page. Zones could be designated by the webmaster to contain customizable areas of content, and then modular components could be added by content authors to display content.

Finally, these modular components could be customized by users on a per-user basis. A good example of this would be a module that displayed a weather report. If the user wanted to customize a weather report for their city, region, or ZIP code, these changes would not affect other users visiting the site.

Over time, these modular components have had different names and varied slightly in format. Whether you call them Web Widgets, Portlets, Gadgets, or Web Parts (in the case of Microsoft SharePoint), they all have the same core function—to represent customizable content on a webpage.

A Brief Introduction to Web Parts

Web Parts are a key component of any SharePoint installation. They are present in all versions, from SharePoint Foundation to SharePoint Server (Standard or Enterprise). They can be purchased from third-party providers or created by developers (perhaps within your own company) to accomplish a specific task.

A variety of Web Parts exist, but there really are only two things a Web Part is intended to do:

  • Receive Input

  • Display Content

Sometimes a Web Part accomplishes both of these tasks. Consider the weather component. If we reimagined this as a custom Web Part, it could both receive input (the city or ZIP code) and display content (the weather report for the appropriate area).

Web Parts can also be connected to each another. One Web Part might receive input and then provide this input to filter the content displayed by a second Web Part. You will see more of this behavior in the section Connecting the Web Parts, later in this chapter.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset