|
|
Windows SharePoint Services Links and Resources  |
Microsoft's main page for Windows SharePoint Services 3.0. Start here if you are new to SharePoint or want to see whats new about WSS V3. SharePoint 2007 Training
Free on demand courses that get you up to speed with SharePoint 2007 document libraries.
This Evaluation Guide is designed to give you a solid understanding of the design goals and feature set for Microsoft Windows SharePoint Services 3.0.
Skills you need to develop for working with code in Windows SharePoint Services 3.0. Also includes information about the differences from traditional ASP.NET development, the required development environment, and the steps to build a Windows SharePoint Services solution with Visual Studio 2005 Extensions for Windows SharePoint Services 3.0.
Take a look at how Microsoft Office Access 2007 integrates with Microsoft Windows SharePoint Services. View this on demand session to learn how Access 2007, the popular data management application, and Windows SharePoint Services enable you to centralize and simplify data management, and share data across your organization.
Windows SharePoint Services 3.0: Software Development Kit (SDK) download. The Microsoft Windows SharePoint Services 3.0 SDK describes the technologies that Windows SharePoint Services 3.0 provides for developers. It contains overview information and step-by-step, how-to procedures for programming with Windows SharePoint Services that can help you get started writing applications. There are several code examples within the documentation, as well as some tips and best practices, for using the development platform of Windows SharePoint Services 3.0.
The purpose of this Microsoft white paper is to describe how Microsoft developed the application templates, identifying best practices for how to work with core capabilities within both Windows SharePoint Services and SharePoint Designer, with the goal of empowering customers and partners to create their own applications.
Arpan Shah's PowerPoint presentation providing a WSS 3.0 overview.
In this webcast, the ability to use, update, and create custom workflows that you can employ in your Windows SharePoint Services site are discussed. Built-in workflow capabilities in Windows SharePoint Services are covered, along with demonstrations of available customizations. In addition, descriptions of how to use Microsoft Office SharePoint Designer 2007 to open, view, and modify included workflows are included. Demonstration concludes with coverage of the capabilities of Workflow Designer in SharePoint Designer 2007.
The resources on this site provide information for getting the most out Application Templates for Windows SharePoint Services 3.0.
You can use top-level Web sites and subsites to divide site content into distinct, separately manageable sites to help you organize content. Follow the link above to find out more.
A list is a collection of information that you share with team members. For example, you can create a sign-up sheet for an event, or track team events on a calendar. Take a look to learn more.
A library is a location on a site where you can create, collect, update, and manage files with team members. Each library displays a list of files and key information about the files, which helps people to use the files to work together.
Content types (content type: A reusable group of settings for a category of content. Use content types to manage the metadata, templates, and behaviors of items and documents consistently. Content types are defined at the site level and used on lists and libraries.) enable organizations to organize, manage, and handle content in a consistent way across a site collection. By defining content types for specific kinds of documents or information products, an organization can ensure that each of these groups of content is managed in a consistent way.
Microsoft Windows SharePoint Services 3.0 provides security features that you as a site owner can use to help control access to and authorization on your sites. By using these security features, site owners — instead of server administrators — control who can access the site, and site owners specify what permissions are assigned to users for particular entities.
As a site owner, when you create the permission structure for your site or grouping of sites, you should balance ease of administration with the need to control specific permissions for individual securable objects. With any Web site, it is also important to follow the principle of least privilege when authorizing access to the site.
A fundamental responsibility concerning site security is to manage who can access resources on your site. Microsoft Windows SharePoint Services 3.0 enables you, as a site owner, to control what users or groups of users can access your SharePoint sites. This effectively transfers the task of managing users from the server administrator to site owners.
Additional WSS 3.0 resources showing methods to control which users, or groups of users, have access to your SharePoint sites.
Although sites that are built on Windows SharePoint Services often have additional default SharePoint groups, Microsoft Windows SharePoint Services 3.0 includes five permission levels (permission level: A set of permissions that can be granted to users or SharePoint groups on an entity such as a site, library, list, folder, item, or document.) by default. Each of these permission levels has specific permissions (permission: Authorization to perform specific actions such as viewing pages, opening items, and creating subsites.) associated with it. As a site owner, you can choose which permissions are associated with these permission levels.
Any users with the Manage Permissions permission on a particular securable object, such as a list, library, folder within a list or library, document, or list item can manage permissions on that particular securable object.
When you enable anonymous access to a Web site, you allow anonymous users (and authenticated users who have not been granted access to the site) to browse the entire Web site, including any list, library, folder within a list or library, list item, or document that inherits its permissions from the Web site.
A blog is a Web site that enables you or your organization to quickly share ideas and information. Blogs contain posts that are dated and listed in reverse chronological order. People can comment on your posts, as well as provide links to interesting sites, photos, and related blogs.
A library is a location on a site where you can create, collect, update, and manage files with team members. Each library displays a list of files and key information about the files, which helps people to use the files to work together. When you create a Microsoft Windows SharePoint Services site, several types of lists are created for you. These default lists range from a discussion board to a calendar list. You can customize the default lists in many ways, or you can create custom lists with the columns that you choose. A Meeting Workspace is a Web site for gathering all the information and materials for one or more meetings. If your meeting materials — such as agendas, related documents, objectives, and tasks — are often scattered, a Meeting Workspace site can help you keep them all in one place. A Document Workspace site helps you to coordinate the development of one or more related documents with other people. The site provides tools to share and update files and to keep people informed about the status of those files.
Determining the goals and objectives of a Web site are important factors to consider when developing a Web site. Careful planning will help to ensure that the Web site will be easier to use and easier to manage.
This topic describes keyboard shortcuts for common tasks on a Microsoft Office SharePoint Server 2007 or Microsoft Office Forms Server 2007 site.
You can use Information Rights Management (IRM) with Microsoft Office SharePoint Server 2007 sites to help control and protect files that are downloaded from lists or libraries. The Three-state workflow is designed to track the status of a list item through three states (phases). It can be used to manage business processes that require organizations to track a high volume of issues or items, such as customer support issues, sales leads, or project tasks. |
|
|
|