branding sharepoint sites why is it so hard? · 2010-01-19 · if theme changes in sharepoint root,...
TRANSCRIPT
Branding SharePoint Sites
Why is it so hard?
Penelope Coventry
About the Speaker….
Penelope Coventry, MVP,
Principal Consultant PPP Consulting Ltd
www.sharepointdesignerstepbystep.com
Twitter: @pjcov
Email: [email protected]
Independent Consultant, Author: SharePoint Designer Step by Step, Windows SharePoint Services Step by Step, SharePoint Server 2007 Administrator’s Companion
Who are you?
Web Designers…
Web Developers…
Business Managers…
IT/Admin…
SharePoint Basics
4
Two Types of Sites
Two Types of Content Pages
Types of Master Pages
Themes
Types of Sites
SharePoint Server 2007 Provides Two Type of Sites
Internet Sites
Collaboration
Sites
Small
Number of
People
Large
Number of
People
Types of SitesPublishing Sites
Shop Fronts
Large Number of Readers
Small number of content authors
Page content Approval Process
Resources, such as Images preloaded
Branding / Look and Feel Very Important
Internet / Intranet Web Sites
Collaboration Sites
Factories – team sites
Small number of Readers
Large number of people
who contribute content
Page Content goes live
immediately
Master Page and Page Rendering
Master Pages
New in this version of SharePoint
All SharePoint Content Pages associated with one Master Page
Can be changed post Site Creation
Provides constant Look-Feel across number of pages Themes plus more!
Common page elementsHeader, Navigation, Footer, Site Actions button, Search box
Unique Items for Your SiteContact Us, About Us, Advertisements, FAQs
Site Wrapper HTML, CSS and JavaScript
Content PlaceHoldersMatch areas on Content Pages where
you can enter Information
Types of Master Pages
Default Master Pages
Used by All Types of Sites
Known in the Browser as Site Master Pages
Custom Master Pages
Used only by Publishing Pages
Known in the Browser as System Master Pages
Application Master Page
Used by administration Pages, i.e., Pages in the _layouts directory
Master Page Inheritance
Browser Branding Options
Navigation
Themes
Master Pages
CSS Style Sheets
Switching Page Layouts
Web Parts
Content Query Web Part (CQWP)
Content Editor Web Part (CEWP)
Themes Change a Site’s Theme - Browser CSS and Images
Copied from SharePoint Root into Content Database under the _themes directory in the site Every site gets there own copy of the files
If Theme changes in SharePoint Root, sites already using the Theme does not see changes, as they’re referring to the theme files in the content database
When Theme changed back to default theme, theme files in content database deleted
Choice of Approximately 18 out-of-the-box Themes
You can create your own Custom Theme Files On Web Server (deployed as solution – change control)
Seen by All Sites Changes the CSS properties for the Site – including the
administration pages (_layouts)
Does NOT change CSS Files across ALL Sites
Browser v SPD
Use Browser and SPD to Prototype Branding
Use SPD for things you can’t do using the Browser
Use SPD to brand when the scope of customisation never need to go beyond single Site Collection.
SPD is not to be used for everyone – Need Training
Never Alter the Files in the SharePoint Root (12 Hive) with SPD – in fact never install SPD on your SharePoint Servers
Make sure that all SharePoint Root customizations are in source control in a way that requires Developers to use it –then get them to produce solution file (wsp) and implemented thro’ Change Control.