Managing and Using Microsoft SharePoint 2010

1. Managing and Using Microsoft SharePoint 2010 By Gerard Beckerleg

2. Course Website • http://sharepoint.ssw.com.au/Training/UTSSP2010/ • Course Materials

3. Part A: SharePoint 2010 Sessions Part A SharePoint Concepts and Use

4. Part B: SharePoint 2010 Sessions Part B SharePoint Configuration and Admin

5. Session 7: SharePoint 2010SharePoint Portal and Web Publishing

6. Agenda • What is Web Publishing • Organize and create web content in SharePoint • Getting SharePoint web site off the ground • What’s out of the box • Best Practices • SharePoint Publishing strength and weaknesses

7. What is web publishing, exactly? • ?

9. What is web publishing, exactly? • Web publishing is user-driven web content management • Lots of examples of this • Wikipedia • Many CMSes available, all with different primary purposes • Key uses for web publishing on SharePoint include intranets and public websites

10. How does this concept fit within SharePoint? • Publishing sites are a feature of SharePoint Server • Not included with SharePoint Foundation (no page layout) • But various concepts are available in (and extended upon) SharePoint Foundation • Extends on core SharePoint concepts such as • Lists and libraries • Content Types • As a result, offers many of the productivity features like integrated editing functionality, version control, workflows, etc

11. A few website fundamentals

12. Without looking – what do you expect to see in a web site • ?

13. Content • Of course, content.

14. Navigation • How do users find content on a site? • Menu / navigation bar • Breadcrumb • Links in content • Search

15. Familiar elements • Common header • Common footer • Common search box • Familiar layout as you move from page to page

16. Bringing it all into a SharePoint world

17. Team Sites vs Publishing Sites In a nutshell: • Team Sites are structured around lists and libraries • Publishing Sites are structured around pages (specifically, in the Pages library) • SharePoint Server only • As many pages as you like • Introduces support for Page Layouts • Publishing sites also support lists and libraries

18. SharePoint publishing sites:a structural birds-eye view • Your SharePoint structure will contain Sites • Each site contains Pages • Each page’s layout is defined by your site collection’s Page Layouts • Your overall design framework is handled by Master Pages • Framework CSS and images usually go into a central Style Library in the root site

19. Master Page Todd’s Bikes Navigation Page Layout A Bike View All Bikes A Bikeajifgoawejfioawjfoiafkasdlvmawoc as dckm More content goes here Welcome Another Bikeajifgoawejfioawjfoiafkasdlvmawoc as dckmawejfioasdjfoafkasndklfnaijwefnjdkfniewf Some intro content Next Bikeajifgoawejfioawjfoiafkasdlvmawoc as dckmawejfioasdjfoafkasndklfnaijwefnjdkfniewf Featured Bike A Bikeajifgoawejfioawjfoiafkasdlvmawoc as dckm

21. What’s in a page? • Like everything in SharePoint, a page is an item in a list • Each page (like all list items) is based on a particular content type, which means that you have a consistent set of fields for related types of pages • You can have items of different content types in the same Pages library

22. Remind me what’s Content Type again? • Understanding content type is crucial for SharePoint Publishing Sites • A content type is a schema, basically tells SharePoint what fields exists for this item • A welcome page may have “Rich Content” as HTML • An Article page extends that further and has “Byline” as text, and “Article Date” as date time.

23. Content Type (cont) • Fields that you enter into a big HTML area is a blob. It is unstructured. • Fields that you enter into specific fields such as Article Date is structured • Allows you to, for example, query SharePoint and display a list of articles produced in the last 60 days, with links to each one • It is difficult to get structured data out of unstructured data after the fact. Part of the design of a SharePoint Publishing site is to determine which fields your editors should use from day one

24. What’s in a page? (cont) • Web Parts are a fairly central aspect of a page’s configurability. • Web Parts are reusable “modules” that can be dropped into most pages • Each Page Layout can contain Web Part Zones that can host as many web parts as is necessary.

25. What tools are needed? • To create and edit Master Pagesand Page Layouts:SharePoint Designer • To edit page content, content types, structure, etcBrowser web interface • To design page framework, graphics, etcDesign tools (e.g. Photoshop, Fireworks, Expression, MS Paint  etc) • To create packages for deploying your website to multiple serversMicrosoft Visual Studio • To test your siteEvery web browser known to man

26. What is your typical SharePoint web publishing team? • Web DesignersDefine the look and feel of your site and incorporate it into stylesheets and master pages. • SharePoint ArchitectsDesign the structure of the SharePoint site • SharePoint AdminsConfigure and maintain the server • DevelopersWrite components and extend SharePoint where appropriate • Content EditorsPopulate and maintain the site’s data

27. Get practical! Lab work

28. Session 6 Lab • SharePoint 2010 Lab 6 Download from Course Materials Site: http://sharepoint.ssw.com.au/Training/UTSSP2010/

29. How can I extend these concepts further? • SharePoint offers a vast array of configurability beyond what we’ve covered in these lab steps. In particular: • Many of the web parts can be styled with XSL^ • You can build a master page design from scratch^ • You can style many other components with CSS. • Most of the lists, as well as many of the web parts, can be syndicated with RSS • You can use many of the concepts we’ve covered in earlier sessions to provide more opportunities for presenting data and documents via a public website (e.g. lists and libraries)

30. Why is SharePoint a good platform for web publishing? • Ease with which end users can manage content • Great integration of site structure and navigation • Workflow • Libraries and lists means there’s great potential for integration with SharePoint’s data features in your publish website • Based on ASP.NET (widely known and supported development platform)

31. What are SharePoint’s web publishing weaknesses? • HTML output is not web standards compliant • Can be addressed with various add-ons and extensions • Accessibility is not a strong point • Fully-featured editing support for IE only • (FIXED in SP2) • Large deployment overhead • Requires substantial planning and testing to create a solution that can be applied to multiple servers

32. Where Else Can I Get Help? Where else can I get help? • Andrew Connell has a blog on SharePoint administration which frequently addresses development gotchas with publishing sites: www.andrewconnell.com/blog • SSW has a number of best practices and rules published over at http://rules.ssw.com.au

33. Reference • SharePoint 2010 Large Page Libraryhttp://technet.microsoft.com/en-us/library/ee721053(office.14).aspx

34. Thank You! Gateway Court Suite 10 81 - 91 Military Road Neutral Bay, Sydney NSW 2089 AUSTRALIA ABN: 21 069 371 900 Phone: + 61 2 9953 3000 Fax: + 61 2 9953 3105 info@ssw.com.auwww.ssw.com.au