1. Building Public Facing SharePoint Sites George Durzi Consultant – Clarity Consulting INETA User Group Mentor for IL, WI, and IN

2. Contact Information george.durzi@claritycon.comhttp://tinyurl.com/gdurziblog@gdurzi

3. Agenda Topology Solutions and features Publishing assets Publishing site definitions Content Deployment Considerations for public facing sites

4. Topology Authoring Publishing Content Deployment Installed SharePoint solutions IntranetDMZ / Public Internet Installed SharePoint solutions

5. Demo – Sample Site

6. 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

7. Demo – Solutions and Features

8. 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?

9. Publishing Site Definitions Use a minimal publishing site definition – Easier than cleaning up OOB Publishing site Site definition feature activates others Dont replicate any look and feel Stapling vs. Packaging – How to decide? Only one instance of the site, or many? Will the site definition change?

10. Demo – Assets / Site Definition

11. Content Deployment Isolate authoring to an authoring environment Scheduled incremental content deployment jobs to deploy to Production Quick Deploy Handy Publishing tools: – ACs STSADM extensions – Check for unpublished items – Related resources view

12. Demo – Content Deployment

13. Considerations for Public Sites Caching SEO Page payload Sitemap.xml Configuring anonymous access Migrating an old site to SharePoint?

14. Q&A

15. Contact Information george.durzi@claritycon.comhttp://tinyurl.com/gdurziblog@gdurzi