Developing Master Pages with SharePoint Designer

1
Developing Master Pages with SharePoint Designer

• Jason Noble
• Practice Manager
• Neudesic

• OFC323

2
Agenda

• Considerations for Master Page design
• Defining the User Experience
• Building Your Master Page
• Deploying Master Pages
• Master Pages and Page Layouts
• Goals
• Provide a reusable process for creating master
  pages for SharePoint
• Provide clarity in exactly what to do in various
  scenarios
• Provide insight into gotchas and best practices

3
Master Page Review
4
Master Page Development Life Cycle
Follow a structured process for success

• ? Identify site features
• ? Create wire frames
• ? Apply visual design
• ? Build a skeleton page
• ? Weave in content place holders and controls
• ? Features, Modules, and Solutions

5
Identify Site Features

• Apply a user centric approach
• Personas
• Scenarios
• Wireframes
• 3 scenarios for SharePoint sites
• Collaboration Portals Team Sites
• Web Content Management Systems - Internet
• Collaboration Portal with WCM Hybrid

Partners
Hybrid
Employees
Team Sites
6
Universal Capabilities

• Consider the following universal capabilities
• ? Top Navigation
• ? Left Navigation
• ? Breadcrumbs
• ? Search

7
Collaboration Portals
Identify Site Features

• SharePoint Features
• ? Document Libraries
• ? Out-of-box and custom Lists
• ? Wikis
• ? Web Part Pages
• ? Calendaring
• ? Document Workspaces
• ? Meeting Workspaces
• ? Data Sheet Views

8
Collaboration Portals
Further considerations Identify Site Features

• Users will need to Sign-In
• Users will need access to the My Site, My Links
  and other items found in the global navigation
• Administrators will need access to the Site
  Actions capabilities
• Because of the flexibility of List Views using a
  fixed width is not recommended
• Any system capabilities that reference pages in
  the _layouts directory will use a different
  master page
• Upload document

9
WCM Web Presence
Identify site features

• SharePoint Features
• ? SharePoint Lists and List Views be used, and if
  so, will they be customizable
• ? Will Calendaring be used
• ? Will Wikis be used
• ? Site Actions
• ? Content Editing Console

• ? Required
• ? Optional

10
WCM Web Presence
Further considerations Identify Site Features

• Aesthetics and user experience are key
• Global features sure as My Site, My Links and
  other SharePoint features are not required
• Sign-In is optional
• Multi-browser support

11
Collaboration Portal with WCM
Site Features

• ? Documents Lists
• ? Sign-In
• ? Global Navigation
• ? Wikis
• ? Calendaring
• ? Documents Lists

• ? Required
• ? Optional

12
Master Page Development Life Cycle
Follow a structured process for success

• ? Identify site feature
• ? Create wire frames
• ? Apply visual design
• ? Build a skeleton page
• ? Weave in content place holders and controls

13
Create Wire Frames
Map the features

• Based on the SharePoint features map each to
  screen regions

14
Collaboration Portal
Wire Frames
15
Web Content Management
Wire Frames
16
Master Page Development Life Cycle
Follow a structured process for success

• ? Identify site feature
• ? Create wire frames
• ? Apply visual design
• ? Build a skeleton page
• ? Weave in content place holders and controls

17
Master Page Development

• Skeleton page, minimal.master, content regions

• DEMONSTRATION

18
Master Pages, Page Layouts, and Page Content
19
Features, Modules, Solutions

• Always use Features and Solutions when deploying
• Do not get into the habit of directly changing
  production using SPD

20
Features

• Deployable Units of Capability
• Can be changed together in Site Definitions
• Provide extreme flexibility

21
Feature.xml

• ltFeature Id"ED91C0CF8553466895CFEF5D9B79E3FF"
• TitleBudget Tracker Master Pages"
• DescriptionBudget Tracker Master
  Pages"
• Hidden"FALSE"
• Version"12.0.0.0"
• Scope"Web
• xmlns"http//schemas.microsoft.com/sharepoint/"gt
• ltElementManifestsgt
• ltElementManifest
• Location"MasterPages\MasterPages.xml"/gt
• lt/ElementManifestsgt
• lt/Featuregt

22
MasterPages.xml

• ltElements xmlns"http//schemas.microsoft.com/shar
  epoint/"gt
• ltModule
• Name"DefaultMasterPage"
• Url"_catalogs/masterpage"
• Path"MasterPages gt
• ltFile
• Urlbudget.master
• Type"GhostableInLibrary/gt
• lt/Modulegt
• lt/Elementsgt

23
ONET.XML

• ltConfiguration ID"2" Name"WorkCenter"
  MasterUrl"_catalogs/masterpage/budget.master"gt
• ltWebFeaturesgt
• lt! Budget Tracker Master Page--gt
• ltFeature ID"ED91C0CF8553466895CFEF5D9B79E3FF" /gt
• lt/WebFeaturesgt

24
Summary

• Master Page Development
• Follow a predictable process
• Include User Experience
• Use a minimal.master to ensure functionality
• Use SharePoint Designer for development
• Deploy to Production with Features
• KB 944105

Jason Noble jason.noble_at_neudesic.com www.neudesic.
com 949.754.4500
25
Thank you.