StarterMasterPages Wiki Rss Feed

Updated Wiki: Home

drisgill — Mon, 22 Apr 2013 20:46:21 GMT

Starter Master Pages for SharePoint 2013
by Randy Drisgill - MVP SharePoint Server

Updated: 4-21-2013

Download Now
Please read the FAQ

Project Description
Starter Master Pages for SharePoint are a clean, commented starting point for creating your own SharePoint branding.

Project Details
Like my previous SharePoint 2010 starter master pages, I have put together a few minimal master pages that can be used to start a SharePoint 2013 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2013 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are several versions of my Starter Master Pages:
Unlike in 2010 all of the master pages, styles, and images are loaded from the master page gallery. Please add the folder StarterBranding to your master page gallery to start with.
- Starter PubCollab - A good starting place for SharePoint Server intranet portal or team sites that may or may not have publishing (MDS enabled)
- Starter Publishing - An example publishing portal. (Not compatible with MDS / team sites)
- Starter MySiteHost - Starter Master Page for the My Sites host
- Starter Foundation - Starter Master Page for Foundation sites or standard team sites
- Starter DesignManager.html - HTML based starter master page for use with the Design Manager in SharePoint Server 2013 (not compatible with MDS / Team sites)

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Sun, 16 Dec 2012 21:28:48 GMT

Starter Master Pages for SharePoint 2013
by Randy Drisgill - MVP SharePoint Server

Updated: 12-16-2012
Updated the code to fix some issues I've discovered over the past month and a half. Namely, issues with editing surveys, adding columns, and adding "apps".

Download Now
Please read the FAQ

Project Description
Starter Master Pages for SharePoint are a clean, commented starting point for creating your own SharePoint branding.

Project Details
Like my previous SharePoint 2010 starter master pages, I have put together a few minimal master pages that can be used to start a SharePoint 2013 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2013 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are several versions of my Starter Master Pages:
Unlike in 2010 all of the master pages, styles, and images are loaded from the master page gallery. Please add the folder StarterBranding to your master page gallery to start with.
- Starter PubCollab - A good starting place for SharePoint Server intranet portal or team sites that may or may not have publishing (MDS enabled)
- Starter Publishing - An example publishing portal. (Not compatible with MDS / team sites)
- Starter MySiteHost - Starter Master Page for the My Sites host
- Starter Foundation - Starter Master Page for Foundation sites or standard team sites
- Starter DesignManager.html - HTML based starter master page for use with the Design Manager in SharePoint Server 2013 (not compatible with MDS / Team sites)

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Wed, 31 Oct 2012 22:17:58 GMT

Starter Master Pages for SharePoint 2013
by Randy Drisgill - MVP SharePoint Server

Download Now
Please read the FAQ

Project Description
Starter Master Pages for SharePoint are a clean, commented starting point for creating your own SharePoint branding.

Project Details
Like my previous SharePoint 2010 starter master pages, I have put together a few minimal master pages that can be used to start a SharePoint 2013 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2013 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are several versions of my Starter Master Pages:
Unlike in 2010 all of the master pages, styles, and images are loaded from the master page gallery. Please add the folder StarterBranding to your master page gallery to start with.
- Starter PubCollab - A good starting place for SharePoint Server intranet portal or team sites that may or may not have publishing (MDS enabled)
- Starter Publishing - An example publishing portal. (Not compatible with MDS / team sites)
- Starter MySiteHost - Starter Master Page for the My Sites host
- Starter Foundation - Starter Master Page for Foundation sites or standard team sites
- Starter DesignManager.html - HTML based starter master page for use with the Design Manager in SharePoint Server 2013 (not compatible with MDS / Team sites)

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Wed, 31 Oct 2012 21:22:15 GMT

Starter Master Pages for SharePoint 2013
by Randy Drisgill - MVP SharePoint Server

Download Now

Project Description
Starter Master Pages for SharePoint are a clean, commented starting point for creating your own SharePoint branding.

Project Details
Like my previous SharePoint 2010 starter master pages, I have put together a few minimal master pages that can be used to start a SharePoint 2013 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2013 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are several versions of my Starter Master Pages:
Unlike in 2010 all of the master pages, styles, and images are loaded from the master page gallery. Please add the folder StarterBranding to your master page gallery to start with.
- Starter PubCollab - A good starting place for SharePoint Server intranet portal or team sites that may or may not have publishing (MDS enabled)
- Starter Publishing - An example publishing portal. (Not compatible with MDS / team sites)
- Starter MySiteHost - Starter Master Page for the My Sites host
- Starter Foundation - Starter Master Page for Foundation sites or standard team sites
- Starter DesignManager.html - HTML based starter master page for use with the Design Manager in SharePoint Server 2013 (not compatible with MDS / Team sites)

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Wed, 31 Oct 2012 21:21:29 GMT

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are several versions of my Starter Master Pages:
Unlike in 2010 all of the master pages, styles, and images are loaded from the master page gallery. Please add the folder StarterBranding to your master page gallery to start with.
- Starter PubCollab - A good starting place for SharePoint Server intranet portal or team sites that may or may not have publishing (MDS enabled)
- Starter Publishing - An example publishing portal. (Not compatible with MDS / team sites)
- Starter MySiteHost - Starter Master Page for the My Sites host
- Starter Foundation - Starter Master Page for Foundation sites or standard team sites
- Starter DesignManager.html - HTML based starter master page for use with the Design Manager in SharePoint Server 2013 (not compatible with MDS / Team sites)

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Wed, 31 Oct 2012 19:50:27 GMT

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are several versions of my Starter Master Pages:
Unlike in 2010 all of the master pages, styles, and images are loaded from the master page gallery. Please add the folder StarterBranding to your master page gallery to start with.
- Starter PubCollab - A good starting place for SharePoint Server intranet portal or team sites that may or may not have publishing (MDS enabled)
- Starter Publishing - An example publishing portal. (Not compatible with MDS / team sites)
- Starter MySiteHost - Starter Master Page for the My Sites host
- Starter Foundation - Starter Master Page for Foundation sites or standard team sites
- Starter DesignManager.html - HTML based starter master page for use with the Design Manager in SharePoint Server 2013 (not compatible with MDS / Team sites)

Starter Master Page Screenshot

Cannot resolve image macro, invalid image name or id.

Updated Wiki: Home

drisgill — Wed, 31 Oct 2012 19:47:57 GMT

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are several versions of my Starter Master Pages:
Unlike in 2010 all of the master pages, styles, and images are loaded from the master page gallery. Please add the folder StarterBranding to your master page gallery to start with.

Starter PubCollab - A good starting place for SharePoint Server intranet portal or team sites that may or may not have publishing (MDS enabled)
Starter Publishing* - An example publishing portal. (Not compatible with MDS / team sites)
Starter MySiteHost* - Starter Master Page for the My Sites host
Starter Foundation* - Starter Master Page for Foundation sites or standard team sites
Starter DesignManager.html* - HTML based starter master page for use with the Design Manager in SharePoint Server 2013 (not compatible with MDS / Team sites)

Starter Master Page Screenshot

Cannot resolve image macro, invalid image name or id.

Updated Wiki: Starter Master Pages for SharePoint 2010

drisgill — Wed, 31 Oct 2012 19:22:56 GMT

Starter Master Pages for SharePoint 2010 (Formerly known as Minimal Master Pages)
by Randy Drisgill - MVP SharePoint Server

Download Now

UPDATED VERSION RELEASED ON OCTOBER 8th 2010
For a list of all changes from the last release see the WinMerge Change Report

Project Description
Starter Master Pages for SharePoint are a clean, commented starting point for creating your own SharePoint 2010 branding. Starter Master Pages were known previously as Minimal Master Pages in SharePoint 2007.

