Address: http://robgarrett.com/cs/blogs/software/archive/2006/07/03/2065.aspx
This short article shows the application of the master page and content page in ASP. net2.0 in Windows SharePoint Services V3.0. WSS 3.0 is implemented based on ASP. NET 2.0. Therefore, the dashboard page/content page in WSS 3.0 is also customized based on the corresponding functions in ASP. NET 2.0. There are many articles on ASP. net2.0 master pages on the Internet. The link source and msdn are provided below. I personally think it is a good introductory article about the structure of the master page in ASP. NET 2.0.
Http://msdn.microsoft.com/msdnmag/issues/04/06/ASPNET20MasterPages/
Global master page
The master page allows multi-level nesting. All sites in SharePoint use the master page default. master. This file is located in the directory c: \ Program Files \ common files \ microsoft shared \ Web Server Extensions \ 12 \ template \ global. The default. master page is a global master page. Any modification to this page will affect all SharePoint sites and the Management Center site.
Edit the master page in SharePoint designer
SharePoint designer is an alternative to the original FrontPage. SPD (SharePoint designer) allows the website designer to customize the appearance and style of the SharePoint site on a visual design interface. When we open a Sharepoint site, the structure of the site is listed in the upper-left corner of the SPD. This SharePoint site contains folders, lists, templates, and pages at a glance. The master page we are looking for is located in the following path: _ catalogs/masterpage/Default. Master
View the master page of the site in the design view, and specify the global master page in the XHTML tag. Before editing it, all the points actually point to the same page. However, after editing and saving, SPD will save a customized master page version for us in the SharePoint database. This is the same as the page Customization Mechanism (or un-ghosting) in SharePoint 2003. After a page is customized, the previous ghosting relationship is broken. That is, the custom version of the page is saved in the database instead of pointing to a file in the disk file system.
Note: after the master page of the site is modified, this change will affect all the pages under the site. Except for pages in the _ layouts directory. Because these pages are not actually pages in the site, they use a different master page (actually in the _ layouts directory ). A typical example of this type of page is the "website Settings" page.
SPD allows us to restore customized pages to the status specified by the original template. This is a feature we dreamed of in the FrontPage era. Right-click the custom page file and select this option from the context menu.
Content Page
The content page in SharePoint uses the masterpagefile attribute in the page declaration to specify the master page it uses. The Typical default master page url is ~ Masterurl/Default. master. The ~ Masterurl specifies the storage location of the master page of the site, all of which are controlled by Sharepoint. Many placeholders (content placeholder) are defined on the master page of SharePoint ). These placeholders define different areas of the page, and developers can customize the content that the placeholders ultimately display to users. Most of the placeholders defined in SharePoint do not allow users to override their content.
Most SharePoint pages include the placeholder placeholdermain, which controls the main content of the page. In typical cases, this placeholder will include a Web Part area to drag the webpart. But for developers, we can place anything we want.
The following table lists placeholders defined on the SharePoint master page: (for detailed locations, see Default. Master)
PlaceholderName |
Description |
Placeholderadditionalpagehead |
Additional content to be written in the |
Placeholderbodyareaclass |
Style appended to the body at the top of the page |
Placeholderbodyleftborder |
Border element of the page body |
Placeholderbodyrightmargin |
Right margin of the page body |
Placeholdercalendarnavigator |
A date selection box is displayed for a calendar in the page. |
Placeholderformdigest |
This is a required "form Digest" security component on the page. |
Placeholderglobalnavigation |
Site Navigation |
Placeholderhorizontalnav |
Navigation label |
Placeholderleftactions |
Action Area under the left navigation area |
Placeholderleftnavbar |
Left Navigation |
Placeholderleftnavbarborder |
Border element in the left navigation area |
Placeholderleftnavbardatasource |
Data Source in the navigation bar on the left |
Placeholderleftnavbartop |
Navigation area on the left navigation area |
Placeholdermain |
Page subject |
Placeholderminiconsole |
A place where page-level commands are placed, such as Edit page, history, and incoming links on the wiki site. |
Placeholdernavspacer |
Width of the left navigation area |
Placeholderpagedescription |
Page Description Area |
Placeholderpageimage |
Icon on the left of the page |
Placeholderpagetitle |
<Title> of the page, usually displayed in the title bar of the browser |
Placeholdersearcharea |
Search box |
Placeholdersitename |
Site name |
Placeholdertitleareaclass |
Style appended to titlearea |
Placeholdertitleareaseparator |
Titleareaseparator Area |
Placeholdertitlebreadcrumb |
Titlebreadcrumb |
Placeholdertitleintitlearea |
Title under breadcrumb |
Placeholdertitleleftborder |
Border on the left of the title Area |
Placeholdertitlerightmargin |
White space on the right of the title Area |
Placeholdertopnavbar |
Tag navigation area |
Placeholderutilitycontent |
A special piece of content required at the bottom of the page |
Spnavigation |
Windows SharePoint Services is empty by default. It is used for additional page editing controls. |
Wssdesignconsole |
Page editing control, used when the page enters the editing page mode (after clicking site actions and Edit page) |
From: http://www.cnblogs.com/Sunmoonfire/archive/2006/10/26/540957.html
