Skip to main content

SharePoint Branding Build Test Checklist

During the creation of the CSS, Master Pages, and Page layouts its critical to stay on top of your Front End Development testing.

As you know many classes in SharePoint are shared classes so when you make a modification to one element you have to test, test, test.

Below are some helpful things to review before giving that oh so critical demo… Hopefully these will help you out during your development process and testing.

  • Create and test all OOTB SharePoint templates
    1. Publishing Sites
      • Publishing Toolbar
      • Page Layouts (All that are available)
    2. My Sites
      • My Profile
        • Organization Hierarchy web part
        • In Common with you web part
    3. Team Sites
    4. Meeting Workspaces
    5. Blog
      • Unique Quick Launch
      • Post date, title, content, and links
    6. Wiki
      • Functional Links (Edit, History, Incoming Links)
      • Unique Quick Launch (Recent Changes)
      • Last Modified
    7. Search
      • People search drop down options
      • Search Results
      • Advanced Search Link
      • Advanced Search Page
    8. Central Administration
      • Don’t spend to much time on these
  • Test as many SharePoint functions as you can
    1. Fly Out Menu’s/Drop Downs
      • My Links
      • Top Navigation
      • Site Actions
      • Modify Web Part
      • Quick Launch if enabled
      • Multi Tier/level if enabled
      • Document Item Drop Down
    2. Button Hovers
      • Search/Go
      • Global Links (Top Links like My Links)
      • SPLink (Welcome & Console Toolbar Buttons)
      • Toolbar View Button
    3. Quick Launch
      • Headers
      • List Items
      • Selected headers/Items
      • Tree View
    4. Breadcrumbs
      • Text
      • Hyperlinks
      • Carrots “>”
    5. Toolbars
    6. Calendar
      • Date Picker
      • Month View
      • Week View
      • Day View
      • Current Day Indicators
    7. Lists/Libraries
      • Datasheet View
      • Alternating item shade (ms-alternating)
    8. Webpart
      • Chrome/Title
      • Border color/width if selected (ms-WPBorder)
      • Separator Lines
    9. Edit Page
      • Webpart Zone Colors
      • Drag and Drop Style
      • Webpart Chrome/Title’s
      • Advanced Webpart Gallery and Options
    10. Admin Pages
      • Site Settings
      • List Forms
        • Form Background (ms-authoringcontrols)
      • Upload Document
      • Error Pages
    11. OOTB Themes
      • If you are going to allow OOTB themes you will have to test, test, and triple test that all themes work and function as expected with your custom design…
    12. Fonts/Colors
      • Stick to system Fonts so that everyone gets the same experience. (Verdana, Tahoma, Arial, Etc)
      • Page Titles
      • Body Content
      • Hyperlinks
      • Hover Text
      • Visited State
    13. Images
      • Teamsite Default Image
      • Social Meeting Workspace Image
    14. Customization/3rd Party
      • Its kinda a given but any custom web parts, 3rd Party or custom controls implemented will need to have branding applied or tested before deployment onto prod servers.

I’m sure there are some that I missed but drop me a comment if you have some that I missed and I will add to the list above.


Anonymous said…
Hi! Your blog is simply super. you have create a differentiate. Thanks for the sharing this
website. it is very useful professional knowledge. Great idea you know about company background.
Customized application development
Robert Dornbush said…
You are a great teacher, You always leave your audience wanting more!...,

By the way, the symbol for 'GO' or expand menu, etc. ">" is correctly spelled 'Caret' (also word for blinking cursor where text is inserted).
Anonymous said…
I am a complete newbie when it comes to branding in sharepoint. your site has ( and will be )been a friggin AWESOME resource - Albert Vargas
When are you launching your book. Looking forward to buy two copies, one to read and other to eat or let again :) Sunil

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…

Small Calendar for SharePoint 2010 & 2013

First off I would like to apologize for the lack of posts. I have been really busy with my new role as the UX Design lead within Slalom Consulting Boston. I will share more about that in another post. In a previous post Create Really Small Calendar I showcased how to do this for SharePoint 2007. However the 2010 and 2013 calendar views have changed and therefore we cannot use the same method or CSS as 2007.SharePoint 2010 Small Calendar:
SharePoint 2013 Small Calendar:
See video below for a video walk through on how to create a small calendar for SharePoint 2010 and & SharePoint 2013 with just CSS.Per the video above here is the code that I referenced:2010 CSS link reference in Master Page:
<SharePoint:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/smallcalendar.css %>" After="corev4.css" runat="server"/>2010 CSS:
/**** Small Calendar ***/
.ms-acal-item{height: 10px !important;}