Autor: Sebastian Gerling

Habe gerade einen wirklich guten Artikel zum Thema „Warum sollte man sich überhaupt mit SharePoint beschäftigen…?“ von Stephanie Krieger auf MSDN unter: http://msdn.microsoft.com/en-us/library/dd637113.aspx gefunden. Die Kernaussage folgt:

Creating a SharePoint Site, Workspace, or Template
Do you need to quickly get started on a team project? No code is required to create a SharePoint site or workspace directly from the Site Actions available on your site. Or, use SharePoint Designer 2007 for flexible tools that help you create and customize your site or workspace. You can also save your customized site as a template that others can use when creating new sites.

Creating Libraries, Lists, and Collaborative Tools
If you need to add content or a new interface through which to share content with team members, you can create lists or libraries for your site as easily as you create a site or workspace. For example, create a document library or an interactive wiki library to add content for the team to share and edit; create a task list or a custom list to track the progress of project elements.

Using Web Parts or Creating Your Own
Do you need to display information on your SharePoint site that isn’t an automatic part of a site or Web page that you created? For example, perhaps you want to display the team calendar or task list on a Wiki site home page? Web Parts are components that a user can easily add to a page on a SharePoint site to display or interact with a wide range of content types.

Branding Your Intranet
You can add basic branding elements to your site, such as your logo, directly from Site Settings. Or, use the design tools in SharePoint Designer 2007 to customize everything from fonts and colors to layout and style of your site for a fully-branded, custom Intranet.

Using Web Services to Populate Document Content
You can create Web service connections to populate document content dynamically with content on a SharePoint site. Or, you can use Web services to populate documents when generating documents on the server with a custom application. 

Creating Custom Workflows
A workflow is a series of actions to apply to specified content. For example, you might have a workflow that creates a task, sends an e-mail, and updates a list when a specified user creates or edits a document. You can create workflows to be initiated either manually by users or automatically based on conditions. A single workflow can have one or many steps and each step can contain multiple conditions and multiple actions.

Creating and Using Custom Content Types
A SharePoint content type is a reusable group of settings that users can apply to different types of content added to a SharePoint site or library, such as documents. Content types make it easier to manage document metadata and behavior, enhancing capabilities such as content creation, enterprise search, and collaboration.

Creating Dynamic Business Intelligence Solutions
The enterprise edition of Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 for Internet Sites include powerful business intelligence capabilities for creating rich business intelligence tools. Build interactive dashboards and portals using tools such as Excel Services, data connection libraries, and business data Web Parts.

Creating Incredible Custom Collaboration Tools Using Windows SharePoint Services 3.0 and Silverlight
Microsoft Silverlight is a rich, Web-based technology, available as a plug-in that developers can use to create amazing media experiences and interactive applications for the Web. When you use Silverlight to develop tools for Windows SharePoint Services 3.0, you can provide users with powerful, compelling, beautiful components and applications that greatly enhance their work experience.

And the Number One Reason to Learn More about SharePoint Products and Technologies…
When you put all of the preceding tools together, you can build dynamic, customized, enterprise collaboration solutions where people can work together in an integrated, efficient, and friendly environment for managing content, data, business processes, and social networking.

Wictor Wilén hat einen sehr schönen Artikel, zu den in seinen Augen wichtigsten Files im 12 Hive Directory, geschrieben, den ich jetzt hier mal wiedergeben möchte. Besonders im letzten Punkt stimme ich mit Ihm überein, da es die Akzeptanz des Users enorm steigert, wenn er die ihm vertrauten Icons im SharePoint wiedefindet. Den Artikel findet man hier.

ctypeswss.xml (in TEMPLATE\FEATURES\ctypes)

This is the feature elements file for all the default WSS Content Types. When creating new content types, most often I find it useful to derive them from existing content types. For example if I need to create a content type that derives from the standard content type Task, i can easily get the content type ID, which is used when creating new content type IDs, and what Site Columns that content type has.

fieldwss.xml (in TEMPLATE\FEATURES\fields)

Second favorite is the elements file for the WSS Site Columns feature. In this file all definitions for the default WSS Site Columns is found. Together with ctypeswss.xml this is really handy when creating custom content types. By finding out the ID’s of the Site Columns you can easily re-use the site columns when creating content types.

Custom List schema.xml in (TEMPLATE\FEATURES\CustomList\CustList)

Whenever I need to create a list definition and need to create a schema.xml I use the schema.xml for the Custom List feature and copy it to my definition.

STS onet.xml in (TEMPLATE\SiteTemplates\STS\Xml)

This is the file to check out when creating Site Definitions. The onet.xml file contains all Site Definitions (althought the folder is called SiteTemplates), which includes navigation, lists etc. Most often I copy this file (and all other files in the STS folder) and remove almost everything except the the blank site def.

DOCICON.xml (in TEMPLATE\XML)

Perhaps not that interesting that the four above, but on nearly all installations you update this file with the PDF icon (at least). What this file does it that it allows you to map an extension (or ProgID) to an icon and optionally specify an editor.