Embed Size (px)
Citation preview
Building Public Facing SharePoint Sites
George Durzi
Consultant – Clarity ConsultingINETA User Group Mentor for IL, WI, and IN
Agenda
• Topology• Solutions and features • Publishing assets• Publishing site definitions• Content Deployment• Considerations for public facing sites
Topology
AuthoringPublishing
Content Deployment
Installed SharePoint solutions
Intranet DMZ / Public Internet
Installed SharePoint solutions
Demo – Sample Site
Solutions and Features
• 1 Visual Studio solution• 1 Visual Studio project = 1 WSP– Multiple features in one solution
• Ability to build on desktop and in TFS– MAKECAB, STSDEV, VS Extensions for WSS …
• Deployment scripts• Separating functionality into features
Demo – Solutions and Features
Publishing Assets
• Run-once assets– Required to initially bring up the site– Images, CSS, etc.– HTML content
• Bulk import
• Isolate in own feature• Throwaway?• Who will be authoring content after go live?• Content authors• Developers• Both?
Publishing Site Definitions
• Use a minimal publishing site definition– Easier than cleaning up OOB Publishing site
• Site definition feature activates others• Don’t replicate any look and feel• Stapling vs. Packaging– How to decide?• Only one instance of the site, or many?• Will the site definition change?
Demo – Assets / Site Definition
Content Deployment
• Isolate authoring to an authoring environment• Scheduled incremental content deployment
jobs to deploy to Production• Quick Deploy• Handy Publishing tools:– AC’s STSADM extensions– Check for unpublished items– Related resources view
Demo – Content Deployment
Considerations for Public Sites
• Caching• SEO• Page payload• Sitemap.xml• Configuring anonymous access• Migrating an old site to SharePoint?
Q&A