Project Details
In the tradition of those SharePoint branding folks that came before me, I have put together a few minimal master pages that can be used to start a SharePoint 2010 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2010 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Note: With SharePoint 2010, Microsoft has actually included their own master page called minimal.master which has a specific use for pages that will have very minimal chrome. Because of this, I am using the term Starter Master Page for my Master Pages instead of the term Minimal Master Page.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are three versions of my Starter Master Pages:
- _starter_publishing.master - Specifically for use with SharePoint Server 2010
- _starter_foundation.master - Specifically for use with SharePoint Foundation 2010
- _starter_meetingworkspace.master - Specifically for use with Meeting Workspaces in SharePoint 2010
These three versions are extremely similar. The primary difference being the navigation and corresponding data sources
The Starter Master Pages should work with MOST out of the box SharePoint 2010 pages including Application pages (like Site Settings), Lists and Documents, and some of My Site
- Search Center's in SharePoint use a special master page. See my post on the topic:http://blog.drisgill.com/2010/09/converting-custom-sharepoint-2010.html
Replace the word “SiteName” throughout the code with your project site’s name and directory
There are some minimal styles included and are commented accordingly.
All styles and images are loaded from the Style Library with simple “/Style Library/sitename” references. This helps with viewing them in Design View in SharePoint Designer 2010. Some deployment instances may require a more robust path usage (such as branding that is deployed to Site Collections that are not at the root web site). In these cases you can either place your styles and images in the 14 folder on the server (_layouts) or use the $SPUrl variable (more info here: http://msdn.microsoft.com/en-us/library/ee354190.aspx#odcsp2007RealWorldBrand_CreatingBrandinSP)
The SharePoint 2010 standard Ribbon controls are being used. This is the same code as in v4.master and NightAndDay.master only with the addition of some comments
The Starter Master Pages employ the standard SharePoint 2010 technique of forcing the Ribbon to “stick” to the top of the page. This is why the ribbon and main body areas are wrapped in specific div classes
There are several div’s throughout that have a class of “s4-notdlg”. This is the standard SharePoint 2010 method of hiding branding (like logos and navigation) from the SharePoint 2010 Dialog windows
I have tried to identify most of the ContentPlaceHolder’s that actually contain content in the out of the box SharePoint 2010 pages and included them in the displayable areas of the Starter Master Pages. All other unneeded (but required) ContentPlaceHolder’s are relegated to the hidden asp:Panel at the bottom of the master page.

Other optional things I have included because I think they are helpful (you can remove as needed):

Favicon code
JavaScript to address the ActiveX Name.DLL issue (Seehttp://support.microsoft.com/default.aspx/kb/931509 for more info)
Class “s4-nosetwidth” is being used to allow for fixed width branding (See http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx for more info)
An area for a header logo that has a link back to the home (you can replace this with the site icon and title if you prefer. See lines 308-317 from v4.master)
A footer area for a copyright notice
The Developer Dashboard code (which is turned on from STSADM or Powershell).
WarnOnUnsupportedBrowsers is being used at the very bottom of the Starter Master Pages to alert IE6 users that the browsing experience is deprecated

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Fri, 08 Oct 2010 21:38:17 GMT

Starter Master Pages for SharePoint 2010 (Formerly known as Minimal Master Pages)
by Randy Drisgill - MVP SharePoint Server

Download Now

UPDATED VERSION RELEASED ON OCTOBER 8th 2010
For a list of all changes from the last release see the WinMerge Change Report

Project Description
Starter Master Pages for SharePoint 2010 are a clean, commented starting point for creating your own SharePoint 2010 branding. Starter Master Pages were known previously as Minimal Master Pages in SharePoint 2007.

Project Details
In the tradition of those SharePoint branding folks that came before me, I have put together a few minimal master pages that can be used to start a SharePoint 2010 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2010 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Note: With SharePoint 2010, Microsoft has actually included their own master page called minimal.master which has a specific use for pages that will have very minimal chrome. Because of this, I am using the term Starter Master Page for my Master Pages instead of the term Minimal Master Page.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are three versions of my Starter Master Pages:
- _starter_publishing.master - Specifically for use with SharePoint Server 2010
- _starter_foundation.master - Specifically for use with SharePoint Foundation 2010
- _starter_meetingworkspace.master - Specifically for use with Meeting Workspaces in SharePoint 2010
These three versions are extremely similar. The primary difference being the navigation and corresponding data sources
The Starter Master Pages should work with MOST out of the box SharePoint 2010 pages including Application pages (like Site Settings), Lists and Documents, and some of My Site
- Search Center's in SharePoint use a special master page. See my post on the topic: http://blog.drisgill.com/2010/09/converting-custom-sharepoint-2010.html
Replace the word “SiteName” throughout the code with your project site’s name and directory
There are some minimal styles included and are commented accordingly.
All styles and images are loaded from the Style Library with simple “/Style Library/sitename” references. This helps with viewing them in Design View in SharePoint Designer 2010. Some deployment instances may require a more robust path usage (such as branding that is deployed to Site Collections that are not at the root web site). In these cases you can either place your styles and images in the 14 folder on the server (_layouts) or use the $SPUrl variable (more info here: http://msdn.microsoft.com/en-us/library/ee354190.aspx#odcsp2007RealWorldBrand_CreatingBrandinSP)
The SharePoint 2010 standard Ribbon controls are being used. This is the same code as in v4.master and NightAndDay.master only with the addition of some comments
The Starter Master Pages employ the standard SharePoint 2010 technique of forcing the Ribbon to “stick” to the top of the page. This is why the ribbon and main body areas are wrapped in specific div classes
There are several div’s throughout that have a class of “s4-notdlg”. This is the standard SharePoint 2010 method of hiding branding (like logos and navigation) from the SharePoint 2010 Dialog windows
I have tried to identify most of the ContentPlaceHolder’s that actually contain content in the out of the box SharePoint 2010 pages and included them in the displayable areas of the Starter Master Pages. All other unneeded (but required) ContentPlaceHolder’s are relegated to the hidden asp:Panel at the bottom of the master page.

Other optional things I have included because I think they are helpful (you can remove as needed):

Favicon code
JavaScript to address the ActiveX Name.DLL issue (See http://support.microsoft.com/default.aspx/kb/931509 for more info)
Class “s4-nosetwidth” is being used to allow for fixed width branding (See http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx for more info)
An area for a header logo that has a link back to the home (you can replace this with the site icon and title if you prefer. See lines 308-317 from v4.master)
A footer area for a copyright notice
The Developer Dashboard code (which is turned on from STSADM or Powershell).
WarnOnUnsupportedBrowsers is being used at the very bottom of the Starter Master Pages to alert IE6 users that the browsing experience is deprecated

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Fri, 08 Oct 2010 20:52:34 GMT

Starter Master Pages for SharePoint 2010 (Formerly known as Minimal Master Pages)
by Randy Drisgill - MVP SharePoint Server

Download Now

UPDATED VERSION RELEASED ON OCTOBER 8th 2010
For a list of all changes from the last release see the WinMerge Change Report

Project Description
Starter Master Pages for SharePoint 2010 are a clean, commented starting point for creating your own SharePoint 2010 branding. Starter Master Pages were known previously as Minimal Master Pages in SharePoint 2007.

Project Details
In the tradition of those SharePoint branding folks that came before me, I have put together a few minimal master pages that can be used to start a SharePoint 2010 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2010 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Note: With SharePoint 2010, Microsoft has actually included their own master page called minimal.master which has a specific use for pages that will have very minimal chrome. Because of this, I am using the term Starter Master Page for my Master Pages instead of the term Minimal Master Page.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are three versions of my Starter Master Pages:
- _starter_publishing.master - Specifically for use with SharePoint Server 2010
- _starter_foundation.master - Specifically for use with SharePoint Foundation 2010
- _starter_meetingworkspace.master - Specifically for use with Meeting Workspaces in SharePoint 2010
These three versions are extremely similar. The primary difference being the navigation and corresponding data sources
The Starter Master Pages should work with MOST out of the box SharePoint 2010 pages including Application pages (like Site Settings), Lists and Documents, and some of My Site
- Search Center's in SharePoint use a special master page. See my post on the topic: http://blog.drisgill.com/2010/09/converting-custom-sharepoint-2010.html
Replace the word “SiteName” throughout the code with your project site’s name and directory
There are some minimal styles included and are commented accordingly.
All styles and images are loaded from the Style Library with simple “/Style Library/sitename” references. This helps with viewing them in Design View in SharePoint Designer 2010. Some deployment instances may require a more robust path usage (such as branding that is deployed to Site Collections that are not at the root web site). In these cases you can either place your styles and images in the 14 folder on the server (_layouts) or use the $SPUrl variable (more info here: http://msdn.microsoft.com/en-us/library/ee354190.aspx#odcsp2007RealWorldBrand_CreatingBrandinSP)
The SharePoint 2010 standard Ribbon controls are being used. This is the same code as in v4.master and NightAndDay.master only with the addition of some comments
The Starter Master Pages employ the standard SharePoint 2010 technique of forcing the Ribbon to “stick” to the top of the page. This is why the ribbon and main body areas are wrapped in specific div classes
There are several div’s throughout that have a class of “s4-notdlg”. This is the standard SharePoint 2010 method of hiding branding (like logos and navigation) from the SharePoint 2010 Dialog windows
I have tried to identify most of the ContentPlaceHolder’s that actually contain content in the out of the box SharePoint 2010 pages and included them in the displayable areas of the Starter Master Pages. All other unneeded (but required) ContentPlaceHolder’s are relegated to the hidden asp:Panel at the bottom of the master page.

Other optional things I have included because I think they are helpful (you can remove as needed):

Favicon code
JavaScript to address the ActiveX Name.DLL issue (See http://support.microsoft.com/default.aspx/kb/931509 for more info)
Class “s4-nosetwidth” is being used to allow for fixed width branding (See http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx for more info)
An area for a header logo that has a link back to the home (you can replace this with the site icon and title if you prefer. See lines 308-317 from v4.master)
A footer area for a copyright notice
The Developer Dashboard code (which is turned on from STSADM or Powershell).
WarnOnUnsupportedBrowsers is being used at the very bottom of the Starter Master Pages to alert IE6 users that the browsing experience is deprecated

Starter Master Page Screenshot

Updated Wiki: Documentation

drisgill — Fri, 08 Oct 2010 20:51:45 GMT

See the Starter Master Page Change Report for a list of what has changed between the October 8th 2010 and March 7th 2010 releases

Updated Wiki: Home

drisgill — Fri, 08 Oct 2010 20:51:27 GMT

Starter Master Pages for SharePoint 2010 (Formerly known as Minimal Master Pages)
by Randy Drisgill - MVP SharePoint Server

Download Now

UPDATED VERSION RELEASED ON OCTOBER 8th 2010

Project Description
Starter Master Pages for SharePoint 2010 are a clean, commented starting point for creating your own SharePoint 2010 branding. Starter Master Pages were known previously as Minimal Master Pages in SharePoint 2007.

Project Details
In the tradition of those SharePoint branding folks that came before me, I have put together a few minimal master pages that can be used to start a SharePoint 2010 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2010 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Note: With SharePoint 2010, Microsoft has actually included their own master page called minimal.master which has a specific use for pages that will have very minimal chrome. Because of this, I am using the term Starter Master Page for my Master Pages instead of the term Minimal Master Page.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are three versions of my Starter Master Pages:
- _starter_publishing.master - Specifically for use with SharePoint Server 2010
- _starter_foundation.master - Specifically for use with SharePoint Foundation 2010
- _starter_meetingworkspace.master - Specifically for use with Meeting Workspaces in SharePoint 2010
These three versions are extremely similar. The primary difference being the navigation and corresponding data sources
The Starter Master Pages should work with MOST out of the box SharePoint 2010 pages including Application pages (like Site Settings), Lists and Documents, and some of My Site
- Search Center's in SharePoint use a special master page. See my post on the topic: http://blog.drisgill.com/2010/09/converting-custom-sharepoint-2010.html
Replace the word “SiteName” throughout the code with your project site’s name and directory
There are some minimal styles included and are commented accordingly.
All styles and images are loaded from the Style Library with simple “/Style Library/sitename” references. This helps with viewing them in Design View in SharePoint Designer 2010. Some deployment instances may require a more robust path usage (such as branding that is deployed to Site Collections that are not at the root web site). In these cases you can either place your styles and images in the 14 folder on the server (_layouts) or use the $SPUrl variable (more info here: http://msdn.microsoft.com/en-us/library/ee354190.aspx#odcsp2007RealWorldBrand_CreatingBrandinSP)
The SharePoint 2010 standard Ribbon controls are being used. This is the same code as in v4.master and NightAndDay.master only with the addition of some comments
The Starter Master Pages employ the standard SharePoint 2010 technique of forcing the Ribbon to “stick” to the top of the page. This is why the ribbon and main body areas are wrapped in specific div classes
There are several div’s throughout that have a class of “s4-notdlg”. This is the standard SharePoint 2010 method of hiding branding (like logos and navigation) from the SharePoint 2010 Dialog windows
I have tried to identify most of the ContentPlaceHolder’s that actually contain content in the out of the box SharePoint 2010 pages and included them in the displayable areas of the Starter Master Pages. All other unneeded (but required) ContentPlaceHolder’s are relegated to the hidden asp:Panel at the bottom of the master page.

Other optional things I have included because I think they are helpful (you can remove as needed):

Favicon code
JavaScript to address the ActiveX Name.DLL issue (See http://support.microsoft.com/default.aspx/kb/931509 for more info)
Class “s4-nosetwidth” is being used to allow for fixed width branding (See http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx for more info)
An area for a header logo that has a link back to the home (you can replace this with the site icon and title if you prefer. See lines 308-317 from v4.master)
A footer area for a copyright notice
The Developer Dashboard code (which is turned on from STSADM or Powershell).
WarnOnUnsupportedBrowsers is being used at the very bottom of the Starter Master Pages to alert IE6 users that the browsing experience is deprecated

Starter Master Page Screenshot

Updated Wiki: Documentation

drisgill — Fri, 08 Oct 2010 20:50:42 GMT

See the Starter Master Page Change Report for a list of what has changed between the October 8th 2010 and March 7th 2010 releases

Updated Wiki: Documentation

drisgill — Fri, 08 Oct 2010 20:50:17 GMT

See the Starter Master Page Change Report for a list of what has changed between the October 8th 2010 and March 7th 2010 releases

Updated Wiki: Documentation

drisgill — Fri, 08 Oct 2010 20:47:54 GMT

See the attached Change Report for the differences between the October 8th 2010 and March 7th 2010 release.

Updated Wiki: Documentation

drisgill — Fri, 08 Oct 2010 20:43:41 GMT

	Starter Master Page Release Candidate		Starter Master Page v1.0
	`<%@ Master language="C#" %>`		`<%@ Master language="C#" %>`
	`<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">`		`<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">`
	`<%@ Import Namespace="Microsoft.SharePoint" %>`		`<%@ Import Namespace="Microsoft.SharePoint" %>`
	`<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>`		`<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>`
	`<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>`		`<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>`
	`<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>`		`<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>`
	`<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>`		`<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>`
	`<%@ Register TagPrefix="wssuc" TagName="MUISelector" src="~/_controltemplates/MUISelector.ascx" %>`		`<%@ Register TagPrefix="wssuc" TagName="MUISelector" src="~/_controltemplates/MUISelector.ascx" %>`
	`<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>`		`<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>`
	`<html xmlns="http://www.w3.org/1999/xhtml" lang="<%$Resources:wss,language_value %>" dir="<%$Resources:wss,multipages_direction_dir_value %>" runat="server">`		`<html xmlns="http://www.w3.org/1999/xhtml" lang="<%$Resources:wss,language_value %>" dir="<%$Resources:wss,multipages_direction_dir_value %>" runat="server">`
	`<head runat="server">`		`<head runat="server">`

	`<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>`		`<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>`
	`<meta http-equiv="Expires" content="0"/>`		`<meta http-equiv="Expires" content="0"/>`
	`<meta http-equiv="X-UA-Compatible" content="IE=8"/>`		`<meta http-equiv="X-UA-Compatible" content="IE=8"/>`

	`<!-- robots -->`		`<!-- robots -->`
	`<SharePoint:RobotsMetaTag runat="server"/>`		`<SharePoint:RobotsMetaTag runat="server"/>`

	`<!-- page title - overridden by asp:content on pages or page layouts -->`		`<!-- page title - overridden by asp:content on pages or page layouts -->`
	`<title runat="server"><asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server">SiteName</asp:ContentPlaceHolder></title>`		`<title runat="server"><asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server">SiteName</asp:ContentPlaceHolder></title>`

	`<!-- favicon -->`		`<!-- favicon -->`
	`<SharePoint:SPShortcutIcon runat="server" IconUrl="/Style%20Library/sitename/favicon.ico"/>`		`<SharePoint:SPShortcutIcon runat="server" IconUrl="/Style Library/sitename/favicon.ico"/>`

	`<!-- all OOTB css -->`		`<!-- all OOTB css -->`
	`<SharePoint:CssLink runat="server" Version="4"/>`		`<SharePoint:CssLink runat="server" Version="4"/>`
	`<SharePoint:Theme runat="server"/>`		`<SharePoint:Theme runat="server"/>`

	`<!-- page manager interacts with script and the sharepoint object model -->`		`<!-- page manager interacts with script and the sharepoint object model -->`
	`<SharePoint:SPPageManager runat="server"/>`		`<SharePoint:SPPageManager runat="server"/>`

	`<!-- unified logging service -->`		`<!-- unified logging service -->`
	`<SharePoint:ULSClientConfig runat="server"/>`		`<SharePoint:ULSClientConfig runat="server"/>`

	`<!-- identifies to scripting elements that this is a v4 master page. required for scrolling? -->`		`<!-- identifies to scripting elements that this is a v4 master page. required for scrolling? -->`
	`<script type="text/javascript">`		`<script type="text/javascript">`
	`var _fV4UI = true;`		`var _fV4UI = true;`
	`</script>`		`</script>`

	`<!-- load SharePoint javascript -->`		`<!-- load SharePoint javascript -->`
	`<SharePoint:ScriptLink language="javascript" Defer="true" runat="server"/>`		`<SharePoint:ScriptLink language="javascript" Defer="true" runat="server"/>`

	`<style type="text/css">`		`<style type="text/css">`
	`/* fix scrolling on list pages */`		`/* fix scrolling on list pages */`
	`#s4-bodyContainer {`		`#s4-bodyContainer {`
	`position: relative;`		`position: relative;`
	`}`		`}`

	`/* hide body scrolling (SharePoint will handle) */`		`/* hide body scrolling (SharePoint will handle) */`
	`body {`		`body {`
	`height:100%;`		`height:100%;`
	`overflow:hidden;`		`overflow:hidden;`
	`width:100%;`		`width:100%;`
	`}`		`}`

	`/* popout breadcrumb menu needs background color for firefox */`		`/* popout breadcrumb menu needs background color for firefox */`
	`.s4-breadcrumb-menu {`		`.s4-breadcrumb-menu {`
	`background:#F2F2F2;`		`background:#F2F2F2;`
	`}`		`}`

	`/* if you want to change the left nav width, change this and the margin-left in .s4-ca */`		`/* if you want to change the left nav width, change this and the margin-left in .s4-ca */`
	`body #s4-leftpanel {`		`body #s4-leftpanel {`
	`/* width:155px; */`		`/* width:155px; */`
	`}`		`}`

	`/* body area normally has a white background */`		`/* body area normally has a white background */`
	`.s4-ca {`		`.s4-ca {`
	`background:transparent none repeat scroll 0 0;`		`background:transparent none repeat scroll 0 0;`
	`/* margin-left:155px; */`		`/* margin-left:155px; */`
	`}`		`}`
	`</style>`		`</style>`

	`<!-- link to our custom css -->`		`<!-- link to our custom css -->`
	`<SharePoint:CssRegistration name="/Style Library/sitename/style.css" After="corev4.css" runat="server"/>`		`<SharePoint:CssRegistration name="/Style Library/sitename/style.css" After="corev4.css" runat="server"/>`

	`<!-- javascript to override the active-x message in ie`		`<!-- javascript to override the active-x message in ie`
	`// See http://blog.drisgill.com/2010/02/removing-name-activex-control-warning.html for more info`		`// See http://blog.drisgill.com/2010/02/removing-name-activex-control-warning.html for more info`
	`// Remove if the IM pressence icons are needed in SharePoint`		`// Remove if the IM pressence icons are needed in SharePoint`
	`-->`		`-->`
	`<script type="text/javascript">`		`<script type="text/javascript">`
	`function ProcessImn(){}`		`function ProcessImn(){}`
	`function ProcessImnMarkers(){}`		`function ProcessImnMarkers(){}`
	`</script>`		`</script>`

	`<!-- additional header delegate control -->`		`<!-- additional header delegate control -->`
	`<SharePoint:DelegateControl runat="server" ControlId="AdditionalPageHead" AllowMultipleControls="true"/>`		`<SharePoint:DelegateControl runat="server" ControlId="AdditionalPageHead" AllowMultipleControls="true"/>`

	`<!-- additional header placeholder - overridden by asp:content on pages or page layouts -->`		`<!-- additional header placeholder - overridden by asp:content on pages or page layouts -->`
	`<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server"/>`

	`<!-- microsoft says these should always be inside the head tag. -->`		`<!-- microsoft says these should always be inside the head tag. -->`
	`<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server"/>`
	`<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server"/>`
	`</head>`		`</head>`

	`<body scroll="no" onload="javascript:_spBodyOnLoadWrapper();">`		`<body scroll="no" onload="javascript:_spBodyOnLoadWrapper();">`

	`<form runat="server" onsubmit="return _spFormOnSubmitWrapper();">`		`<form runat="server" onsubmit="return _spFormOnSubmitWrapper();">`

	`<!-- handles SharePoint scripts -->`		`<!-- handles SharePoint scripts -->`
	`<asp:ScriptManager id="ScriptManager" runat="server" EnablePageMethods="false" EnablePartialRendering="true" EnableScriptGlobalization="false" EnableScriptLocalization="true" />`		`<asp:ScriptManager id="ScriptManager" runat="server" EnablePageMethods="false" EnablePartialRendering="true" EnableScriptGlobalization="false" EnableScriptLocalization="true" />`

	`<!-- controls the web parts and zones -->`		`<!-- controls the web parts and zones -->`
	`<WebPartPages:SPWebPartManager runat="server"/>`		`<WebPartPages:SPWebPartManager runat="server"/>`

	`<!-- this control is more navigation for mysites, otherwise it is empty -->`		`<!-- this control is more navigation for mysites, otherwise it is empty -->`
	`<SharePoint:DelegateControl runat="server" ControlId="GlobalNavigation"/>`		`<SharePoint:DelegateControl runat="server" ControlId="GlobalNavigation"/>`

	`<!-- ===== Begin Ribbon ============================================================ -->`		`<!-- ===== Begin Ribbon ============================================================ -->`

	`<div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle">`		`<div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle">`
	`<div id="s4-ribboncont">`		`<div id="s4-ribboncont">`

	`<!-- ribbon starts here -->`		`<!-- ribbon starts here -->`
	`<SharePoint:SPRibbon`		`<SharePoint:SPRibbon`
	`runat="server"`		`runat="server"`
	`PlaceholderElementId="RibbonContainer"`		`PlaceholderElementId="RibbonContainer"`
	`CssFile="">`		`CssFile="">`

	`<!-- ribbon left side content starts here -->`		`<!-- ribbon left side content starts here -->`
	`<SharePoint:SPRibbonPeripheralContent`		`<SharePoint:SPRibbonPeripheralContent`
	`runat="server"`		`runat="server"`
	`Location="TabRowLeft"`		`Location="TabRowLeft"`
	`CssClass="ms-siteactionscontainer s4-notdlg">`		`CssClass="ms-siteactionscontainer s4-notdlg">`

	`<!-- site actions -->`		`<!-- site actions -->`
	`<span class="ms-siteactionsmenu" id="siteactiontd">`		`<span class="ms-siteactionsmenu" id="siteactiontd">`
	`<SharePoint:SiteActions runat="server" accesskey="<%$Resources:wss,tb_SiteActions_AK%>" id="SiteActionsMenuMain"`		`<SharePoint:SiteActions runat="server" accesskey="<%$Resources:wss,tb_SiteActions_AK%>" id="SiteActionsMenuMain"`
	`PrefixHtml=""`		`PrefixHtml=""`
	`SuffixHtml=""`		`SuffixHtml=""`
	`MenuNotVisibleHtml="&nbsp;"`		`MenuNotVisibleHtml="&nbsp;"`
	`>`		`>`
	`<CustomTemplate>`		`<CustomTemplate>`
	`<SharePoint:FeatureMenuTemplate runat="server"`		`<SharePoint:FeatureMenuTemplate runat="server"`
	`FeatureScope="Site"`		`FeatureScope="Site"`
	`Location="Microsoft.SharePoint.StandardMenu"`		`Location="Microsoft.SharePoint.StandardMenu"`
	`GroupId="SiteActions"`		`GroupId="SiteActions"`
	`UseShortId="true"`		`UseShortId="true"`
	`>`		`>`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_EditPage"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_EditPage"`
	`Text="<%$Resources:wss,siteactions_editpage%>"`		`Text="<%$Resources:wss,siteactions_editpage%>"`
	`Description="<%$Resources:wss,siteactions_editpagedescriptionv4%>"`		`Description="<%$Resources:wss,siteactions_editpagedescriptionv4%>"`
	`ImageUrl="/_layouts/images/ActionsEditPage.png"`		`ImageUrl="/_layouts/images/ActionsEditPage.png"`
	`MenuGroupId="100"`		`MenuGroupId="100"`
	`Sequence="110"`		`Sequence="110"`
	`ClientOnClickNavigateUrl="javascript:ChangeLayoutMode(false);"`		`ClientOnClickNavigateUrl="javascript:ChangeLayoutMode(false);"`
	`/>`		`/>`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_TakeOffline"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_TakeOffline"`
	`Text="<%$Resources:wss,siteactions_takeoffline%>"`		`Text="<%$Resources:wss,siteactions_takeoffline%>"`
	`Description="<%$Resources:wss,siteactions_takeofflinedescription%>"`		`Description="<%$Resources:wss,siteactions_takeofflinedescription%>"`
	`ImageUrl="/_layouts/images/connecttospworkspace32.png"`		`ImageUrl="/_layouts/images/connecttospworkspace32.png"`
	`MenuGroupId="100"`		`MenuGroupId="100"`
	`Sequence="120"`		`Sequence="120"`
	`/>`		`/>`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_CreatePage"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_CreatePage"`
	`Text="<%$Resources:wss,siteactions_createpage%>"`		`Text="<%$Resources:wss,siteactions_createpage%>"`
	`Description="<%$Resources:wss,siteactions_createpagedesc%>"`		`Description="<%$Resources:wss,siteactions_createpagedesc%>"`
	`ImageUrl="/_layouts/images/NewContentPageHH.png"`		`ImageUrl="/_layouts/images/NewContentPageHH.png"`
	`MenuGroupId="200"`		`MenuGroupId="200"`
	`Sequence="210"`		`Sequence="210"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('Page')) { OpenCreateWebPageDialog('~site/_layouts/createwebpage.aspx') }"`		`ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('Page')) { OpenCreateWebPageDialog('~site/_layouts/createwebpage.aspx') }"`
	`PermissionsString="AddListItems, EditListItems"`		`PermissionsString="AddListItems, EditListItems"`
	`PermissionMode="All" />`		`PermissionMode="All" />`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_CreateDocLib"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_CreateDocLib"`
	`Text="<%$Resources:wss,siteactions_createdoclib%>"`		`Text="<%$Resources:wss,siteactions_createdoclib%>"`
	`Description="<%$Resources:wss,siteactions_createdoclibdesc%>"`		`Description="<%$Resources:wss,siteactions_createdoclibdesc%>"`
	`ImageUrl="/_layouts/images/NewDocLibHH.png"`		`ImageUrl="/_layouts/images/NewDocLibHH.png"`
	`MenuGroupId="200"`		`MenuGroupId="200"`
	`Sequence="220"`		`Sequence="220"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('DocLib')) { GoToPage('~site/_layouts/new.aspx?FeatureId={00bfea71-e717-4e80-aa17-d0c71b360101}&ListTemplate=101') }"`		`ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('DocLib')) { GoToPage('~site/_layouts/new.aspx?FeatureId={00bfea71-e717-4e80-aa17-d0c71b360101}&ListTemplate=101') }"`
	`PermissionsString="ManageLists"`		`PermissionsString="ManageLists"`
	`PermissionMode="Any"`		`PermissionMode="Any"`
	`VisibilityFeatureId="00BFEA71-E717-4E80-AA17-D0C71B360101" />`		`VisibilityFeatureId="00BFEA71-E717-4E80-AA17-D0C71B360101" />`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_CreateSite"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_CreateSite"`
	`Text="<%$Resources:wss,siteactions_createsite%>"`		`Text="<%$Resources:wss,siteactions_createsite%>"`
	`Description="<%$Resources:wss,siteactions_createsitedesc%>"`		`Description="<%$Resources:wss,siteactions_createsitedesc%>"`
	`ImageUrl="/_layouts/images/newweb32.png"`		`ImageUrl="/_layouts/images/newweb32.png"`
	`MenuGroupId="200"`		`MenuGroupId="200"`
	`Sequence="230"`		`Sequence="230"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('Site')) { STSNavigate('~site/_layouts/newsbweb.aspx') }"`		`ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('Site')) { STSNavigate('~site/_layouts/newsbweb.aspx') }"`
	`PermissionsString="ManageSubwebs,ViewFormPages"`		`PermissionsString="ManageSubwebs,ViewFormPages"`
	`PermissionMode="All" />`		`PermissionMode="All" />`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_Create"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_Create"`
	`Text="<%$Resources:wss,siteactions_create%>"`		`Text="<%$Resources:wss,siteactions_create%>"`
	`Description="<%$Resources:wss,siteactions_createdesc%>"`		`Description="<%$Resources:wss,siteactions_createdesc%>"`
	`MenuGroupId="200"`		`MenuGroupId="200"`
	`Sequence="240"`		`Sequence="240"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('All')) { STSNavigate('~site/_layouts/create.aspx') }"`		`ClientOnClickScriptContainingPrefixedUrl="if (LaunchCreateHandler('All')) { STSNavigate('~site/_layouts/create.aspx') }"`
	`PermissionsString="ManageLists, ManageSubwebs"`		`PermissionsString="ManageLists, ManageSubwebs"`
	`PermissionMode="Any" />`		`PermissionMode="Any" />`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_ViewAllSiteContents"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_ViewAllSiteContents"`
	`Text="<%$Resources:wss,quiklnch_allcontent%>"`		`Text="<%$Resources:wss,quiklnch_allcontent%>"`
	`Description="<%$Resources:wss,siteactions_allcontentdescription%>"`		`Description="<%$Resources:wss,siteactions_allcontentdescription%>"`
	`ImageUrl="/_layouts/images/allcontent32.png"`		`ImageUrl="/_layouts/images/allcontent32.png"`
	`MenuGroupId="300"`		`MenuGroupId="300"`
	`Sequence="302"`		`Sequence="302"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickNavigateUrl="~site/_layouts/viewlsts.aspx"`		`ClientOnClickNavigateUrl="~site/_layouts/viewlsts.aspx"`
	`PermissionsString="ViewFormPages"`		`PermissionsString="ViewFormPages"`
	`PermissionMode="Any" />`		`PermissionMode="Any" />`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_EditSite"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_EditSite"`
	`Text="<%$Resources:wss,siteactions_editsite%>"`		`Text="<%$Resources:wss,siteactions_editsite%>"`
	`Description="<%$Resources:wss,siteactions_editsitedescription%>"`		`Description="<%$Resources:wss,siteactions_editsitedescription%>"`
	`ImageUrl="/_layouts/images/SharePointDesigner32.png"`		`ImageUrl="/_layouts/images/SharePointDesigner32.png"`
	`MenuGroupId="300"`		`MenuGroupId="300"`
	`Sequence="304"`		`Sequence="304"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickScriptContainingPrefixedUrl="EditInSPD('~site/',true);"`		`ClientOnClickScriptContainingPrefixedUrl="EditInSPD('~site/',true);"`
	`PermissionsString="AddAndCustomizePages"`		`PermissionsString="AddAndCustomizePages"`
	`PermissionMode="Any"`		`PermissionMode="Any"`
	`/>`		`/>`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_SitePermissions"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_SitePermissions"`
	`Text="<%$Resources:wss,people_sitepermissions%>"`		`Text="<%$Resources:wss,people_sitepermissions%>"`
	`Description="<%$Resources:wss,siteactions_sitepermissiondescriptionv4%>"`		`Description="<%$Resources:wss,siteactions_sitepermissiondescriptionv4%>"`
	`ImageUrl="/_layouts/images/Permissions32.png"`		`ImageUrl="/_layouts/images/Permissions32.png"`
	`MenuGroupId="300"`		`MenuGroupId="300"`
	`Sequence="310"`		`Sequence="310"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickNavigateUrl="~site/_layouts/user.aspx"`		`ClientOnClickNavigateUrl="~site/_layouts/user.aspx"`
	`PermissionsString="EnumeratePermissions"`		`PermissionsString="EnumeratePermissions"`
	`PermissionMode="Any" />`		`PermissionMode="Any" />`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_Settings"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_Settings"`
	`Text="<%$Resources:wss,settings_pagetitle%>"`		`Text="<%$Resources:wss,settings_pagetitle%>"`
	`Description="<%$Resources:wss,siteactions_sitesettingsdescriptionv4%>"`		`Description="<%$Resources:wss,siteactions_sitesettingsdescriptionv4%>"`
	`ImageUrl="/_layouts/images/settingsIcon.png"`		`ImageUrl="/_layouts/images/settingsIcon.png"`
	`MenuGroupId="300"`		`MenuGroupId="300"`
	`Sequence="320"`		`Sequence="320"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickNavigateUrl="~site/_layouts/settings.aspx"`		`ClientOnClickNavigateUrl="~site/_layouts/settings.aspx"`
	`PermissionsString="EnumeratePermissions,ManageWeb,ManageSubwebs,AddAndCustomizePages,ApplyThemeAndBorder,ManageAlerts,ManageLists,ViewUsageData"`		`PermissionsString="EnumeratePermissions,ManageWeb,ManageSubwebs,AddAndCustomizePages,ApplyThemeAndBorder,ManageAlerts,ManageLists,ViewUsageData"`
	`PermissionMode="Any" />`		`PermissionMode="Any" />`
	`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_CommitNewUI"`		`<SharePoint:MenuItemTemplate runat="server" id="MenuItem_CommitNewUI"`
	`Text="<%$Resources:wss,siteactions_commitnewui%>"`		`Text="<%$Resources:wss,siteactions_commitnewui%>"`
	`Description="<%$Resources:wss,siteactions_commitnewuidescription%>"`		`Description="<%$Resources:wss,siteactions_commitnewuidescription%>"`
	`ImageUrl="/_layouts/images/visualupgradehh.png"`		`ImageUrl="/_layouts/images/visualupgradehh.png"`
	`MenuGroupId="300"`		`MenuGroupId="300"`
	`Sequence="330"`		`Sequence="330"`
	`UseShortId="true"`		`UseShortId="true"`
	`ClientOnClickScriptContainingPrefixedUrl="GoToPage('~site/_layouts/prjsetng.aspx')"`		`ClientOnClickScriptContainingPrefixedUrl="GoToPage('~site/_layouts/prjsetng.aspx')"`
	`PermissionsString="ManageWeb"`		`PermissionsString="ManageWeb"`
	`PermissionMode="Any"`		`PermissionMode="Any"`
	`ShowOnlyIfUIVersionConfigurationEnabled="true" />`		`ShowOnlyIfUIVersionConfigurationEnabled="true" />`
	`</SharePoint:FeatureMenuTemplate>`		`</SharePoint:FeatureMenuTemplate>`
	`</CustomTemplate>`		`</CustomTemplate>`
	`</SharePoint:SiteActions></span>`		`</SharePoint:SiteActions></span>`

	`<!-- global navigation dhtml popout menu -->`		`<!-- global navigation dhtml popout menu -->`
	`<asp:ContentPlaceHolder id="PlaceHolderGlobalNavigation" runat="server">`		`<asp:ContentPlaceHolder id="PlaceHolderGlobalNavigation" runat="server">`
	`<SharePoint:PopoutMenu`		`<SharePoint:PopoutMenu`
	`runat="server"`		`runat="server"`
	`ID="GlobalBreadCrumbNavPopout"`		`ID="GlobalBreadCrumbNavPopout"`
	`IconUrl="/_layouts/images/fgimg.png"`		`IconUrl="/_layouts/images/fgimg.png"`
	`IconAlt="<%$Resources:wss,master_breadcrumbIconAlt%>"`		`IconAlt="<%$Resources:wss,master_breadcrumbIconAlt%>"`
	`IconOffsetX=0`		`IconOffsetX=0`
	`IconOffsetY=112`		`IconOffsetY=112`
	`IconWidth=16`		`IconWidth=16`
	`IconHeight=16`		`IconHeight=16`
	`AnchorCss="s4-breadcrumb-anchor"`		`AnchorCss="s4-breadcrumb-anchor"`
	`AnchorOpenCss="s4-breadcrumb-anchor-open"`		`AnchorOpenCss="s4-breadcrumb-anchor-open"`
	`MenuCss="s4-breadcrumb-menu">`		`MenuCss="s4-breadcrumb-menu">`
	`<div class="s4-breadcrumb-top">`		`<div class="s4-breadcrumb-top">`
	`<asp:Label runat="server" CssClass="s4-breadcrumb-header" Text="<%$Resources:wss,master_breadcrumbHeader%>" />`		`<asp:Label runat="server" CssClass="s4-breadcrumb-header" Text="<%$Resources:wss,master_breadcrumbHeader%>" />`
	`</div>`		`</div>`
	`<asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server">`		`<asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server">`
	`<SharePoint:ListSiteMapPath`		`<SharePoint:ListSiteMapPath`
	`runat="server"`		`runat="server"`
	`SiteMapProviders="SPSiteMapProvider,SPContentMapProvider"`		`SiteMapProviders="SPSiteMapProvider,SPContentMapProvider"`
	`RenderCurrentNodeAsLink="false"`		`RenderCurrentNodeAsLink="false"`
	`PathSeparator=""`		`PathSeparator=""`
	`CssClass="s4-breadcrumb"`		`CssClass="s4-breadcrumb"`
	`NodeStyle-CssClass="s4-breadcrumbNode"`		`NodeStyle-CssClass="s4-breadcrumbNode"`
	`CurrentNodeStyle-CssClass="s4-breadcrumbCurrentNode"`		`CurrentNodeStyle-CssClass="s4-breadcrumbCurrentNode"`
	`RootNodeStyle-CssClass="s4-breadcrumbRootNode"`		`RootNodeStyle-CssClass="s4-breadcrumbRootNode"`
	`NodeImageOffsetX=0`		`NodeImageOffsetX=0`
	`NodeImageOffsetY=353`		`NodeImageOffsetY=353`
	`NodeImageWidth=16`		`NodeImageWidth=16`
	`NodeImageHeight=16`		`NodeImageHeight=16`
	`NodeImageUrl="/_layouts/images/fgimg.png"`		`NodeImageUrl="/_layouts/images/fgimg.png"`
	`RTLNodeImageOffsetX=0`		`RTLNodeImageOffsetX=0`
	`RTLNodeImageOffsetY=376`		`RTLNodeImageOffsetY=376`
	`RTLNodeImageWidth=16`		`RTLNodeImageWidth=16`
	`RTLNodeImageHeight=16`		`RTLNodeImageHeight=16`
	`RTLNodeImageUrl="/_layouts/images/fgimg.png"`		`RTLNodeImageUrl="/_layouts/images/fgimg.png"`
	`HideInteriorRootNodes="true"`		`HideInteriorRootNodes="true"`
	`SkipLinkText="" />`		`SkipLinkText="" />`
	`</asp:ContentPlaceHolder>`		`</asp:ContentPlaceHolder>`
	`</SharePoint:PopoutMenu>`		`</SharePoint:PopoutMenu>`
	`</asp:ContentPlaceHolder>`		`</asp:ContentPlaceHolder>`

	`<!-- save button at top of ribbon -->`		`<!-- save button at top of ribbon -->`
	`<SharePoint:PageStateActionButton id="PageStateActionButton" runat="server" Visible="false" /></SharePoint:SPRibbonPeripheralContent>`		`<SharePoint:PageStateActionButton id="PageStateActionButton" runat="server" Visible="false" /></SharePoint:SPRibbonPeripheralContent>`

	`<!-- ribbon right side content starts here -->`		`<!-- ribbon right side content starts here -->`
	`<SharePoint:SPRibbonPeripheralContent`		`<SharePoint:SPRibbonPeripheralContent`
	`runat="server"`		`runat="server"`
	`Location="TabRowRight"`		`Location="TabRowRight"`
	`ID="RibbonTabRowRight"`		`ID="RibbonTabRowRight"`
	`CssClass="s4-trc-container s4-notdlg">`		`CssClass="s4-trc-container s4-notdlg">`

	`<!-- GlobalSiteLink0 delegate default shows nothing -->`		`<!-- GlobalSiteLink0 delegate - the variation selector / shows nothing by default otherwise -->`
	`<SharePoint:DelegateControl runat="server" ID="GlobalDelegate0" ControlId="GlobalSiteLink0" />`		`<SharePoint:DelegateControl runat="server" ID="GlobalDelegate0" ControlId="GlobalSiteLink0" />`

	`<!-- Welcome / Login control -->`		`<!-- Welcome / Login control -->`
	`<div class="s4-trc-container-menu">`		`<div class="s4-trc-container-menu">`
	`<div>`		`<div>`
	`<wssuc:Welcome id="IdWelcome" runat="server" EnableViewState="false">`		`<wssuc:Welcome id="IdWelcome" runat="server" EnableViewState="false">`
	`</wssuc:Welcome>`		`</wssuc:Welcome>`
	`<!-- MultiLingual User Interface menu -->`		`<!-- MultiLingual User Interface menu -->`
	`<wssuc:MUISelector ID="IdMuiSelector" runat="server"/>`		`<wssuc:MUISelector ID="IdMuiSelector" runat="server"/>`
	`</div>`		`</div>`
	`</div>`		`</div>`

	`<!-- GlobalSiteLink2 delegate default shows nothing -->`		`<!-- GlobalSiteLink2 delegate default shows nothing -->`
	`<SharePoint:DelegateControl ControlId="GlobalSiteLink2" ID="GlobalDelegate2" Scope="Farm" runat="server" />`		`<SharePoint:DelegateControl ControlId="GlobalSiteLink2" ID="GlobalDelegate2" Scope="Farm" runat="server" />`

	`<!-- link to launch developer dashboard if its activated by admin -->`		`<!-- link to launch developer dashboard if its activated by admin -->`
	`<span>`		`<span>`
	`<span class="s4-devdashboard">`		`<span class="s4-devdashboard">`
	`<Sharepoint:DeveloperDashboardLauncher`		`<Sharepoint:DeveloperDashboardLauncher`
	`ID="DeveloperDashboardLauncher"`		`ID="DeveloperDashboardLauncher"`
	`NavigateUrl="javascript:ToggleDeveloperDashboard()"`		`NavigateUrl="javascript:ToggleDeveloperDashboard()"`
	`runat="server"`		`runat="server"`
	`ImageUrl="/_layouts/images/fgimg.png"`		`ImageUrl="/_layouts/images/fgimg.png"`
	`Text="<%$Resources:wss,multipages_launchdevdashalt_text%>"`		`Text="<%$Resources:wss,multipages_launchdevdashalt_text%>"`
	`OffsetX=0`		`OffsetX=0`
	`OffsetY=222`		`OffsetY=222`
	`Height=16`		`Height=16`
	`Width=16 />`		`Width=16 />`
	`</span>`		`</span>`
	`</span>`		`</span>`
	`</SharePoint:SPRibbonPeripheralContent>`		`</SharePoint:SPRibbonPeripheralContent>`
	`</SharePoint:SPRibbon>`		`</SharePoint:SPRibbon>`

	`<!-- end main ribbon control -->`		`<!-- end main ribbon control -->`
	`</div>`		`</div>`

	`<!-- dynamic notification area -->`		`<!-- dynamic notification area -->`
	`<div id="notificationArea" class="s4-noti"></div>`		`<div id="notificationArea" class="s4-noti"></div>`

	`<!-- old navigation delegate? -->`		`<!-- old navigation delegate? -->`
	`<asp:ContentPlaceHolder ID="SPNavigation" runat="server">`		`<asp:ContentPlaceHolder ID="SPNavigation" runat="server">`
	`<SharePoint:DelegateControl runat="server" ControlId="PublishingConsole" Id="PublishingConsoleDelegate">`		`<SharePoint:DelegateControl runat="server" ControlId="PublishingConsole" Id="PublishingConsoleDelegate">`
	`</SharePoint:DelegateControl>`		`</SharePoint:DelegateControl>`
	`</asp:ContentPlaceHolder>`		`</asp:ContentPlaceHolder>`

	`<!-- top web part panel -->`		`<!-- top web part panel -->`
	`<div id="WebPartAdderUpdatePanelContainer">`		`<div id="WebPartAdderUpdatePanelContainer">`
	`<asp:UpdatePanel`		`<asp:UpdatePanel`
	`ID="WebPartAdderUpdatePanel"`		`ID="WebPartAdderUpdatePanel"`
	`UpdateMode="Conditional"`		`UpdateMode="Conditional"`
	`ChildrenAsTriggers="false"`		`ChildrenAsTriggers="false"`
	`runat="server">`		`runat="server">`
	`<ContentTemplate>`		`<ContentTemplate>`
	`<WebPartPages:WebPartAdder ID="WebPartAdder" runat="server" />`		`<WebPartPages:WebPartAdder ID="WebPartAdder" runat="server" />`
	`</ContentTemplate>`		`</ContentTemplate>`
	`<Triggers>`		`<Triggers>`
	`<asp:PostBackTrigger ControlID="WebPartAdder" />`		`<asp:PostBackTrigger ControlID="WebPartAdder" />`
	`</Triggers>`		`</Triggers>`
	`</asp:UpdatePanel>`		`</asp:UpdatePanel>`
	`</div>`		`</div>`
	`</div>`		`</div>`

	`<!-- ===== End Ribbon and other Top Content ============================================================ -->`		`<!-- ===== End Ribbon and other Top Content ============================================================ -->`


	`<!-- ===== Start Scrolling Body Area ============================================================ -->`		`<!-- ===== Start Scrolling Body Area ============================================================ -->`

	`<!-- these two div id's are used to setup the main scrolling page area, they should stay if you are sticking the ribbon to the top -->`		`<!-- these two div id's are used to setup the main scrolling page area, they should stay if you are sticking the ribbon to the top -->`
	`<div ID="s4-workspace" class="s4-nosetwidth"> <!-- NOTE: s4-nosetwidth is used when you are setting a fixed page width in css, remove for 100% -->`		`<div ID="s4-workspace" class="s4-nosetwidth"> <!-- NOTE: s4-nosetwidth is used when you are setting a fixed page width in css, remove for 100% -->`
	`<div ID="s4-bodyContainer">`		`<div ID="s4-bodyContainer">`

	`<!-- link back to homepage, can place a logo image here for link back to home, or evan use CssClass to style it with CSS -->`		`<!-- id="mso_contentdiv" required, helps SharePoint put the web part editing pane in the main body on the right, you can move the ID if needed -->`
			`<div id="MSO_ContentDiv" runat="server">`

			`<!-- link back to homepage, SiteLogoImage gets replaced by the Site Icon, you can hard code this so that its not overridden by the Site Icon or even remove -->`
	`<div class="s4-notdlg"><!-- NOTE: any time you see s4-notdlg, this element will be hidden from SharePoint dialog windows -->`		`<div class="s4-notdlg"><!-- NOTE: any time you see s4-notdlg, this element will be hidden from SharePoint dialog windows -->`
	`<SharePoint:SPLinkButton runat="server" NavigateUrl="~sitecollection/" ToolTip="Back to Home">SiteName Logo</SharePoint:SPLinkButton>`		`<SharePoint:SPLinkButton runat="server" NavigateUrl="~sitecollection/">`
			`<SharePoint:SiteLogoImage LogoImageUrl="/Style Library/sitename/logo.png" runat="server"/>`
			`</SharePoint:SPLinkButton>`
	`</div>`		`</div>`

	`<!-- search box loads from delegate, style with CSS -->`		`<!-- search box loads from delegate, style with CSS -->`
	`<div class="s4-notdlg">`		`<div class="s4-notdlg">`
	`<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server">`		`<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server">`
	`<SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" Version="4"/>`		`<SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" Version="4"/>`
	`</asp:ContentPlaceHolder>`		`</asp:ContentPlaceHolder>`
	`</div>`		`</div>`

	`<!-- top navigation area -->`		`<!-- top navigation area -->`
	`<div class="s4-notdlg">`		`<div class="s4-notdlg">`
	`<!-- top navigation publishing data source -->`		`<!-- top navigation publishing data source -->`
	`<PublishingNavigation:PortalSiteMapDataSource`		`<PublishingNavigation:PortalSiteMapDataSource`
	`ID="topSiteMap"`		`ID="topSiteMap"`
	`runat="server"`		`runat="server"`
	`EnableViewState="false"`		`EnableViewState="false"`
	`SiteMapProvider="CombinedNavSiteMapProvider"`		`SiteMapProvider="GlobalNavigation"`
	`StartFromCurrentNode="true"`		`StartFromCurrentNode="true"`
	`StartingNodeOffset="0"`		`StartingNodeOffset="0"`
	`ShowStartingNode="false"`		`ShowStartingNode="false"`
	`TrimNonCurrentTypes="Heading"/>`		`TrimNonCurrentTypes="Heading"/>`

	`<!-- top navigation menu (set to use the new Simple Rendering) -->`		`<!-- top navigation menu (set to use the new Simple Rendering) -->`
	`<SharePoint:AspMenu`		`<SharePoint:AspMenu`
	`ID="TopNavigationMenuV4"`		`ID="TopNavigationMenuV4"`
			`EncodeTitle="false"`
	`Runat="server"`		`Runat="server"`
	`EnableViewState="false"`		`EnableViewState="false"`
	`DataSourceID="topSiteMap"`		`DataSourceID="topSiteMap"`
	`AccessKey="<%$Resources:wss,navigation_accesskey%>"`		`AccessKey="<%$Resources:wss,navigation_accesskey%>"`
	`UseSimpleRendering="true"`		`UseSimpleRendering="true"`
	`UseSeparateCss="false"`		`UseSeparateCss="false"`
	`Orientation="Horizontal"`		`Orientation="Horizontal"`
	`StaticDisplayLevels="1"`		`StaticDisplayLevels="1"`
	`MaximumDynamicDisplayLevels="1"`		`MaximumDynamicDisplayLevels="1"`
	`SkipLinkText=""`		`SkipLinkText=""`
	`CssClass="s4-tn">`		`CssClass="s4-tn">`
	`</SharePoint:AspMenu>`		`</SharePoint:AspMenu>`
	`</div>`		`</div>`

	`<!-- page editing status bar -->`		`<!-- page editing status bar -->`
	`<div class="s4-notdlg">`		`<div class="s4-notdlg">`
	`<div id="s4-statusbarcontainer" class="s4-notdlg">`		`<div id="s4-statusbarcontainer" class="s4-notdlg">`
	`<div id="pageStatusBar" class="s4-status-s1"></div>`		`<div id="pageStatusBar" class="s4-status-s1"></div>`
	`</div>`		`</div>`
	`</div>`		`</div>`


	`<!-- styles needed to have left nav to the left of the main area -->`		`<!-- styles needed to have left nav to the left of the main area -->`
	`<div id="s4-leftpanel" class="s4-notdlg">`		`<div id="s4-leftpanel" class="s4-notdlg">`
	`<!-- The quick launch bar / left navigation -->`		`<!-- The quick launch bar / left navigation -->`
	`<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server">`		`<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server">`
	`<PublishingNavigation:PortalSiteMapDataSource`		`<PublishingNavigation:PortalSiteMapDataSource`
	`ID="SiteMapDS"`		`ID="SiteMapDS"`
	`runat="server"`		`runat="server"`
	`EnableViewState="false"`		`EnableViewState="false"`
	`SiteMapProvider="CurrentNavigation"`		`SiteMapProvider="CurrentNavigation"`
	`StartFromCurrentNode="true"`		`StartFromCurrentNode="true"`
	`StartingNodeOffset="0"`		`StartingNodeOffset="0"`
	`ShowStartingNode="false"`		`ShowStartingNode="false"`
	`TrimNonCurrentTypes="Heading"/>`		`TrimNonCurrentTypes="Heading"/>`
	`<SharePoint:AspMenu`		`<SharePoint:AspMenu`
	`ID="CurrentNav"`		`ID="CurrentNav"`
			`EncodeTitle="false"`
	`runat="server"`		`runat="server"`
	`EnableViewState="false"`		`EnableViewState="false"`
	`DataSourceID="SiteMapDS"`		`DataSourceID="SiteMapDS"`
	`UseSeparateCSS="false"`		`UseSeparateCSS="false"`
	`UseSimpleRendering="true"`		`UseSimpleRendering="true"`
	`Orientation="Vertical"`		`Orientation="Vertical"`
	`StaticDisplayLevels="2"`		`StaticDisplayLevels="2"`
	`MaximumDynamicDisplayLevels="0"`		`MaximumDynamicDisplayLevels="0"`
	`CssClass=""`		`CssClass="s4-ql"`
	`SkipLinkText="<%$Resources:cms,masterpages_skiplinktext%>"/>`		`SkipLinkText="<%$Resources:cms,masterpages_skiplinktext%>"/>`
	`</asp:ContentPlaceHolder>`		`</asp:ContentPlaceHolder>`

	`<!-- The small menu attached Quick Launch bar. Used only on very specific pages -->`		`<!-- The small menu attached Quick Launch bar. Used only on very specific pages -->`
	`<asp:ContentPlaceHolder id="PlaceHolderLeftActions" runat ="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderLeftActions" runat ="server"/>`
	`</div>`		`</div>`

	`<!-- s4-ca is the main body div -->`		`<!-- s4-ca is the main body div -->`
	`<div class="s4-ca" id="MSO_ContentTable">`		`<div class="s4-ca">`

	`<div class="s4-notdlg">`		`<div class="s4-notdlg">`
	`<!-- links for I like it and Tags and Notes -->`		`<!-- links for I like it and Tags and Notes -->`
	`<!-- use ControlID="GlobalSiteLink3" for larger icons or remove this line entirely for no icons -->`		`<!-- use ControlID="GlobalSiteLink3" for larger icons or remove this line entirely for no icons -->`
	`<SharePoint:DelegateControl ControlId="GlobalSiteLink3-mini" Scope="Farm" runat="server"/>`		`<SharePoint:DelegateControl ControlId="GlobalSiteLink3-mini" Scope="Farm" runat="server"/>`
	`</div>`		`</div>`

	`<div id="s4-titlerow" class="s4-notdlg">`		`<div class="s4-notdlg">`
	`<!-- page title -->`		`<!-- page title -->`
	`<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea" runat="server" />`		`<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea" runat="server" />`
	`</div>`		`</div>`

	`<!-- page description -->`		`<!-- place a table around this to handle funky markup in _Layouts/areacachesettings.aspx (if you want) -->`
	`<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat="server" />`

	`<!-- mso_contentdiv required, helps SharePoint put the web part editing pane in the main body on the right -->`		`<div>`
	`<div id="MSO_ContentDiv" runat="server">`
	`<!-- page content loads from the pages and pages layout -->`		`<!-- page content loads from the pages and pages layout -->`
	`<asp:ContentPlaceHolder id="PlaceHolderMain" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderMain" runat="server"/>`
	`</div>`		`</div>`
	`</div>`		`</div>`


	`<!-- footer - this is purely optional -->`		`<!-- footer - this is purely optional -->`
	`<div class="s4-notdlg" style="clear: both;">`		`<div class="s4-notdlg" style="clear: both;">`
	`© Copyright 2010 SiteName`		`© Copyright 2010 SiteName`
	`</div>`		`</div>`

	`<!-- the developer dashboard can be turned on by administrators and shows debuging and performance info for the page -->`		`<!-- the developer dashboard can be turned on by administrators and shows debuging and performance info for the page -->`
	`<div id="DeveloperDashboard" class="ms-developerdashboard">`		`<div id="DeveloperDashboard" class="ms-developerdashboard">`
	`<SharePoint:DeveloperDashboard runat="server"/>`		`<SharePoint:DeveloperDashboard runat="server"/>`
	`</div>`		`</div>`

	`</div>`		`</div>`
			`</div>`
	`</div>`		`</div>`

	`<!-- ===== End scrolling body area with these two previous div's ============================================================ -->`		`<!-- ===== End scrolling body area with these two previous div's ============================================================ -->`

	`<!-- The form digest security control used to for security validation on forms -->`		`<!-- The form digest security control used to for security validation on forms -->`
	`<asp:ContentPlaceHolder id="PlaceHolderFormDigest" runat="server">`		`<asp:ContentPlaceHolder id="PlaceHolderFormDigest" runat="server">`
	`<SharePoint:FormDigest runat=server/>`		`<SharePoint:FormDigest runat="server"/>`
	`</asp:ContentPlaceHolder>`		`</asp:ContentPlaceHolder>`

	`<!-- ===== Hidden Placeholders ============================================================ -->`		`<!-- ===== Hidden Placeholders ============================================================ -->`
	`<asp:Panel visible="false" runat="server">`		`<asp:Panel visible="false" runat="server">`

			`<!-- Usually shows the tree view but do not remove because of issue with changing views in the ribbon in publishing sites -->`
			`<SharePoint:DelegateControl runat="server" ControlId="TreeViewAndDataSource"></SharePoint:DelegateControl>`

	`<!-- ===== These placeholders don't output anything very often OOTB ========== -->`		`<!-- ===== These placeholders don't output anything very often OOTB ========== -->`
	`<!-- The navigation menu that is inside the top navigation bar. -->`		`<!-- The navigation menu that is inside the top navigation bar. -->`
	`<asp:ContentPlaceHolder id="PlaceHolderHorizontalNav" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderHorizontalNav" runat="server"/>`
	`<!-- The top navigation where GlobalNavigationSiteMap is contained. Gets overridden by default. V4 uses it to change the top nav -->`		`<!-- The top navigation where GlobalNavigationSiteMap is contained. Gets overridden by default. V4 uses it to change the top nav -->`
	`<asp:ContentPlaceHolder id="PlaceHolderTopNavBar" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderTopNavBar" runat="server"/>`
	`<!-- The top of the Quick Launch menu. -->`		`<!-- The top of the Quick Launch menu. -->`
	`<asp:ContentPlaceHolder id="PlaceHolderQuickLaunchTop" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderQuickLaunchTop" runat="server"/>`
	`<!-- The bottom of the Quick Launch menu. -->`		`<!-- The bottom of the Quick Launch menu. -->`
	`<asp:ContentPlaceHolder id="PlaceHolderQuickLaunchBottom" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderQuickLaunchBottom" runat="server"/>`
	`<!-- The placement of the data source used to populate the left navigation bar. -->`		`<!-- The placement of the data source used to populate the left navigation bar. -->`
	`<asp:ContentPlaceHolder id="PlaceHolderLeftNavBarDataSource" runat="server" />`		`<asp:ContentPlaceHolder id="PlaceHolderLeftNavBarDataSource" runat="server" />`
	`<!-- The date picker used when a calendar is visible on the page. -->`		`<!-- The date picker used when a calendar is visible on the page. -->`
	`<asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat ="server" />`		`<asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat ="server" />`
	`<!-- The top section of the left navigation bar. -->`		`<!-- The top section of the left navigation bar. -->`
	`<asp:ContentPlaceHolder id="PlaceHolderLeftNavBarTop" runat="server" />`		`<asp:ContentPlaceHolder id="PlaceHolderLeftNavBarTop" runat="server" />`
	`<!-- used to override the global sitemap? -->`		`<!-- used to override the global sitemap? -->`
	`<asp:ContentPlaceHolder id="PlaceHolderGlobalNavigationSiteMap" runat="server" />`		`<asp:ContentPlaceHolder id="PlaceHolderGlobalNavigationSiteMap" runat="server" />`


	`<!-- ===== These placeholders does not appear as part of the 2010 UI but must be present for backward compatibility. ========== -->`		`<!-- ===== These placeholders does not appear as part of the 2010 UI but must be present for backward compatibility. ========== -->`
	`<!-- The name of the site where the current page resides. -->`		`<!-- The name of the site where the current page resides. -->`
	`<asp:ContentPlaceHolder id="PlaceHolderSiteName" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderSiteName" runat="server"/>`
	`<!-- Page icon in the upper-left area of the page -->`		`<!-- Page icon in the upper-left area of the page -->`
	`<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server"/>`		`<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server"/>`
	`<!-- Left border of the title area -->`		`<!-- Left border of the title area -->`
	`<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server"/>`		`<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server"/>`
	`<!-- mini console - supplementary buttons for pages like the wiki / history / incoming links -->`		`<!-- mini console - supplementary buttons for pages like the wiki / history / incoming links -->`
	`<asp:ContentPlaceHolder id="PlaceHolderMiniConsole" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderMiniConsole" runat="server"/>`
	`<!-- Right margin of the title area -->`		`<!-- Right margin of the title area -->`
	`<asp:ContentPlaceHolder id="PlaceHolderTitleRightMargin" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderTitleRightMargin" runat="server"/>`
	`<!-- Left border of the title area -->`		`<!-- Left border of the title area -->`
	`<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server"/>`		`<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server"/>`
	`<!-- The width of the left navigation area -->`		`<!-- The width of the left navigation area -->`
	`<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server"/>`		`<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server"/>`
	`<asp:ContentPlaceHolder id="PlaceHolderLeftNavBarBorder" runat="server"/>`		`<asp:ContentPlaceHolder id="PlaceHolderLeftNavBarBorder" runat="server"/>`
	`<!-- Border element for the main page body -->`		`<!-- Border element for the main page body -->`
	`<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server"/>`		`<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server"/>`
	`<!-- Right margin of the main page body -->`		`<!-- Right margin of the main page body -->`
	`<asp:ContentPlaceHolder id="PlaceHolderBodyRightMargin" runat="server" />`		`<asp:ContentPlaceHolder id="PlaceHolderBodyRightMargin" runat="server" />`

	`</asp:Panel>`		`</asp:Panel>`

	`<!-- Handle Search "enter" key and back button -->`		`<!-- Handle Search "enter" key and back button -->`
	`<input type="text" name="__spDummyText1" style="display:none;" size=1/>`		`<input type="text" name="__spDummyText1" style="display:none;" size="1"/>`
	`<input type="text" name="__spDummyText2" style="display:none;" size=1/>`		`<input type="text" name="__spDummyText2" style="display:none;" size="1"/>`

	`</form>`		`</form>`

	`<!-- extra form for some instances -->`		`<!-- extra form for some instances -->`
	`<asp:ContentPlaceHolder id="PlaceHolderUtilityContent" runat="server" />`		`<asp:ContentPlaceHolder id="PlaceHolderUtilityContent" runat="server" />`

	`<!-- warn users of old browsers that they need to upgrade -->`		`<!-- warn users of old browsers that they need to upgrade -->`
	`<SharePoint:WarnOnUnsupportedBrowsers runat="server"/>`		`<SharePoint:WarnOnUnsupportedBrowsers runat="server"/>`

	`<!-- Starter Master Page by Randy Drisgill (http://blog.drisgill.com) - Jan 27, 2009 -->`		`<!-- Starter Master Page by Randy Drisgill (http://blog.drisgill.com) - Oct. 7, 2010 -->`
	`<!-- Remove this credit if you want, but if you leave it in I will appreciate it! -->`		`<!-- Remove this credit if you want, but if you leave it in I will appreciate it! -->`
	`</body>`		`</body>`
	`</html>`		`</html>`

Updated Wiki: Home

drisgill — Fri, 08 Oct 2010 20:39:10 GMT

Starter Master Pages for SharePoint 2010 (Formerly known as Minimal Master Pages)
by Randy Drisgill - MVP SharePoint Server

Download Now

UPDATED VERSION RELEASED ON OCTOBER 8th 2010

Project Description
Starter Master Pages for SharePoint 2010 are a clean, commented starting point for creating your own SharePoint 2010 branding. Starter Master Pages were known previously as Minimal Master Pages in SharePoint 2007.

Project Details
In the tradition of those SharePoint branding folks that came before me, I have put together a few minimal master pages that can be used to start a SharePoint 2010 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2010 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Note: With SharePoint 2010, Microsoft has actually included their own master page called minimal.master which has a specific use for pages that will have very minimal chrome. Because of this, I am using the term Starter Master Page for my Master Pages instead of the term Minimal Master Page.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are three versions of my Starter Master Pages:
- _starter_publishing.master - Specifically for use with SharePoint Server 2010
- _starter_foundation.master - Specifically for use with SharePoint Foundation 2010
- _starter_meetingworkspace.master - Specifically for use with Meeting Workspaces in SharePoint 2010
These three versions are extremely similar. The primary difference being the navigation and corresponding data sources
The Starter Master Pages should work with MOST out of the box SharePoint 2010 pages including Application pages (like Site Settings), Lists and Documents, and some of My Site
- Search Center's in SharePoint use a special master page. See my post on the topic: http://blog.drisgill.com/2010/09/converting-custom-sharepoint-2010.html
Replace the word “SiteName” throughout the code with your project site’s name and directory
There are some minimal styles included and are commented accordingly.
All styles and images are loaded from the Style Library with simple “/Style Library/sitename” references. This helps with viewing them in Design View in SharePoint Designer 2010. Some deployment instances may require a more robust path usage (such as branding that is deployed to Site Collections that are not at the root web site). In these cases you can either place your styles and images in the 14 folder on the server (_layouts) or use the $SPUrl variable (more info here: http://msdn.microsoft.com/en-us/library/ee354190.aspx#odcsp2007RealWorldBrand_CreatingBrandinSP)
The SharePoint 2010 standard Ribbon controls are being used. This is the same code as in v4.master and NightAndDay.master only with the addition of some comments
The Starter Master Pages employ the standard SharePoint 2010 technique of forcing the Ribbon to “stick” to the top of the page. This is why the ribbon and main body areas are wrapped in specific div classes
There are several div’s throughout that have a class of “s4-notdlg”. This is the standard SharePoint 2010 method of hiding branding (like logos and navigation) from the SharePoint 2010 Dialog windows
I have tried to identify most of the ContentPlaceHolder’s that actually contain content in the out of the box SharePoint 2010 pages and included them in the displayable areas of the Starter Master Pages. All other unneeded (but required) ContentPlaceHolder’s are relegated to the hidden asp:Panel at the bottom of the master page.

Other optional things I have included because I think they are helpful (you can remove as needed):

Favicon code
JavaScript to address the ActiveX Name.DLL issue (See http://support.microsoft.com/default.aspx/kb/931509 for more info)
Class “s4-nosetwidth” is being used to allow for fixed width branding (See http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx for more info)
An area for a header logo that has a link back to the home (you can replace this with the site icon and title if you prefer. See lines 308-317 from v4.master)
A footer area for a copyright notice
The Developer Dashboard code (which is turned on from STSADM or Powershell).
WarnOnUnsupportedBrowsers is being used at the very bottom of the Starter Master Pages to alert IE6 users that the browsing experience is deprecated

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Tue, 25 May 2010 22:26:21 GMT

Starter Master Pages for SharePoint 2010 (Formerly known as Minimal Master Pages)
by Randy Drisgill - MVP SharePoint Server

Download Now

UPDATED VERSION RELEASED ON MARCH 7th 2010
You can still download the previous version from here:
http://startermasterpages.codeplex.com/releases/view/36075

Project Description
Starter Master Pages for SharePoint 2010 are a clean, commented starting point for creating your own SharePoint 2010 branding. Starter Master Pages were known previously as Minimal Master Pages in SharePoint 2007.

Project Details
In the tradition of those SharePoint branding folks that came before me, I have put together a few minimal master pages that can be used to start a SharePoint 2010 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2010 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Note: With SharePoint 2010, Microsoft has actually included their own master page called minimal.master which has a specific use for pages that will have very minimal chrome. Because of this, I am using the term Starter Master Page for my Master Pages instead of the term Minimal Master Page.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
They are currently considered a beta release
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are three versions of my Starter Master Pages:
- _starter.master - Specifically for use with SharePoint Server 2010
- _foundation_starter.master - Specifically for use with SharePoint Foundation 2010
- _meetingworkspace_starter.master - Specifically for use with Meeting Workspaces in SharePoint 2010
These three versions are extremely similar. The primary difference being the navigation and corresponding data sources
The Starter Master Pages should work with MOST out of the box SharePoint 2010 pages including Application pages (like Site Settings), Lists and Documents, and some of My Site
Replace the word “SiteName” throughout the code with your project site’s name and directory
There are some minimal styles included and are commented accordingly.
All styles and images are loaded from the Style Library with simple “/Style Library/sitename” references. This helps with viewing them in Design View in SharePoint Designer 2010. Some deployment instances may require a more robust path usage (such as branding that is deployed to Site Collections that are not at the root web site). In these cases you can either place your styles and images in the 14 folder on the server (_layouts) or use the $SPUrl variable (more info here: http://msdn.microsoft.com/en-us/library/ee354190.aspx#odcsp2007RealWorldBrand_CreatingBrandinSP)
The SharePoint 2010 standard Ribbon controls are being used. This is the same code as in v4.master and NightAndDay.master only with the addition of some comments
The Starter Master Pages employ the standard SharePoint 2010 technique of forcing the Ribbon to “stick” to the top of the page. This is why the ribbon and main body areas are wrapped in specific div classes
There are several div’s throughout that have a class of “s4-notdlg”. This is the standard SharePoint 2010 method of hiding branding (like logos and navigation) from the SharePoint 2010 Dialog windows
I have tried to identify most of the ContentPlaceHolder’s that actually contain content in the out of the box SharePoint 2010 pages and included them in the displayable areas of the Starter Master Pages. All other unneeded (but required) ContentPlaceHolder’s are relegated to the hidden asp:Panel at the bottom of the master page.

Other optional things I have included because I think they are helpful (you can remove as needed, the approximate line number in _starter.master is included):

Line 24 - Favicon code
Line 92 - JavaScript to address the ActiveX Name.DLL issue (See http://support.microsoft.com/default.aspx/kb/931509 for more info)
Line 388 - Class “s4-nosetwidth” is being used to allow for fixed width branding (See http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx for more info)
Line 393 - An area for a header logo that has a link back to the home (you can replace this with the site icon and title if you prefer. See lines 308-317 from v4.master)
Line 498 - A footer area for a copyright notice
Line 503 - The Developer Dashboard code (which is turned on from STSADM or Powershell).
Line 571 - WarnOnUnsupportedBrowsers is being used at the very bottom of the Starter Master Pages to alert IE6 users that the browsing experience is deprecated

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Sun, 07 Mar 2010 08:42:45 GMT

Starter Master Pages for SharePoint 2010 (Formerly known as Minimal Master Pages)
by Randy Drisgill - MVP SharePoint Server

Download Now

UPDATED VERSION RELEASED ON MARCH 7th 2010
You can still download the previous version from here:
http://startermasterpages.codeplex.com/releases/view/36075

Project Description
Starter Master Pages for SharePoint 2010 are a clean, commented starting point for creating your own SharePoint 2010 branding. Starter Master Pages were known previously as Minimal Master Pages in SharePoint 2007.

Project Details
In the tradition of those SharePoint branding folks that came before me, I have put together two minimal master pages that can be used to start a SharePoint 2010 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2010 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Note: With SharePoint 2010, Microsoft has actually included their own master page called minimal.master which has a specific use for pages that will have very minimal chrome. Because of this, I am using the term Starter Master Page for my Master Pages instead of the term Minimal Master Page.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
They are currently considered a beta release
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are three versions of my Starter Master Pages:
- _starter.master - Specifically for use with SharePoint Server 2010
- _foundation_starter.master - Specifically for use with SharePoint Foundation 2010
- _meetingworkspace_starter.master - Specifically for use with Meeting Workspaces in SharePoint 2010
These three versions are extremely similar. The primary difference being the navigation and corresponding data sources
The Starter Master Pages should work with MOST out of the box SharePoint 2010 pages including Application pages (like Site Settings), Lists and Documents, and some of My Site
Replace the word “SiteName” throughout the code with your project site’s name and directory
There are some minimal styles included and are commented accordingly.
All styles and images are loaded from the Style Library with simple “/Style Library/sitename” references. This helps with viewing them in Design View in SharePoint Designer 2010. Some deployment instances may require a more robust path usage (such as branding that is deployed to Site Collections that are not at the root web site). In these cases you can either place your styles and images in the 14 folder on the server (_layouts) or use the $SPUrl variable (more info here: http://msdn.microsoft.com/en-us/library/ee354190.aspx#odcsp2007RealWorldBrand_CreatingBrandinSP)
The SharePoint 2010 standard Ribbon controls are being used. This is the same code as in v4.master and NightAndDay.master only with the addition of some comments
The Starter Master Pages employ the standard SharePoint 2010 technique of forcing the Ribbon to “stick” to the top of the page. This is why the ribbon and main body areas are wrapped in specific div classes
There are several div’s throughout that have a class of “s4-notdlg”. This is the standard SharePoint 2010 method of hiding branding (like logos and navigation) from the SharePoint 2010 Dialog windows
I have tried to identify most of the ContentPlaceHolder’s that actually contain content in the out of the box SharePoint 2010 pages and included them in the displayable areas of the Starter Master Pages. All other unneeded (but required) ContentPlaceHolder’s are relegated to the hidden asp:Panel at the bottom of the master page.

Other optional things I have included because I think they are helpful (you can remove as needed, the approximate line number in _starter.master is included):

Line 24 - Favicon code
Line 92 - JavaScript to address the ActiveX Name.DLL issue (See http://support.microsoft.com/default.aspx/kb/931509 for more info)
Line 388 - Class “s4-nosetwidth” is being used to allow for fixed width branding (See http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx for more info)
Line 393 - An area for a header logo that has a link back to the home (you can replace this with the site icon and title if you prefer. See lines 308-317 from v4.master)
Line 498 - A footer area for a copyright notice
Line 503 - The Developer Dashboard code (which is turned on from STSADM or Powershell).
Line 571 - WarnOnUnsupportedBrowsers is being used at the very bottom of the Starter Master Pages to alert IE6 users that the browsing experience is deprecated

Starter Master Page Screenshot

Updated Wiki: Home

drisgill — Sun, 07 Mar 2010 08:42:35 GMT

Starter Master Pages for SharePoint 2010 (Formerly known as Minimal Master Pages)
by Randy Drisgill - MVP SharePoint Server

Download Now

UPDATED VERSION RELEASE ON MARCH 7th 2010
You can still download the previous version from here:
http://startermasterpages.codeplex.com/releases/view/36075

Project Description
Starter Master Pages for SharePoint 2010 are a clean, commented starting point for creating your own SharePoint 2010 branding. Starter Master Pages were known previously as Minimal Master Pages in SharePoint 2007.

Project Details
In the tradition of those SharePoint branding folks that came before me, I have put together two minimal master pages that can be used to start a SharePoint 2010 Branding project. They contain only very minimal HTML styling in order to accommodate some of the specific needs of SharePoint 2010 and are commented throughout. I hope you find them useful as a good starting point for creating branded SharePoint sites. If you make improvements upon them that could be used to improve the Starter Master Page experience for others, please share the changes with me through the CodePlex site or through my blog comments.

Note: With SharePoint 2010, Microsoft has actually included their own master page called minimal.master which has a specific use for pages that will have very minimal chrome. Because of this, I am using the term Starter Master Page for my Master Pages instead of the term Minimal Master Page.

Here are some notes about the Starter Master Pages (PLEASE READ BEFORE USING):

I am placing them on CodePlex and will be releasing updated versions as time goes on
They are currently considered a beta release
Please send feedback (here or on my blog, http://blog.drisgill.com) on problems or changes that you think would help everyone
Use at your own risk!
There are three versions of my Starter Master Pages:
- _starter.master - Specifically for use with SharePoint Server 2010
- _foundation_starter.master - Specifically for use with SharePoint Foundation 2010
- _meetingworkspace_starter.master - Specifically for use with Meeting Workspaces in SharePoint 2010
These three versions are extremely similar. The primary difference being the navigation and corresponding data sources
The Starter Master Pages should work with MOST out of the box SharePoint 2010 pages including Application pages (like Site Settings), Lists and Documents, and some of My Site
Replace the word “SiteName” throughout the code with your project site’s name and directory
There are some minimal styles included and are commented accordingly.
All styles and images are loaded from the Style Library with simple “/Style Library/sitename” references. This helps with viewing them in Design View in SharePoint Designer 2010. Some deployment instances may require a more robust path usage (such as branding that is deployed to Site Collections that are not at the root web site). In these cases you can either place your styles and images in the 14 folder on the server (_layouts) or use the $SPUrl variable (more info here: http://msdn.microsoft.com/en-us/library/ee354190.aspx#odcsp2007RealWorldBrand_CreatingBrandinSP)
The SharePoint 2010 standard Ribbon controls are being used. This is the same code as in v4.master and NightAndDay.master only with the addition of some comments
The Starter Master Pages employ the standard SharePoint 2010 technique of forcing the Ribbon to “stick” to the top of the page. This is why the ribbon and main body areas are wrapped in specific div classes
There are several div’s throughout that have a class of “s4-notdlg”. This is the standard SharePoint 2010 method of hiding branding (like logos and navigation) from the SharePoint 2010 Dialog windows
I have tried to identify most of the ContentPlaceHolder’s that actually contain content in the out of the box SharePoint 2010 pages and included them in the displayable areas of the Starter Master Pages. All other unneeded (but required) ContentPlaceHolder’s are relegated to the hidden asp:Panel at the bottom of the master page.

Other optional things I have included because I think they are helpful (you can remove as needed, the approximate line number in _starter.master is included):

Line 24 - Favicon code
Line 92 - JavaScript to address the ActiveX Name.DLL issue (See http://support.microsoft.com/default.aspx/kb/931509 for more info)
Line 388 - Class “s4-nosetwidth” is being used to allow for fixed width branding (See http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx for more info)
Line 393 - An area for a header logo that has a link back to the home (you can replace this with the site icon and title if you prefer. See lines 308-317 from v4.master)
Line 498 - A footer area for a copyright notice
Line 503 - The Developer Dashboard code (which is turned on from STSADM or Powershell).
Line 571 - WarnOnUnsupportedBrowsers is being used at the very bottom of the Starter Master Pages to alert IE6 users that the browsing experience is deprecated

Starter Master Page Screenshot