SharePoint
au
Quotidien
avec
EROL
|
|
|
|
Customizing a Web Site Based on Windows SharePoint Services
· Manage Lists· Add and Customize Pages· Apply Themes and Borders· Apply Style SheetsOther users of your site cannot gain access to the pages required to perform these tasks unless you specifically assign them to a site group that contains these permissions. For more information about controlling permissions and assigning rights and site groups, see Managing Site Groups and Permissions. 1) Customizing Web Sites in the Browser Basic customization can be done from within the browser, using links from the Home, Create, and Site Settings pages of the Web site. From the browser you can perform basic customizations such as the following: · Add a list.· Change the layout of the home page.· Change the picture on the home page.· Add a Web Part to a Web Part Page.· Change a site's display name (not the URL).· Apply a theme.The Windows SharePoint Services Beta 2 Help files contain more information about customizing Web sites from within the browser. 2) Customizing Web Sites by Using Web Page Editing Tools Additional customization can be done by using a Windows SharePoint Services–compatible Web page editor, such as Microsoft FrontPage 11 (Beta). With a Web page editor you can perform customizations such as the following: · Add borders to pages.· Insert graphics.· Add components to the home page.· Change the navigation of a site.For example, if you have created a custom theme for Windows SharePoint Services Beta 2 sites in FrontPage 11 (Beta), and added the theme name to the list of themes in FrontPage 11 (Beta), you can edit the list of available themes in Windows SharePoint Services Beta 2 to include your new theme. An XML template called spthemes.xml contains the theme name, style sheet location, thumbnail, preview, and description of each theme that is available through the browser. This XML file is used to render the theme selection page. You can modify this XML file (by opening it in any editor, such as Notepad) to include a custom theme on the Apply Theme to Web page. You must be a member of the local administrators group for the server to edit this file. For more information about creating a theme and adding it to the list of themes in FrontPage 11 (Beta), see the FrontPage 11 (Beta) Help system. Add a custom theme to the list of available themes 1. On the top link bar, click Site Settings. 2. In the Manage This Web section, click Apply theme to site. 3. In the Address bar on the browser, replace the file name themeweb.aspx with spthemes.xml. 4. For example, if the Address bar showed http://server_name/_layouts/1033/themeweb.aspx, you would change the path to http://server_name/_layouts/1033/spthemes.xml. 5. Edit the XML file and add a new section for your custom theme, similar to the following: - <Templates> <TemplateID>newtemplateid</TemplateID> <DisplayName>NewTemplateDisplayName</DisplayName> <Description>Description</Description> <Thumbnail>../images/image.png</Thumbnail> <Preview>../images/image.gif</Preview> </Templates> For more information about customizing Web site elements in a Windows SharePoint Services–compatible Web page editor, see the Help system for the Web page editor. 3) Customizing Web Sites by Using Administrative Controls If you are an Administrator, you can customize how Web sites work by performing tasks such as the following: · Change settings, such as regional settings.· Add, remove, or modify site groups.· Add or remove users, or change their site group membership.You control these features by using the Site Administration pages. Only an administrator of the site can perform these types of customizations, or users who are members of a site group that contains administrative rights, such as the Manage Site Groups right. 4) Customizing Web Sites Programmatically You can perform advanced Web development customizations by using the programming model behind Windows SharePoint Services Beta 2. You can use the programming model to make Web site customizations such as: · Add, edit, delete, and retrieve data from SharePoint Lists.· Create new lists and set list metadata (such as the fields in a list).· Work with documents in document libraries.· Perform administrative tasks such as creating webs, adding users, creating roles, and so on.For more information about advanced customizations, see the Windows SharePoint Services Software Development Kit. 5)Customizing SharePoint Portal Server This is a preliminary document. Additional information about this feature will be provided prior to final commercial release. Enterprise Application Integration Web Parts This section will include how to force a user to have a certain Web Part on a page. Portal Template Pages Related Topics Link to Customizing SharePoint Team Services Sites
6) Customizing Help Web sites based on Microsoft Windows SharePoint Services Beta 2 are fully customizable — you can add any type of Web page to the site, and all kinds of interactive content to the pages. To complement this flexibility in the site, the Help system for Windows SharePoint Services Beta 2 was designed to be customizable. So, when you customize the pages available on a Web site, you can also customize the Help available for those pages by adding topics that contain information specific to your organization. For example, you might want to customize Help when: · You change the behavior of a default Web site page and want to explain how users can interact with the modified page.· You add a new page to the site with a form that users must fill out and you want to provide assistance for particular fields in the form.· You want to explain your organization's Web site policies, processes, or structure to new users of the site.You must have administrator rights to the server computer to add topics to the Windows SharePoint Services Beta 2 Help system. 7) Performing Basic Customization of Help Basic customization of Help consists of adding new Help topics. You can use any level 4 HTML-compatible Web page editor, such as Microsoft FrontPage 11 (Beta), to create topics. When you add a topic, be sure to edit the table of contents topic to include the new file, and also create a hyperlink in the index topic to link to important terms in the new topic. Help for Windows SharePoint Services Beta 2 is stored as HTML and image files in the file system of the server computer. These files are stored per server, so when you add a Help topic, it is available for all users of that server. The following table lists and describes the contents of the folders used to store Help content on a server.
About the Windows SharePoint Services Beta 2 Help Folder and Security Because the Windows SharePoint Services Beta 2 Help topics take advantage of JScript coding to control some Help features, the \_vti_bin\help\lcid\sts\ folder that contains the Windows SharePoint Services Beta 2 Help files grants Read and Read and Execute permissions to the Everyone group. Be sure to tightly control access to this folder, and any of the other Windows SharePoint Services Beta 2 installation folders. Because of the Read and Execute permission, a user with Write permissions to this folder could potentially add malicious scripting to files in the folder, which would then be allowed to run. Customizing Special Help Files The Help system for Windows SharePoint Services Beta 2 consists of Help topic files plus special files such as the table of contents, index, glossary, and other files. When you add custom content to the Help system, consider updating these special files as well to contain references to your new content. Finding Specific Help Files You can easily find topics in the Help system by browsing through the table of contents. After you identify the topic you want, you can turn on the Address bar for the Help window (in Microsoft Internet Explorer, on the View menu, click Toolbars, and then click Address Bar), and then make a note of the file name. Alternatively, you can use Microsoft Windows search feature to search through the _vti_bin\lcid\sts\html folder to find a particular sentence or phrase in Help. Performing Advanced Customization of Help You can also perform more advanced customization of the Help system. For example, each default page has one or more unique Help topics associated with it. These associations are maintained in an XML file called sts.xml. By editing this file, you can make your custom Help topics appear in the list of context-sensitive topics for a particular page in your Web site. For more information about advanced customization of Help, see the Windows SharePoint Services Software Development Kit. Preserving Customized Help When Installing Service Releases Windows SharePoint Services Beta 2 service releases often contain updated Help files. If you customize a default Help topic, and then apply a service release, your customized version of the Help file can be overwritten. Because service releases update default Help topics, it is not recommended that you customize the default Help topics, aside from the table of contents and index files. New topics that you add to the Help system are not overwritten by service releases, unless you use the same file names as existing or new topics. If you are customizing the Help system extensively, be sure to back up your customized topics before applying a service release, so that you can restore your customizations after the service release has been installed.
8) Using the SDK to Perform Advanced Customization This is a preliminary document. Additional information about this feature will be provided prior to final commercial release.
9) Deploying Additional Web Parts Microsoft Windows SharePoint Services Beta 2 comes with several Web Parts that your users can use right away, and many more are available in the online Web Part gallery. In addition, you can create your own Web Parts or install Web Part Packages that include Web Parts from Microsoft or other software vendors. Creating Custom Web Parts You can create custom Web Parts by using the Web Part Framework, and add them to the Web Part gallery for a site collection. If you want to deploy your custom Web Parts to multiple servers, or share them with other organizations, you can create a Web Part Package. For more information about creating a Web Part or a Web Part Package, see the Windows SharePoint Services Software Development Kit. Installing a Web Part Package A custom Web Part Package can be distributed as a cabinet (CAB) file. If you have a Web Part Package in CAB format, you can use the command line to install it to your server. Again, if you are in a server farm environment, you must use the command line to install the Web Part Package to each front-end Web server in the server farm individually. Web Part Packages from Microsoft (such as add-in packs for Windows SharePoint Services Beta 2) can be packaged into a Microsoft Windows Installer (MSI) file. You simply install the MSI file to your Web server, and the Web Parts are added to the server gallery. If you have multiple servers in a server farm, you must install the Web Part Package to each server in the server farm to make it available across your farm. When you install a Web Part Package, it is added to the virtual server gallery, and can be used for any site on that virtual server. Adding Web Parts from a CAB File to the Server Gallery You use the command-line tool Stsadm.exe to add the Web Parts in a Web Part Package (in CAB file format) to the list of Web Parts available for a server. The following operations are available for Web Part Packages in Stsadm.exe: · addwppack — Adds a Web Part Package to your server Web Part gallery.· deletewppack — Removes a Web Part Package from your server Web Part gallery.· enumwppack — Lists the Web Part Packages currently in your server Web Part gallery.These operations take the optional -url, -filename, -name, -farm, and -force parameters. For example, to list the Web Part Packages that are currently available for your server, you would use the following syntax: stsadm.exe -o enumwppack To add a new Web Part Package to your server, you would use the following syntax: stsadm.exe -o addwppack -filename <path to file> You can use the -force parameter to overwrite an existing Web Part Package with a new version, or to repair a Web Part Package by reinstalling it. For more information about using these commands, see Command-Line Operations.
10) Extending Windows SharePoint Services Microsoft Windows SharePoint Services Beta 2 is a technology that was designed to be extended and used with other products. Several products from Microsoft and other software vendors use Windows SharePoint Services Beta 2 as an extensible platform. These products build additional features that work with Windows SharePoint Services Beta 2 or customize existing features to meet the users' needs. This extension and customization can be as simple as editing an XML template file or providing special Web Parts that can be used on Web Part Pages, or as complex as creating entire products that build on the Windows SharePoint Services Beta 2 functionality. Other products may also provide administrative or user tools that interact with Windows SharePoint Services Beta 2. If you have installed Windows SharePoint Services Beta 2 as part of another product, be sure to read the administrative documentation for that product to find out what additional features you have that are not covered in the Windows SharePoint Services Beta 2 Administrator's Guide. If you are interested in building features for Windows SharePoint Services Beta 2 to work with your product, you can find information about building Web Parts, connecting to Windows SharePoint Services Beta 2, and customizing Windows SharePoint Services Beta 2 features and templates files in the Windows SharePoint Services Software Development Kit. Related Links For more information about creating or customizing templates, see Working with Templates. For more information about distributing Web Parts, see Deploying Additional Web Parts. 19/06/2003 |
|
|
Web sites based on Microsoft Windows SharePoint
Services Beta 2 are designed to be flexible. You can tailor a site to fit your
users' needs by adding or removing pages, changing the appearance of pages,
changing the site navigation, and making other customizations. To customize Web
sites based on Windows SharePoint Services Beta 2, you must have the following
rights, all of which are included in the Web Designer and Administrator
site groups by default: