1 / 34

Using sharepoint to create your public website June 13, 2012 @ 2:45

Using sharepoint to create your public website June 13, 2012 @ 2:45. Presented by: Mark gerow & charles faramarzi-rad, fenwick & west LLP Michael P. Kolb, CIO, dickinson wright PLLC. Dickinson Wright Snapshot:. Dickinson Wright - 11 Offices 300 lawyers Move to SharePoint internally - 2007

ormand
Télécharger la présentation

Using sharepoint to create your public website June 13, 2012 @ 2:45

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using sharepoint to create your public websiteJune 13, 2012 @ 2:45 Presented by: Mark gerow & charles faramarzi-rad, fenwick & west LLP Michael P. Kolb, CIO, dickinson wright PLLC

  2. Dickinson Wright Snapshot: • Dickinson Wright - 11 Offices 300 lawyers • Move to SharePoint internally - 2007 • Move to sharepoint extranet - 2010 • Move to sharepoint website - March 2011 • Initial Drivers • marketing continuity • single source database • connectivity to internal systems

  3. Dickinson Wright:

  4. Dickinson Wright: • Benefits to using SharePoint: • Less training time required if SharePoint is already used in the firm as an extranet/intranet.  • Move content management away from IT Department • Ease transitions with marketing department • familiar with CMS • Website • Contact Manager • Email Marketing • Event Management System

  5. Dickinson Wright:

  6. Dickinson Wright: • Benefits of using SharePoint: • Built in Content Management System (CMS) with work flow, publishing and versioning • SharePoint takes advantage of .NET master pages and layout pages for easier development and control of SharePoint. • Audience targeting of content

  7. Dickinson Wright: • Benefits to using SharePoint: • SharePoint allows for different levels of contribution within organization (content contributors add content but can’t publish without approval) • Lawyers • Department Managers • Content Managers • secretaries • Marketing

  8. Dickinson Wright PLLC • Issues to be aware of: • SharePoint intranet sites are not SEO friendly or compliant for accessibility standards without customization. • Make sure each page has a unique title that reflects it’s content • Make sure each page has a description • Add a description column to all the content types used for each page layout • Make sure each page has an alternative text that describes if for the image search • relevant pages for the site map

  9. Dickinson Wright PLLC • Issues to be aware of: • Branding SharePoint sites requires SharePoint specific branders and/or .net - Price point for SharePoint for Internet Sites is very expensive See link • Need access to system files on the server to do any custom development which may be a long process depending on how IT is involved. • Mobile views require highly customized pages or third party products to change the format of a SharePoint page.

  10. Fenwick’s goals for this Web Site • 1.To take advantage of SharePoint’s built in CMS • 2. Performance is key • 3. Highly interconnected website • 4. Using search and metadata tags to bring content to you (dynamic pages) • 5. Vanity Urls • 6. Maintain and migrate.

  11. Performance • Dynamic Master Pages • Cache is king • Ajax and Jquery

  12. Dynamic MasterPage • Created a base class upon which custom page layouts are based, so that master page swapping can be centralized. The anonymous master page will not contain JavaScript or form tags and other includes required to support content editing, and thus will load much more quickly

  13. Fiddler snapshot • Authenticated

  14. Fiddler snapshot • Anonymous

  15. Cache is King • Output caching • Blob caching • Custom object level caching • Search

  16. Custom object level caching • Cache all objects content (example cache all professionals) • Perform queries against that cache • Cache the result of that query

  17. Ajax and Jquery • Making Ajax calls using Jquery to layout pages. • Asynchronous calls will make the page appear to load faster. (search pages). • Will have no page refresh • All this is done without using asp.net Ajax and post backs.

  18. Demo • Professional Search • Search Feeds • Trending topics

  19. Interconnected WebSite • Data is pulled in to the page from all over the site collection. • Everything is tagged so that you can click on a tag and see everything that is associated with that tag. • Great use of managed metadata • Great for Search • Great for SEO

  20. DEMO • Topics and Topic detail page.

  21. Using search and Managed metadata • Extensive Use of Taxonomy fields • Tied in with Custom Content Types • Creation of Managed Properties in Search • Enter “The Filter Feed” • 70-80% of our content is delivered via these feeds. • Using SharePoint Search

  22. Demo • Filter Feed

  23. Vanity Urls • Needed a Way to Continue to Serve Urls from legacy ASP site, and • SharePoint Urls are: • Ugly • Bad for SEO • … but • You can use an Http Module to reroute Urls, so that old links will be redirected to corresponding pages on new site

  24. The Process

  25. Control List • SharePoint List Used to Map Urls http://www.fenwick.com/attorneys/4.2.1.asp?aid=304

  26. Maintenance and Migration tools • Built tool to migrate content into the site from the legacy site.

  27. Maintenance and Migration tools • Built tool to update the new pages with all the necessary webparton a global scale or local scale

  28. Maintenance and Migration tools • Built tool to swap page layouts for when we have to update the page layouts.

  29. Maintenance and Migration tools • Had to build our own warmup tool. • Because every page has cached content on there, we wanted to make sure that every page is hit. • Very similar to how SharePoint search crawls the pages

  30. Maintenance and Migration tools • Built scripts to migrate databases and new wsps from production to backup Farms.

  31. Lessons learned • Search offers the best bang for buck when it comes to querying large dataset with performance in mind. • Make sure the data structures are the first thing that are designed and locked down. Headache to go through and change after the fact. • Create the content types using visual studio

  32. Lessons learned • If caching in code, when it comes to taxonomy fields, you need to build string representations of them in order for caching to work. • XML Web Parts are a savior. • Take the time to build xml representation of the page. Build a utility that will generate a xml for every page that is visited, and then use xslt to style the page.

  33. Lessons learned • Page Layouts were a nightmare when it came to updating them. Especially after migration had happened from legacy database. • That is why we created the page layout swapper. • Use SharePoint designer to create your custom layouts.

  34. Lessons learned and pitfalls to avoid • Plan your DR. • Agile really works

More Related