This document summarizes a presentation about using SharePoint as a content management system. It discusses why companies choose SharePoint, the roles involved in a typical SharePoint team, requirements of content editors, and compares SharePoint to other options like WordPress and Screwturn Wiki. The presentation concludes that SharePoint Wiki is the best option, scoring highest in meeting content editor needs and preferences.

1. SharePointThe Jonah Lomu of CMS Adam Cogan Chief Architect at SSW Microsoft Regional Director @AdamCogan Delivering Awesome Web Applications

2. Agenda Why SharePoint? Take a look at the SharePoint Team What do Content Editors want? The Smackdown

3. Chief Architect at SSW Developing custom solutions for businesses across a range of industries such as Government, banking, insurance Microsoft Gold Partner Microsoft Regional Director VSTS MVP @AdamCogan About Adam

5. Nor are Content Management Systems There are plenty on the market The need for web publishing is not new

6. 1. Why SharePoint?

7. Scenario: Sprawling company with lots of departments

8. Businesses make $ ... #1 Why companies want SharePoint’s Web Content Management

9. A: Windows (and AD) Integrated

10. SharePoint – managing groups

11. B: Already using it on intranet

12. C: Rich editing experience

13. Someone has stuff checked out... D: Presence stuff is awesome

14. "Hey Joe, can you check in Welcome.aspx"

15. Help. I introduced a bug E: Publishing

16. Remove IT’s workload / crankiness

17. F: Workflow is greatCreate the workflow in Office SharePoint Designer 2007

18. F: Workflow is greatWorkflow in Office SharePoint Designer 2010

19. F: Workflow is great3rd Party: Workflow in Nintex

20. F: Workflow is great3rd party: Workflow in K2 Blackpearl

21. Kick it off in SharePoint

22. So easy, a baby could do it! … although it would have to be some kind of genius developer baby G: Customize with .NET

23. H: Already sold – it’s the future

24. March 2008 “US$1billion-dollar business with 100 million licenses sold, and growth of more than 50 percent in the second quarter of the current fiscal year” http://www.microsoft.com/presspass/features/2008/mar08/03-02SharePoint.mspx I: Microsoft’s #1 selling server product

25. J: All the other things

26. 2. So... Let’s look at a SharePoint team

27. A SharePoint team – introducing the people involved

28. A SharePoint team – introducing the people involved

29. Initially (planning and configuration stage)

30. Followed by... (development stage)

31. ... And once it’s up (content stage)

32. Overall PSDs – “concept mockup” (Wakefield) Slice into HTML and Images - “HTML mockup” Make the CSS files for the HTML – “HTML styling” Give back to the developer Style Tip #2F: the designer's job must be defined

33. Working together is important otherwise: Avoid Designer vs Developer Designers like it to be perfect, so their designs have the presentation intended If they are working they are more understanding and you avoid e.g. It is not perfectly centred e.g. This pixel is out of alignment e.g. Colours are not right... this is 1 shade off due to compression ...the designer's job must be defined (cont)

34. Q:How do you get our great resultBy avoiding dealing with this At Work ... (A SharePoint public sites needs focus) TheResult

35. BEFORE: .psd

36. AFTER: Live Website

37. BEFORE: .psd

38. AFTER: Live Website

39. an added bonus…

42. 3. What do Content Editors want?(and how to solve them)

43. SEO – Nice URL, nice title tag Clipboard functionality like in Word Copy-Paste Images Ribbon bars with easy formatting (h1, h2, h3 etc) Key Requirements

44. Nice HTML No Word-inserted CSS! ... Key Requirements

46. Ordering by ‘category’ Not date ... Key Requirements

47. Comments Can group KB article in multiple categories Publishing/Approval Workflow Sort by rating and popularity Image handling ie. renaming ... “Nice to have” requirements

48. Create a standard Team Site in SharePoint Foundation Create a Wiki Library

49. This will take you into Rich Text Edit Mode for editing page.

50. 4. Rich Text Editor - Blog

51. 4. Rich Text Editor - Wiki

52. Apply styles to text Spell check your content (sux) Insert and format tables Embed graphics or video 4. The Rich Text Editor

53. Spell check not as good as word Need to manually check it http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterTechnicalDocumentation.aspx#WordSpellingAndGrammarChecker 4. The Rich Text Editor

54. But... 4. Done!

55. 4. Layout is ugly

56. RTE (Rich Text Editor) CSS classes ... 4. Identify CSS classes

57. format .ms-rteElement How styles/themes work If you have no site them applied to a site (default – no theme) CSS files are resident in the 14 hive (SharePoint 2010) Once you apply a theme the CSS files are auto-propagated to themes folder of the site and you can modify the CSS form here How do you customize... 4. Identify CSS classes

58. Verdict on Comments

59. SharePoint 2010 Wiki’s don’t have a commenting system SharePoint 2010 Blogs have an ordinary commenting system (no threading, no spam detection etc) Suggestion to Microsoft: built in web part to add one of the main 3rd party commenting systems: www.Disqus.com www.IntenseDebate.com www.aboutecho.com How could Microsoft solve this... (two ways) How to Solve the comment problem

60. Option 1

61. Option 2

62. SEO marketers want to stuff different keywords into the: Page Name, Page Title, URL and Meta Description Problem. SharePoint 2010 Wiki’s assumes the same text in first 3 and offers no way of editing the ‘Meta Description’ tag. This is an incorrect assumption and should be fixed in SP1 (if Microsoft wants to get it used in the CMS world). http://www.ssw.com.au/ssw/Standards/BetterSoftwareSuggestions/SharePointTeamServices.aspx#WikiSEO ... SEO – Page Name, Page Title, URL and Meta Description Problem Keep these 2 the same Let me change the URL

63. Bad Performance

64. Good example

65. http://blog.mastykarz.nl/generating-css-sprites-imtech-spritegenerator/ Sprite Generator

66. 4. The Smackdown

67. ? The Smackdown

68. WordPress Wiki – Screwturn Wiki SharePoint Wiki SharePoint Blog ... The Smackdown

69. WordPress

70. WordPress Nice URLs LiveWriter Wiki (over Blog) Minimal Customization - Need to add a view (not sorted by date) PHP User Experience is consistent with intranet Rating System Integrated Authentication Found using SharePoint search 3/9

71. Wiki – Screwturn Wiki

72. Screwturn Wiki Nice URLs LiveWriter Wiki (over Blog) Minimal Customization - Need to add a view (not sorted by date) .NET User Experience is consistent with intranet Rating System Integrated Authentication Found using SharePoint search 5/9

73. SharePoint Blog

74. SharePoint Blog Nice URLs LiveWriter Wiki (over Blog) Minimal Customization - Need to add a view (not sorted by date) .NET User Experience is consistent with intranet Rating System Integrated Authentication Found using SharePoint search 5/9

75. SharePoint Wiki

76. SharePoint Wiki Nice URLs LiveWriter Wiki (over Blog) Minimal Customization - Need to add a view (not sorted by date) .NET User Experience is consistent with intranet Rating System ? Integrated Authentication Found using SharePoint search 8/9

77. SharePoint Wiki! Winner is...

78. Summary Why SharePoint? Take a look at the SharePoint Team What do Content Editors want? The Smackdown

79. Thank You! Sydney | Melbourne | Brisbane | Adelaide info@ssw.com.auwww.ssw.com.au

80. http://www.slideshare.net/SSWconsulting/ Slideshare