Specialized Web Parts from SharePoint 2010 Gallery - dummies

Specialized Web Parts from SharePoint 2010 Gallery

SharePoint 2010 provides many specialized Web Parts that are meant to be used in a certain context or to return a certain set of content. Some of these include

  • Lists and Libraries: These Web Parts displays items from the lists and libraries on your team site. You can use list views to filter, sort, and group the information presented in the Web Part.

  • My Information: If your company uses Exchange Server 2003 or higher for e-mail, you can use these Web Parts to display your inbox, calendar, and other folders on a web page in SharePoint.

    Your company needs to provide you with a web address for Exchange that’s configured to use Windows Integrated Authentication.

  • Office Client: SharePoint 2010 has a lot of integration points with Office clients, and these Web Parts are a testament to that. Here you find Web Parts that let you interact with Excel spreadsheets, Visio models, and Access databases.

    The cool factor isn’t so much that you can interact with your Office files; it’s that SharePoint publishes the output to your web page so that other people can interact with your Office files.

    The Office Client Web Parts are present only if you’re licensed to use the Enterprise Edition of SharePoint. Many large companies take a two-tiered approach to SharePoint where only certain users get Enterprise licenses. If you need these Web Parts, ask for a license upgrade. Individual users can be upgraded without upgrading the licensing for the entire company.

  • People: These Web Parts are kinda boring, but one really cool one is here — the Note Board. Dropping this Web Part on your page adds a Social Commenting box. So folks can add comments right inside your web page. Social commenting is part of SharePoint’s new social networking features.

Any configuration or content that you put inside a Web Part isn’t version-controlled. In other words, each time you change the Web Part, you write over any previous configuration or content. That’s another reason against using the Content Editor Web Parts.

Store your content in lists and libraries where the content is subject to version control and retention policies rather than placing it directly in the web page. You can export your Web Part’s configuration using the Export on the Web Part’s menu.

Content that you place inside a Rich Content control on a wiki page is version-controlled if versioning is enabled in your library.