Home » SharePoint 2013 » Planning a Toolset for Branding Projects for SharePoint 2013

Planning a Toolset for Branding Projects for SharePoint 2013

A toolset for branding sites in SharePoint Server 2013 should include components for developing custom branding along with components useful for repairing problems arising in the branding process. Yaroslav Pentsarskyy, a subject matter expert on branding and a published author on the topics has produced a video tutorial on this topic, which any subscriber to SharePoint-Videos.com can view. This video tutorial is also available in a set of video tutorials on branding SharePoint Server 2013 sites, SP13-301 SharePoint 2013: Branding Video Training Package. The video is titled Tools you’ll need for branding.

The remediation requirement can be accomplished with popular web browsers, specifically with source code viewers capable of selectively displaying style-specific information only. For Internet Explorer 8, 9, and 10 and Firefox the viewers are accessed with the F12 function key. For Google Chrome, a combination keystroke of Ctrl + I calls the developers tools. These Chrome tools include additional functionality over and above style requirement, so it makes sense to gain familiarity with the range of capabilities of the Chrome tools prior to using it.

For the Firefox browser, this specialized source code viewer is the Firebug plug in. Internet Explorer 8, 9, and 10 incorporate “F12 Developer Tools”, also accessibility from the “Tools” menu for the browser.

In Yaroslav’s video, he demonstrates how to use any of these browser tools to preview color changes, and even to identify problem style features and fix them, on the fly. Pleae note: any fixes accomplished with any of these browser tools will need to be recorded. The fix actually changes the page as viewed in a specific browser and does not change the actual page coding. So plan on working out the fix with the original source code after identifying problems with the browser.

Any development requirements should be handled either with SharePoint Designer 2013, or with Visual Studio 2013. Our tutorial maps where it makes sense to use SharePoint Designer 2013 and where it makes sense to use Visual Studio 2013. Bottom line: for public and/or larger sites any development requirements should be handled strictly with Visual Studio 2013.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved