arizona sharepoint professionals group n.
Skip this Video
Loading SlideShow in 5 Seconds..
January 28th 2010 meeting PowerPoint Presentation
Download Presentation
January 28th 2010 meeting

Loading in 2 Seconds...

play fullscreen
1 / 45

January 28th 2010 meeting - PowerPoint PPT Presentation

  • Uploaded on

Arizona SharePoint Professionals Group. January 28th 2010 meeting. Agenda. Tonight’s Sponsor. Welcome Back!!! Happy Birthday AZSPG!!!. Thank You for your support!!!. 191 Attendees 18 volunteers 12 Sponsors 20 Sessions 16 Speakers $5000+ in prizes including 3 Xboxes and

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'January 28th 2010 meeting' - amelia

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
thank you for your support
Thank You for your support!!!

191 Attendees

18 volunteers

12 Sponsors

20 Sessions

16 Speakers

$5000+ in prizes including 3 Xboxes and

Rated 4.7 out of 5 overall

community news
Community News

Office Update Center on TechNet

SharePoint 2010 virtual machine available

SSP Speaker Request for Scottsdale Conference (Feb 25th)

SEO Toolkit (Free)

SharePoint 2010 Dev & Planning Centers

sharepoint 2010 compatibility chart
SharePoint 2010 CompatibilityChart

enterprise web platform
Enterprise Web Platform



Platform Potential

Virtual Earth

Live ID

Live Search

Cloud based services enrich value

Advanced Analytics


Tighter integration


Commerce Server


Foundation of your web business


Windows Server

SQL Server


Dev Tools

sample solution site and examples
Sample Solution Site and Examples
  • WSSDemo (SharePoint 2010)
  • Top SharePoint Sites
  • AdventureWorks Integrated Travel Site
site evaluation
Site Evaluation
  • Business Requirement Review
    • Consider Information Architecture
      • Identify what data needs to be stored and how it will be displayed
      • Content Organization > Navigation Design
    • Site Architecture > Solution Structure
    • Understand and leverage product features before developing custom code
      • Lots of new stuff most folks don’t know about
moss ia components

Establish operational procedures for managing and maintaining IA

MOSS + IA Components

Page and navigation structure


Properties used to classify and organize content items


Defines the attributes of a list item, document, folder

Structured: pre-defined info hierarchies...

Un-structured: relevancy linking, user preferences...

User interface

Structured: pre-defined properties, classification taxonomies...

Un-structured: user-generated properties...

Structured: workflows, lists types, document types, security...

Un-structured: wikis, folksonomies, blogs...

Branding your site
  • Plan the brand strategy
    • Strong, clear and concise identity is the keystone upon which the structural layout, functional purpose and taxonomy depend.
  • Know your platform
    • SharePoint Server and Office SharePoint Designer (SPD) are flexible but require more forethought
      • Work with designers who can leverage SPD through CSS and JavaScript
        • Separation of layers and inheritance are prime considerations in the design stage
  • Try out content variety
    • First iterations more for rough design rather than real content placement
    • Place real content on the pages (not just Latin!)
      • Long strings, multi-level headings, images
Evaluating your content
  • Review and validate user needs and business goals
  • Content management – know your content first!
    • Do a full content audit of current portfolio
    • Programmatically design your Information Architecture based on user needs and business goals
      • Organize content based on your user needs (e.g. MSW moved from organization base to topic base)
      • Determine basic navigation flow to allow for easy discovery with minimal clicks.
        • Usability study indicated global top / local left navigation combined provided best results
    • Do an analysis and plan for content portfolio growth and bake that into your site launch plans
      • Content depth & breadth balance is key for a logically scalable IA structure and usable navigation
building a wcm team
Building a WCM team

Program Manager – strategic, programmatic and marketing leadership

Information Architect – organizes content and designs navigation systems to help people find and manage information

SharePoint Architect – understand the END GOAL of the solution and optimize use of infrastructure and technologies to meet current and future demands

building a wcm team cont d
Building a WCM team, cont’d

Graphic Designer – design of visual elements and style guides

ASP.NET Developers – create and package any necessary customizations

SharePoint Business Analyst – understands and applies SharePoint capabilities for content creation

Content Authors – creation of web content & meta data

sharepoint publishing infrastructure
SharePoint Publishing Infrastructure
  • Provides additional functionality
    • Page layouts
    • Pages library (special list template similar to a document library)
    • Additional field types available with the publishing feature
      • Full HTML content with formatting and constraints for publishing
      • Image with formatting and constraints for publishing
      • Hyperlink with formatting and constraints for publishing
      • Summary links data
    • Content expiration and visibility
moss wcm considerations
MOSS WCM Considerations

Content Deployment – move content from one site to another (i.e. from staging to production)

Variations – tailor sites for different cultures, markets and geographic regions

Host-named site collections – provide scalability for hosting large numbers of sites

Web parts are bad, field controls are good

master pages
Master Pages
  • Define general look and feel
    • CSS references
  • Contain controls that are common for all the pages in a site
    • Top and left navigation menus
    • Logos
    • Search fields
    • Page editing controls
    • Login controls
    • Any other custom controls you decide to create
page layouts
Page Layouts

Publishing page templates

Control what content is displayed and how the content is laid out on the publishing page

ASPX files stored in the Master Page Gallery

Associated with a content type

Contain field controls

page pages layout page content
Page = Pages Layout + Page Content

Inherited from WSS:

  • Versioning, Check-in/Check-out
  • Content types
  • Access control
  • Workflow

Page execution:

Page URL requested

Page layout executed in content of page

Content server controls bind to page fields

Rendered page returned

dynamic web parts
Dynamic Web Parts
  • Office SharePoint Server 2007 features allow content to be more easily distributed and re-used
  • Parts allow the surfacing of off-page data
  • Examples
    • Content Query Web Part (CQWP)
    • List viewer Web Part
    • BDC Web Part(s)
    • Search
    • Table of Contents (TOC) Web Part
dynamic portal design
Dynamic Portal Design

Content delivery

  • Leveraging RSS
    • All lists and libraries can be enabled to emit RSS
    • Content Query Web Part (CQWP) can emit RSS stream of displayed results
    • Created a custom remote list query Web Part to display content from different site collections (where RSS viewer not able to, due to authentication issues)
Style management
  • Plan for use and override of core.css
    • We don’t touch the core.css, we override it
    • Understanding inheritance vs. cascading is critical
      • The order which stylesheets are called is important so that overrides are properly executed
      • Overrides and resets should be called first, followed by structural and page elements next - In CSS proximity equals priority!
    • Reference any CSS using the CSS Link Server control in the master
  • All CSS, their respective images and XSLT files are maintained in a central style library
  • All custom formatting for the roll-up Web Parts added directly to the out-of-box XSLT files

Lessons Learned

Publishing Solutions to Common Problems

  • Leverage content types: helpful for library consolidation, content filtering, and page layout design
  • Use page layouts to control site design and manage publishing efforts
  • Leverage workflow only when necessary or publishing process dictates
  • Use the CQWP for data rollup and filtered RSS feeds.
    • Event rollup
    • News alert feeds
solution package deployment
Solution Package & Deployment
  • Use MOSS Deployment Infrastructure to deploy all custom code to your portal environment
    • Allows setting up development environments quickly
    • Aids in iterative development – redeployments are fast and consistent
  • Utilize installation scripts to assist in automation and upgrade
    • Build process is customized with target files to dynamically generate solution package
  • Automate configuration as much as possible
    • Reduces documentation & support costs
    • Every manual step is a potential point of failure
solution package deployment1
Solution Package & Deployment
  • Deploy through single batch file that:
    • Handles multiple solutions
    • Establishes repeatable install workflow
    • Generated by build process
    • Supports rapid farm or WFE build
  • To facilitate iterative development and initial deployment Master and Page Layout templates can be deployed via solution
    • Challenge is resolving where to keep the source components long-term: through publishing/back-up or source control?
how to approach sharepoint dev
How to approach SharePoint Dev
  • Minimize custom code – use OOB UI where possible
    • SharePoint has met most of our needs
  • Consider the impact of caching on your solution
  • Use PortalLog and SPException for error handling
  • Separate UI presentation layer
    • XSLT web part property to format structured result sets where it applies (i.e., search result scenarios)
    • Use User Controls to encapsulate the UI for server controls
  • Push development normally handled in custom UI to event handlers
  • When designing web parts – consider how to facilitate dynamic pages
  • Web part connections offer a way to package functionality to promote web part reuse
  • Common problems
    • Cleanup SPWeb and SPSite objects
    • Don’t use SPWeb.AllowUnsafeUpdates etc.
internal vs external storage
Internal vs. External Storage

To list or not to list?

  • Content storage really depends on data complexity
    • SharePoint lists work great for simple, flat data
  • Advantages of using lists
    • Tight integration with search
    • Good OOB roll-up and display functionality (no custom code)
  • For large lists (~150K items)
    • Display should be carefully managed through custom views or code
    • Make use of indexes
    • Managed with expiration policies, where appropriate
    • Keep folders to <2000 items
    • For automated feeds into a list, use hashing to determine which folder an item goes in, set the ViewAttributes property of SPQuery to “Scope=\”RecursiveAll\”” to retreive it.
smart architecture supportable site
Smart Architecture = Supportable Site
  • Knowing what SharePoint can/cannot do is recommended before beginning any solution development
    • Customize OOB before creating custom solutions
  • Important to think of design in terms of longer-term support and site evolution
our experts panel
Our Experts Panel

Doug Perkes - Senior Consultant, Microsoft Corp.

Rick Taylor - Summit 7 Systems

Travis Clayton - Microsoft Consulting

Tim Baggs- Microsoft SharePoint TSP

the topics
The Topics

Web content management


SharePoint Search