2. • SharePoint Page Types
Master Pages
Application Pages
Site Pages
• Application Pages
• Site Pages
3. • WSS 3.0 is built on top of ASP.NET 2.0, it supports
master pages
• Benefits of Master Pages
A better editing experience
Web-level editing
User interface reuse
More consistent pages and a better end-user
experience
4. • Central file controlling the layout and the design of
the content pages in a SharePoint site
Title, logo, and
description of site
Navigation controls
Welcome and
administration
Search experience
Linking cascading
style sheet files and script
files
Web part manager
ContentPlaceHolder controls
5. • Template files
Default.master in Global site definition
Custom master pages via Features
• Master Pages are customized when using SharePoint
Designer 2007
• Master Page Gallery
One per site collection
Resides at the root of
the site collection
6. • Application pages (layouts pages) are stored in the
virtual directory for SharePoint web application
url: http://myserver/_layouts/mysite.aspx
Or http://myserver/_layouts/a/b/c/_layouts/mysite.aspx
• By default, _layouts folder:
C:program filescommon filesmicrosoft sharedweb
server extensions12TEMPLATElayouts
• Application Pages are always compiled into a single
DLL
• Application Pages are allowed to have in-line code
• Application Pages do not support customization
9. • Site Pages (Content Pages) can be modified by end
users by using tools such as SharePoint Designer 2007
• Site Page are stored logically within SharePoint sites,
most of the files are stored in content database
10.
11.
12. • How to create your own page templates
<%@ Page MasterPageFile="~masterurl/default.master"
meta:progid="SharePoint.WebPartPage.Document" %>
<asp:Content runat="server" ContentPlaceHolderID="PlaceHolderMain“>
<h3>Page 1 - Hello World</h3>
A simple page template used to create site pages
</asp:Content>
13. • Customized site pages are parsed and processed in a
special mode known as safe mode
• In-line script runs fine in uncustomized pages
• When a user modifies the page, WSS refuses to process
it in safe mode and generates an error
15. • Safe mode allows the farm administrator to determine
which controls can be used in pages that are processed
in safe mode
• Customized pages can only contain server-side
controls that are explicitly registered as safe controls
<SafeControls>
<SafeControl Assembly="Microsoft.SharePoint, …"
Namespace="Microsoft.SharePoint.WebControls" TypeName="*"
AllowRemoteDesigner="True" />
</SafeControls>
17. • Page Templates
Page template files are stored on disk, not in the
content database
SharePoint provisions a page from a page template,
system creates a pointer to the instance of the page
template (not customized pages or ghost pages)
After a page customized (modified) pages, the pointer
is voided and the page is stored in the content database
• Using server side code on Site Pages
If the page is not customized, server side code is
supported
if the page is customized, server side code does not
execute on the page, and the page does not render
18. • Browser
No special skills required
Site admin users browser UI to make choices
• SharePoint Designer
Moderate skills required (web designer)
Client/server app fully supports remote editing
Can only edit pages in content DB
Easy to create site template (*.stp) in browser
• Site definition
Moderate to advanced skills required
Have to be on server machine
Can include files customized by Designer (.master, .css)
19. 1. Web site construction
• Page layout and design
• Master Page creation
• CSS stylesheet edit/apply
• List/Content Type Design
• Creation of sample data
• Web Part page creation
• Web Part hookup
• No-code data views & forms
• No-code workflows
Tool: SharePoint Designer + Browser
2. Custom Coding (if necessary)
• Web Controls
• Web Parts
• ASP.NET page coding
• Workflow actions
• Event handlers
Tool: SharePoint Designer + Browser
3. Finalization
• Create Site Definition (wsp)
from working site
Tool: future VS add-in
4. Deployment
• Box admin installs new app
template using WSP on
production server
