Branding Office SharePoint Server 2007 Web Content Management solutions reaches beyond development and is done in most scenarios by webdesigners. Once done the templates are being sliced into pieces and incorporated in SharePoint. To simplify the work, SharePoint community has created a Minimal Master Page: a template which contains all the elements required by SharePoint. Just recently I have noticed that using that template for branding is rather harmful and can lead to even more problems instead of sparing you the time.
Designing for the Web and developing are two different disciplines.
Designing for the Web and developing are two different disciplines. Designing requires different skills and experience and is therefore done in most scenarios by a different group of people than SharePoint developers. Because devigners (people who can both develop and design) are very rare, in most scenarios you – SharePoint developer will have to do it with designers who will provide you with the templates for the WCM solution.
I’ve been working with SharePoint for almost two years now. What I noticed is that many SharePoint developers know very little about webdesign and accessibility. While they know really a lot about SharePoint and all the others server-side technologies, they have little to none understanding of how the Web, CSS and HTML really work. It’s not that bad while developing a web application but if you are working on a serious Web Content Management solution, you are in trouble.
As soon as you paste the pieces of HTML into Master Page and Page Layouts it seems like SharePoint is changing the way the things are rendered
In the last two years I have met quite a few developers who were complaining about how difficult it is to get the branding working in SharePoint. As soon as you paste the pieces of HTML into Master Page and Page Layouts it seems like SharePoint is changing the way the things are rendered. Not surprisingly all of them were using the Minimal Master Page to speed up the branding process and just to be sure that they’ve got all the controls required by SharePoint. So what is actually wrong with the Minimal Master Page?
Mind the doctype!
Next to all the controls and placeholders required by SharePoint the Minimal Master Page contains the doctype. What many developers don’t know is that the browser renders the page using the doctype information. What it means is, that if you take design created using the XHTML 1.0 Strict doctype and embed it in SharePoint using the XHTML 1.0 Transitional doctype, there is a chance that the layout will break. Eric Meyer has covered all the different issues in his article Picking a Rendering Mode.
Changing the doctype afterwards might lead to most weird rendering errors which debugging might costs you hours
Because the Minimal Master Page already contains a doctype, many developers think that this is the way the thing must be. They proceed directly to embedding all the other elements missing in the Minimal Master Page, forgetting to copy the doctype declaration as provided in the templates. Changing the doctype afterwards might lead to most weird rendering errors which debugging might costs you hours.
Using the Minimal Master Page is not wrong – not at all. Since I started working with SharePoint, I have created my own Minimal Master Page. Because it’s a template, it saves you lots of time and allows you to focus on the solution-specific work. What you should remember is to always copy the doctype from the templates you received from the designers. In many situations it will save you a lot of frustration and debugging.