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.

Comments

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 say....read again :) Sunil

Popular posts from this blog

How To: Create Hyperlink to Modal Pop-Up Form

I was asked by a client recently if there was a way to create a hyperlink to a New Item Form anywhere within a site but still get the rich experience of the Modal pop-up window that grays out the background. (Note this is for SharePoint 2010 Only…) I basically took the code directly from the “Add new item” and the “Add Document” link within the list view. What this allows you to do is simply add in the following code to any content editor web part, Master page, or Page Layout in any site collection and display the form to be filled out. The user will get the nice experience of the modal window and not have to navigate away from their current page. This could be used for example a feedback form that is included in the master page so whenever someone wants to give feedback it is always going back to a central list. The only that is required for you to know is the List ID and the site name. Full Code For a List Item: <a onclick="javascript:NewItem2(event, &quot

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 Row Table Row Left Site Actions Navigate Up Edit Tab List Browse Page Table Row Right Give Feedback Welcome Menu Workspace Body Container Title Row Title

SharePoint 2013 Responsive Table Columns

I have been wanting to write this one for a while now. It is really amazing how UX is really finding is way into everything that we use and interact with. From Custom applications both mobile and on a desktop to document management or large data visualizations. There is always room for better usability and new concepts. SharePoint lists and library functionality really has not changed much for the past 10 years... I remember back in 2003 when I saw the same table/grid based views of documents and list items that exists in SharePoint 2013. But now we can look at them in a whole new way! In this video blog you will see how to create a responsive CSS table so that when the browser size is reduced it will hide specific columns. However hiding data is not always the right thing to do. What if a user needed those columns to filter on or to use for comparison to another document? Well that is where the custom jQuery Column chooser comes in. It allows you to see what columns are displ