SharePoint as a Web CMS
Download as PPTX, PDF2 likes3,943 views
The document discusses the advantages of using SharePoint for web content management, emphasizing its integration with Windows, rich editing capabilities, and strong workflow features. It highlights the importance of a well-defined collaboration between designers and developers to optimize the platform's potential. Additionally, it addresses shortcomings of SharePoint 2010, including issues with SEO and the commenting system, suggesting enhancements for future versions.
SharePoint as a Web CMS
- 1. SharePointThe Jonah Lomu of CMSAdam CoganChief Architect at SSWMicrosoft Regional Director@AdamCoganDelivering Awesome Web Applications
- 2. Pre-RequisitesOut of Box, orPlatformContent EditorsPower Users eg. Developers eg.DesignersHosting
- 3. AgendaWhy SharePoint?Why companies want SharePoint’s Web Content Management?Take a look at the SharePoint TeamRequirementsAlternatives
- 4. Chief Architect at SSWDeveloping custom solutions for businesses across a range of industries such as Government, banking, insuranceMicrosoft Gold PartnerMicrosoft Regional DirectorVSTS MVP@AdamCoganAbout Adam
- 6. Nor are Content Management SystemsThere are plenty on the marketThe need for web publishing is not newDoesn’t suck
- 8. Scenario: Sprawling company with lots of departments
- 9. Businesses make $ ...Why companies want SharePoint’s Web Content Management
- 10. A: Windows (and AD) Integrated
- 11. SharePoint – managing groups
- 12. B: Already using it on intranet
- 13. C: Rich editing experience
- 15. "Hey Joe, can you check in Welcome.aspx"
- 16. Help. I introduced a bugE: Publishing
- 17. Remove IT’s workload / crankiness
- 18. F: Workflow is greatCreate the workflow in Office SharePoint Designer 2007
- 19. F: Workflow is greatWorkflow in Office SharePoint Designer 2010
- 20. F: Workflow is great3rd Party: Workflow in Nintex
- 21. F: Workflow is great3rd party: Workflow in K2 Blackpearl
- 22. Kick it off in SharePoint
- 23. G: Customize with .NET
- 24. H: Already sold – it’s the future
- 25. 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.mspxI: Microsoft’s #1 selling server product
- 26. J: All the other things
- 27. J: All the other things
- 28. So... Let’s look at a SharePoint team
- 29. A SharePoint team – introducing the people involved
- 30. A SharePoint team – introducing the people involved
- 31. Initially (planning and configuration stage)
- 32. Followed by... (development stage)
- 33. ... And once it’s up (content stage)
- 34. 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 developerStyle Tip: the designer's job must be defined
- 35. Working together is important otherwise:Avoid Designer vs DeveloperDesigners like it to be perfect, so their designs have the presentation intendedIf they are working they are more understanding and you avoide.g. It is not perfectly centrede.g. This pixel is out of alignmente.g. Colours are not right... this is 1 shade off due to compression...the designer's job must be defined (cont)
- 36. Q:\ How do you get our great resultBy avoiding dealing with thisAt Work ... (A SharePoint public sites needs focus)TheResult
- 37. BEFORE: .psd
- 39. BEFORE: .psd
- 41. an added bonus…
- 44. SEO – Nice URL, nice title tagClipboard functionality like in WordCopy-Paste ImagesRibbon bars with easy formatting (h1, h2, h3 etc)Key Requirements
- 45. Nice HTMLNo Word-inserted CSS! ... Key Requirements
- 47. Ordering by ‘category’Not date...Key Requirements
- 48. CommentsCan group KB article in multiple categoriesPublishing/Approval WorkflowSort by rating and popularityImage handlingie. renaming...“Nice to have” requirements
- 49. Create a standard Team Site in SharePoint FoundationCreate a Wiki Library
- 50. This will take you into Rich Text Edit Mode for editing page.
- 51. Rich Text Editor - Blog
- 52. Rich Text Editor - Wiki
- 53. Apply styles to textSpell check your content (sux)Insert and format tablesEmbed graphics or videoThe Rich Text Editor
- 54. Spell check not as good as wordNeed to manually check ithttp://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterTechnicalDocumentation.aspx#WordSpellingAndGrammarCheckerThe Rich Text Editor
- 55. But...Done!
- 56. Layout is ugly
- 57. RTE (Rich Text Editor) CSS classes ...Identify CSS classes
- 58. format .ms-rteElementHow styles/themes workIf 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 hereHow do you customize...Identify CSS classes
- 60. SharePoint 2010 Wiki’s don’t have a commenting systemSharePoint 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.comwww.IntenseDebate.comwww.aboutecho.comHow could Microsoft solve this... (two ways)How to Solve the comment problem
- 61. Option 1
- 62. Option 2
- 63. 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 ProblemKeep these 2 the sameLet me change the URL
- 64. Alternatives
- 65. ?Alternatives
- 66. WordPressWiki – Screwturn WikiSharePoint WikiSharePoint Blog...Alternatives
- 67. WordPress
- 68. WordPressNice URLsLiveWriterWiki (over Blog)Minimal Customization - Need to add a view (not sorted by date)PHPUser Experience is consistent with intranetRating SystemIntegrated AuthenticationFound using SharePoint search3/9
- 69. Wiki – Screwturn Wiki
- 70. Screwturn WikiNice URLsLiveWriterWiki (over Blog)Minimal Customization - Need to add a view (not sorted by date).NETUser Experience is consistent with intranetRating SystemIntegrated AuthenticationFound using SharePoint search5/9
- 71. SharePoint Blog
- 72. SharePoint BlogNice URLsLiveWriterWiki (over Blog)Minimal Customization - Need to add a view (not sorted by date).NETUser Experience is consistent with intranetRating SystemIntegrated AuthenticationFound using SharePoint search5/9
- 73. SharePoint Wiki
- 74. SharePoint WikiNice URLsLiveWriterWiki (over Blog)Minimal Customization - Need to add a view (not sorted by date).NETUser Experience is consistent with intranetRating System ?Integrated AuthenticationFound using SharePoint search8/9
- 76. SummaryWhy SharePoint?Why companies want SharePoint’s Web Content Management?Take a look at the SharePoint TeamRequirementsAlternatives
- 77. Thank You!Sydney | Melbourne | Brisbane | Adelaideinfo@ssw.com.auwww.ssw.com.au
Editor's Notes
- #2: Cover page.
- #5: Adam looks weird here...
- #10: #2 video
- #17: **TODO: TRISTAN THIN ONE PLEASE
- #18: JOHN LIU
- #23: Workflows – Nintex workflow K2 blackperl
- #28: I cannot find this image!!!
- #64: http://www.ssw.com.au/ssw/Standards/BetterSoftwareSuggestions/SharePointTeamServices.aspx#WikiSEO