What is branding? Branding is how you apply an organization's identity to an existing software application through customization of a portal site.
With the portal site home page becoming the primary interface between employees, customers and their Web, you should assure that it reflects and reinforces the organization's identity. Portal site users should understand intuitively that they are using an enterprise resource. Users should feel that they are interacting with the organization's portal site rather than a standard software application.
Your organization’s Web site represents your organization just as officially as your Annual Report. A number of organizations have made significant investments in the development of standards to guide the creation of their Web sites. These standards include logos and images, colors, fonts, page layouts, and navigational models. Because a portal site is at the center of an organization's intranet, it must adopt such standards. Standards should promote a common look and feel throughout the organization's Webs to make it easier for users to navigate and find the information they need to do their jobs.
A corporate intranet and Internet site is commonly made up of many different sites, created by diverse parts of the organization using a variety of tools. Any branding effort must ensure the greatest possible consistency with existing sites. You should always place higher priority on usability than on look and feel. A solution's look and feel refers to the visual, attractive elements of its interface; usability, however, is about making it easy for end users to interact with and use the interface.
Corporate intranets and Internets can be made up of many loosely connected sites, so any branding effort should communicate a clear "sense of place" to your users so they can understand where they are within the portal site quickly. Common approaches to solving this problem include elements such as breadcrumbs, navigation tress, and page titles.
Branding of a portal site is the application of an organization's identity to an existing software application through customization of the portal site. It is an important requirement for any portal implementation and it has a significant impact on the end user experience. You typically brand a portal site to meet your organization's intranet and Internet standards and guidelines. By definition no two implementations are the same, making it important to understand both the capabilities of the chosen portal platform and the specific organization requirements.
Following are some common branding requirements (or standards) described by organizations in their intranet and Internet design guidelines.
Applying color and style are the most fundamental elements of branding. You should consider any organization requirements in this area to be essential and probably governed by very strict guidelines. Apply these elements of a brand completely and consistently throughout any solution.
The most common branding requirement is developing a page "banner," also known as a "brand-box" or page "header." This element is common to all pages and most organizations will already have a design in place.
Organizations have various requirements for site navigation, typically including one or more horizontal and vertical menus. The location of these menus varies; in particular, you can place the horizontal menu along the very top of the page or immediately below the banner. Menu style also varies; some organizations prefer a "fly out" style, others a collapsible style, and still others their own custom design.
Organizations often have one or more standard screen layouts. These are page designs that define where to position elements such as navigation, banner, footer, and body on a page. You must accommodate any number of these page designs within the portal site design, promoting consistency throughout the intranet and in turn making it easier for people to use.
Different organizations refer to certain product features in different ways. For example, some customers refer to items added to the portal site as "News," while others prefer to call these items "Announcements." Accommodating these vocabularies can have a significant impact on overall ease of use. In addition, some organizations want to emphasize some product features over others, making some more obvious or discoverable. These same features may not be relevant to other organizations who may want to hide them altogether. Finally, you must take care to ensure full support for accessibility standards, screen resolutions, and different types of browser.
Imagine that you have a fictional Web site called foo.com and this is Welcome page for the site.
The Welcome page for the site has been requested by the user.
The table at the bottom of the slide represents the Web page and its content, for example Title or Image. In SharePoint this page is represented as an item in a SharePoint library with a content type that defines what fields are available in the page.
When the request comes in to Welcome.aspx the page has a column defining the view. While the page defines the content it does not own the presentation of the content. For presentation the page must look up its associated page layout. The page layout is another server side .aspx that lives in the database and it defines the view or presentation of the content, for example where the title goes or where the image goes. The Page layout executes controls that render the title, the body, the description from page fields in the page item.
The Page layout doesn’t fully own presentation of content. It must also use a Master Page that defines the common shared look and feel across the site, for example the logo and the positioning of the logo or the presence and position of the search box at the top. Any element that appears across your site will be stored in the Master Page which is also a server side .aspx in the database.
One of the important points in this page rendering process is that data is separate from view. This enables you to make changes easily across your sites.
For example, what if you have a site with 1000 article pages and Corporate Communications decides to replace the image or to change the placement of the image from left to right? You only need to update one page layout and the required change will be reflected in all 1000 article pages. Or what if Corporate Communications decides to update the look of your logo and to change the corporate colors? Again all you need to do is make these changes on the Master Page and these changes will be reflected throughout your site.
The second important point is that since these pages are part of a SharePoint library they inherit all the SharePoint library features. The page model takes advantage of all underlying SharePoint support capabilities, including versioning, check-in and check-out, and workflows.
Let’s do a quick review of what it means to have a Web site using this page model.
l Sites are a collection of Webs
Ø The Webs are arranged in a hierarchy
Ø Hierarchy controls navigation and security
l Each Web has a document library for Pages
l Page Layouts, Master Pages are stored in the root Web Master Page Gallery
l CSS files stored in the root Web Style Library
In the previous module we learned how the site structure is a hierarchy of SharePoint Webs. We also learned that Webs are container objects that can contain libraries or other Webs and that each Web has a library called pages where the page items mentioned in the previous slide are stored. This represents the content of the site but what about the presentation?
All the elements that define how the content of your site will appear are stored in the root Web highlighted here in blue. These elements include Page Layouts, Master Pages, and CSS stylesheets which we’ll look at in greater detail in this module. These elements are stored in a Master Page Gallery which is a document library in the root site of the site collection and are shared across the Web site. The Master Page Gallery stores all the chrome master and page layouts used to control branding and authoring. This document library supports views, versioning, check in, check out, and workflows as does any other SharePoint list.
Together, this hierarchy of Webs with their libraries and the items in their libraries using the common SharePoint elements define the Web site and its Web pages.
Office SharePoint Server 2007 enables branding by separating content from display through the use of Master Pages, Pages Layouts and CSS styles. Branding is controlled in one place and applied top-down in your Web site and you can restrict authors to create pages that comply with your branding through the use of Page Layouts and control restrictions.
Master pages provide the look and feel and standard behavior that you want for all of the pages in your site. Page layouts contain field controls that allow content to be edited and rendered for display. They also reference a master page and host field controls that bind to fields on the master page list item. Together with content pages, they produce output that combines the layout of the master page with content from the content page.
Because Windows SharePoint Services is built on top of Microsoft ASP.NET 2.0, it supports master pages for defining elements that are common to all pages. You can specify all of the shared elements of your site in the master page or pages, and add content page-specific elements to content pages. Using master pages gives you a single-location ability for change. You can make design changes in one place and propagate the changes to all pages that use the master page.
CSS styles can be used to define and change the look and feel of items on the page.
l SharePoint separates content from display
l Master Pages provide the look and feel
Ø ASP.NET 2.0 Master Pages control look and feel of the Web site
l Page Layouts provide the template for rendering
Ø Reference a master page for global navigation and chrome
l CSS styles
Ø Alternate CSS setting allows for CSS overrides independent of master page used
Remember that in the page rendering process we looked at earlier, the Page layout executes controls that render the title, the body, the description from page fields in the page item, but the Page layout doesn’t full own the presentation of content. The Page Layout must also use a Master Page that defines the common shared look and feel across the site. We mentioned Master Pages earlier in the day and used some of the functionality of Master Pages especially in the Navigation module. Now we’re going to cover Master pages in greater depth, and we’ll look at the Page Layout template later in this module.
Master pages are a feature of ASP.NET 2.0. When a user requests a content page, it is merged with a master page to produce output that combines the layout of the master page with the content from the content page. All content pages share the same page structure—the global breadcrumb, site title area, top navigation, page title area, and left navigation bar. This shared page structure is contained in the master page called default.master, which is used by all content pages.
In addition to static text and controls that appear on all pages, a master page also includes one or more System.Web.UI.WebControls.ContentPlaceHolder controls, which define regions where replaceable content can appear. In turn, the replaceable content is defined in content pages.
Imagine, for example, that you want every page in an application to use the same layout along with a standard header and navigation menu. In that case, you can create one Master Page with the desired layout and base all the pages in the application on the Master Page. By creating a single Master Page, you avoid performing the work of duplicating the common content for each page. Also, if you decide to change the layout of all the pages in the future, you need to modify only the single Master Page.
You create a Master Page by creating a page with a .master extension. A Master Page can contain almost anything that you can include in a normal ASP.NET page. What makes a Master Page special is the fact that it can contain one or more <asp:ContentPlaceHolder> controls. The <asp:ContentPlaceHolder> controls indicate regions of replaceable content in the Master Page.
You can base any ASP.NET page on a master page template simply by adding a directive to the page (for example: <%@ Page Master=”SiteLayout.Master” %>). The ASP.NET page can then optionally override any of the <asp:ContentPlaceHolder> regions declared within the Master Page. At runtime a single merged page will then be sent down to calling browser clients.
There are supported scenarios for customizing master pages:
· How to: Create a Minimal Master Page - http://msdn2.microsoft.com/en-us/library/aa660698.aspx
· Page Layouts and Master Pages: http://msdn2.microsoft.com/en-us/library/ms543497.aspx
When a new site is created, it uses the default master page that is located in the file system. If a master page is customized using Office SharePoint Designer, Windows SharePoint Services stores a modified version of the master page in the content database.
l Page layouts provide the template for rendering
Ø Can have many layouts per content type
l Define what can be authored in the page:
Ø Field controls
Ø Web Parts
Ø Web Part zones
l Define how much control the author has over page content’s look and feel
Ø Turning on restrictions on field controls
Ø Wrapping controls in CSS classes
As we said earlier the Page Layout selected for a content page calls the appropriate Master Page. Now we will discuss the Page Layout in greater detail.
A page layout is a template that is used in conjunction with a master page to control the look, feel, and content of a page. Each page layout has an associated content type that determines the kind of content that can be stored on pages based on that page layout. Microsoft Office SharePoint Server 2007 provides three default publishing content types: Page, Article Page, and Welcome Page.
Imagine, for example, that you have 1000 article pages with an image on the right and that Corporate Communications has decided the image should now appear on the left. In that case, you need to modify only the single Page Layout. You can modify the Page Layout with the desired layout and all the article pages with that layout will reflect the new layout standard.
All page layouts reference a master page that is based on the SPWeb.CustomMasterUrl of the SPWeb class. If multiple Master Pages are available, the page layout determines which Master Page is called for the particular page. All page layouts host controls called field controls that bind to fields on the master page list item. You can use the default controls or build custom ones. Field controls allow content to be edited and rendered for display, just as placeholder controls in MCMS 2002 do.
Page layouts can be used by all page instances that are based on that page layout. Page instances based on the same page layout in different sites can use different master pages.
Page layouts are stored in the Master Page and Page Layout Gallery, a document library that is created when you install Office SharePoint Server 2007. By default, Office SharePoint Server 2007 creates a master page gallery for every site; however, you can only create new pages with the page layouts stored in the master page gallery of the top-level site in the site collection.
As with any type of document stored in a SharePoint library, you can use versioning, check-in and check-out, workflow, and other features on page layouts. These features are available from within the master page gallery. The master page gallery is secured to limit the rights of most users, except those users with designer or higher permission rights.
l Customized CSS only applies to current Web
l To apply to all Webs in Microsoft® Office SharePoint® Server 2007
Ø Make independent CSS file just with style overrides
Ø Reference it in custom.master and/or default.master (after CssLink control)
Ø Choose site setting to push down masters to all subwebs
Consider what graphics and graphic design you require for your site:
· Will your site require banner images of specific sizes?
· Will your site require highly customized images that define the very look and feel of the site? For example, these may be curves that are positioned and lined up with other custom images via html to represent a corporate brand or look and feel.
· Do you have graphics development and creative site design skills required?
· Do you require high optimization of your images (to minimise total page download size) for internet /extranet site scenarios?
Sites that are highly visible (intranet home page) or sites that provide a specific service are good candidates for highly crafted User Interface design.
Examples of these are:
o Corporate Portal Theme
o Corporate Site Theme(s)
· Point Solution (Business Driver Sites)
o Search Centre
o Press Centre
o Research Centre
o Company Division
Some sites in your organisation may require a high degree of interactivity and as a result may require use of the following rich / interactive media:
o Video Streaming
o Web Casts
o Interactive Media Manager
o Audio Streaming
o Pod Casts
· Adobe Flash
· SoapBox / YouTube integration
· Virtual Earth / Google Maps
For each of the above, consider:
· Load on your environment
· Return on Investment (ROI) and Total Cost of Ownership (TCO)
· Level of complexity required to maintain and grow.
· Reliability of external services
· Maturity of technologies (against future potential of the same technology).
· Skill set required to develop.
· Skill set required that you need to retain to maintain and progress solution
Exterior navigation refers to the navigation elements across a set of sites collections and sites. Examples include: Site and Page Navigation, Breadcrumbs.
Interior navigation refers to navigation elements placed within a site, such as the Table of Content Webpart, Content by Query Webpart, Links Webpart. This may take the form of aggregated links from sub sites to a list of links.
In Office SharePoint Server 2007 the site structure is a hierarchy of SharePoint Webs which controls navigation. Webs are container objects that can contain other objects, such as lists, libraries or other Webs. The Webs are arranged in a hierarchy and this hierarchy controls the navigation and security. Each Web has a library for Pages which represent the content of the site.
The goal of navigation in Office SharePoint Server 2007 is to generate dynamic page navigation from the structure of the site. The hierarchy of sites and pages defined in the left-hand side of this slide defines the different levels as they appear to the user displayed here on the right. In the next module we’ll see how these are actually Master Page controls. Pages are dynamically added to navigation and static Authored links to external or internal resources can also be added.
In the example below you see some of the controls typically displayed on a page: a top navigation bar with a highlighted breadcrumb and a menu with fly outs. The goal of navigation is ease of use and transparency so when you create a new subsite in this hierarchy—for example under Investors—the new subsite will automatically appear on the page as part of the navigational structure. In this example, it appears in the fly out. Pages are also dynamically added. And you can display Authored links to any resource within your Internet or any rendered http:// link.
Behind the cover, Microsoft Office SharePoint Server 2007 takes advantage of Microsoft ASP.NET 2.0 pluggable navigation—the Site Map Provider model—to make it easy to build effective menus and navigation. Essentially the provider extracts the hierarchy from the site map and then data sources plug into the hierarchy at any level to display the navigation and controls.
You use a site map to describe the logical structure of your site. You can then manage page navigation by modifying the site map as pages are added or removed, instead of modifying hyperlinks in all of your Web pages. The ASP.NET controls display navigation menus on your Web pages and these navigation menus are based on the site map.
In Office SharePoint Server 2007, you can replace the default navigation provider with your own. You can also configure multiple navigation providers for a site. You can even configure your navigation provider to create a navigational structure targeted to audience type, so that you can provide different audiences with custom navigation.
Several controls for interior navigation:
For rolling up pages in a particular subsection of the site, SharePoint Server provides the Table of Contents control. This control allows authors to create and style a hierarchical view of pages.
· Provides a “site map” view of a site
· Uses data from the navigation sitemap provider
It is often useful to generate a list of links to a series of pages through the site, based on a fixed set of criteria. For example, it might be useful to display a list of the five most recently published press releases about a particular product on the overview page for that product. To accomplish this SharePoint Server provides the Content By Query control. This control allows users to easily define queries that return links to pages that match certain criteria and then style the results.
· Links to content based on a query
· For example, display latest 5 KB articles for SharePoint Server
For selecting links through the site, and from external sites, the Summary Links control enables you to create summaries that include a link, description, and an image, and to set a display style for the summary. Summary links can be organized into groups and sorted using drag and drop.
· Authored links to content
· Same visual styles as Content by Query