Skip to main content

Renaming SharePoint Master Page Classes

Simply said, "Just because you can, doesn't mean you should".

I have noticed that I am saying this phrase to myself more often than not with SharePoint. When it comes to SharePoint Branding you/client/developers have allot of choices to make. Its never as easy as you think.

I find myself going down the rat hole of making it overly complicated not because I don't know what I am doing, but because I know I have the power to do so.

Within SharePoint master pages you have the ability to change the default class names. For example if I wanted to change the class name within a custom master page for the quick launch
(ms-quicklaunch) to your own custom class (xyz-quicklaunch) its very easy to do in the master page. However you might be getting yourself into allot of headaches because with out really thinking about it you might have totally screwed yourself... Since you now have stripped that main class out of the page all of the default references to ms-quicklaunch will have to be added to your custom style sheet even though you might not be changing 1 single attribute for that class...

Classes that have a parent child relationship depend on some of those default classes. In the default core.css file you might have the following Example:

ms-quicklaunch .ms-navitem{
padding: 10px;

So in the example above this class is saying that all ms-quicklaunch classes that have ms-navitem in it will get padding of 10 pixels. if you do not reference all of those one off classes, you might find your design getting a little bit funky. This is especially true with font sizes, margins, and padding.

Therefore here is my conclusion:

If you are going to be creating a brand from scratch and removing all references to the OOTB style sheets, go ahead and rename those classes. But if you are going to keep the OOTB style sheet reference save your self the headache and keep the class names but put all of your override styles in a alternate style sheet.


Popular posts from this blog

How To: Hide Left Side Navigation on Home Page

I was recently asked: "How can I hide the side nav bar on the main homepage layout ?? I want to be able to use the side NAV with in the team site etc etc, but I don't want it on the front page.. " There are a couple of ways to do this in SharePoint 2010. If you are using a non-publishing site you can add a Content Editor Web Part to the page and add the following to the HTML Source.
body #s4-leftpanel
display: none;
margin-left: 0px;
Basically the CSS above hides the left navigation Div, and then sets the content area to not have a left margin. Once you are done, simply modify the web part and hide it on the page. If you are using a publishing site for your homepage simply add the same styles specified above to a custom page layout. That way if you have a need for other pages that do not need the left side navigation you can re-use the page layout.

SharePoint 2010 Base CSS Classes

This will be the first of many SharePoint 2010 posts. I will be focusing on a few of the main CSS classes used for SharePoint 2010 Public Beta. As the product becomes more final there might be some changes to the class names but I will be sure to create a new post if that happens. This will be quite a lengthy but it should be helpful. The default CSS given below are just highlights of the full CSS attributes for that class.I will be using a basic team site as my base for the screenshots. Here is a basic structure of the main areas that I will cover.Ribbon RowTable Row Left Site Actions Navigate Up Edit Tab List Browse Page Table Row Right Give Feedback Welcome Menu WorkspaceBody Container Title Row Title Title Logo Title Text / BreadcrumbPage DescriptionSocial Data SeparatorI like It Tags/Notes Top Header 2/Top Links li Static-Selected li Static SearchHelpStatus Bar Container Main A…

SharePoint 2010 Content Query for Blog Posts

I hope this post will help many of you feel comfortable with using the Content Query Web Part.In this post I will walk you through the process of creating a content query web part and configuring it to show custom field types. I will also give details on how to use XSLT to stylize and format the data being pulled. I will be using the following scenario as an example. Say that you had a site collection with a top level publishing site. This publishing site would display a the most recent blog posts from all blog sites within its own site collection. To solve this problem we will use a Content Query Web Part and a customized ItemStyle.xsl using XSLT.Please note that the “SharePoint Server Publishing Infrastructure” needs to be enabled at the site collection to display the content query web part.Step 1: Add a Content Query Web Part to PageNavigate to the site that you want the blog posts to show up and click on edit page. Under Editing Tools in the Ribbon, Click on insert > Web PartUn…