SharePoint 2010 Web Content Management - The Developer Story
Download as PPTX, PDF1 like2,747 views
This document discusses the improvements to web content management (WCM) in SharePoint 2010. It provides tips for both content editors and developers. For content editors, SharePoint 2010 provides a improved user experience with features like a ribbon interface and rich text editing. For developers, there are cleaner markup, extensibility, and support for new technologies like Silverlight and AJAX. The document concludes by emphasizing the importance of learning the new tools and approaches for building rich websites in SharePoint 2010.
![Tip #5: Unlock Client OM for anonymous$wa = Get-SPWebApplication -Identity "http://diwug"$wa.ClientCallableSettings.AnonymousRestrictedTypes.Remove([Microsoft.SharePoint.SPList], "GetItems")$wa.Update()Keep in mind: Decreases security!More info:http://blog.mastykarz.nl/go/diwug-325](https://image.slidesharecdn.com/diwugwcm-100527034609-phpapp01/85/SharePoint-2010-Web-Content-Management-The-Developer-Story-31-320.jpg)
Ad
More Related Content
What's hot (20)
Similar to SharePoint 2010 Web Content Management - The Developer Story (20)
Ad
More from Waldek Mastykarz (20)
Ad
Recently uploaded (20)
SharePoint 2010 Web Content Management - The Developer Story
- 1. SharePoint 2010Web Content ManagementThe Developer Story
- 2. 2
- 3. AgendaWCM Challenges in the pastWCM the 2010 wayNot-so-out-of-the-box stuffTips’N’Tricks3
- 4. 4 Anonymous Enabled
- 5. Customers’ challengesNo support for web standards
- 7. No support for media
- 8. Expensive!5
- 9. MOSS 2007 WCM developer challengesNo developer tools
- 11. No control over HTML
- 12. Markup: mine vs. theirs6
- 14. “...and then SharePoint became the center of the universe...”8
- 15. Good NewsEverything you learned applies!SharePoint Server 2010 For Internet Sites Standard9
- 16. If you are content editorGreat User ExperienceRich authoringRibbonRich Text EditorFluent UILive previewWeb Parts in contentMultilingual UICross-browser!Support for Assets & Rich MediaManaged MetadataWeb Analytics10
- 17. 11SharePoint Server 2010 Rich Editing Experience
- 18. If you are developerCleaner markupHighly extensible UIImproved Content Query Web PartSupport for SilverlightSupport for AJAXNew theming engine12
- 19. Content Query Web Part 2010SlotsContent-to-contentRenders div’s by defaultStill no pagingat least not out of the box ;-)13
- 20. 14Content Query Web Part new capabilities
- 22. CKS:DEVWhat’s there for Publishing:Import Content TypeCreate Page LayoutExplore Publishing PagesExplore Master Pages GalleryExplore Style LibraryComing soon:Export Publishing PageCancel Adding SharePoint ItemsActivate Selected Features…and moreSet of SharePoint productivity tools for developersFully integrated with Visual Studio 2010 SharePoint Developer ToolsFree & Open sourceCommunity drivenGet it now from http://blog.mastykarz.nl/go/diwug-116
- 23. 17CKS:DEV features for WCM solutions
- 24. SubclassedContent Query Web PartNew functionalitySupport for PagingCustom XSLT parameters and functionsEXSLTCalling into SharePoint Object ModelEasy access to hidden propertiesSetting custom XSLTOverriding QueryToggling CacheMore info:http://blog.mastykarz.nl/go/diwug-218
- 25. 19CQWP show off: Cool Pager with Mavention Content Query Web Part
- 27. Tip #1: Be careful what you promiseWell-formed XHTML vs. Valid XHTMLCQWP vs. Managed MetadataNo more support for IE6!Custom vs. out-of-the-boxOut of the box: solid foundationStill lots of partner opportunity21
- 28. Tip #2: UseSimpleRenderingSharePoint 2007 menu as tablesUseSimpleRenderingNew property on the SharePoint 2010 menu controlRenders menu as a nested unordered list<SharePoint:AspMenuUseSimpleRendering="true"runat="server"/>22
- 29. Tip #3: Make branding available in RTERichHtmlField attributesStyleSheet – point to your CSS filePrefixStyleSheet – create custom prefix to suppress standard brandingDoesn’t work with CEWP!<PublishingWebControls:RichHtmlFieldFieldName="PublishingPageContent“StyleSheet="<% $SPUrl:~sitecollection/Style Library/CSS/styles.css %>"PrefixStyleSheet="m-“HasInitialFocus="True“MinimumEditHeight="400px"DisableInputFieldLabel="true"runat="server"></PublishingWebControls:RichHtmlField>23
- 30. Tip #4: Test anonymous ASAPSame as in MOSS 2007 but now even more importantRequires extra attentionSharePoint LINQSilverlight OMHierarchical titleshttp://blog.mastykarz.nl/go/diwug-4Body ID’shttp://blog.mastykarz.nl/go/diwug-524
- 31. Tip #5: Unlock Client OM for anonymous$wa = Get-SPWebApplication -Identity "http://diwug"$wa.ClientCallableSettings.AnonymousRestrictedTypes.Remove([Microsoft.SharePoint.SPList], "GetItems")$wa.Update()Keep in mind: Decreases security!More info:http://blog.mastykarz.nl/go/diwug-325
- 32. Tip #6: Mind new inheritance modelIn SharePoint 2007 <FieldRefs /> to inherit all fieldsIn SharePoint 2010 Inherits=“TRUE”FieldRefs not requiredanymore26
- 33. Tip #7: Use conditional contentLeverage conditional controls to optimize page outputUse conditional processing instead of conditional renderingMore info:http://blog.mastykarz.nl/go/diwug-627
- 34. Tip #8: Set the defaultsDefaultPageLayout: new in SharePoint Server 2010 Publishing FeatureConfigures the default Page Layout used for one-click creating new Publishing Pages<WebFeatures><FeatureID="22A9EF51-737B-4ff2-9346-694633FE4416"><PropertyKey="DefaultPageLayout"Value="~SiteCollection/_catalogs/masterpage/MyLayout.aspx"/></Feature></WebFeatures>Tip: Want to create pages even faster?http://blog.mastykarz.nl/go/diwug-728
- 35. Tip #9: Control your CSSIntroduced in SharePoint 2007Allows you to register CSS fileNew in SharePoint 2010: After propertyAllows you to load your CSS after some other CSS<SharePoint:CssRegistrationname="<% $SPUrl:~sitecollection/Style Library/myStyles.css %>"After="corev4.css"runat="server"/>29
- 36. Tip #10: Disable SharePoint DesignerNot needed in production for Internet-facing websitesDisabling finally supported!Configurable per:Web ApplicationSite Collection30
- 37. Tip #11: Don’t use Pages in codeIn MOSS 2007Title depends on locale (Pages/Pagina’s/Seiten)Same URL (Pages)Except for German: SeitenIn SharePoint Server 2010 “fixed”Both title and URL depend on localeRetrieve dynamicallyIn code: PublishingWeb.DefaultPagesListNameIn XML: $Resources:osrvcore,List_Pages_UrlName;<PropertyKey="SearchCenterUrl"Value="~SiteCollection/nl/Search/$Resources:osrvcore,List_Pages_UrlName;"/>31
- 38. Tip #12: Disable PresenceSupported!No more dodgy JSPer Web Application setting32
- 39. Tip #13: Hide Ribbon from anonymous usersConditional processing and Conditional rendering don’t workWhat you need to doHide in CSS<Mavention:SecurityTrimmedControlRenderingAuthenticationRestriction=“AnonymousUsersOnly”runat=“server”><styletype=“text/css”>.ribbonbackground{ display: none; visibility: hidden; }</style></Mavention:SecurityTrimmedControlRendering>33
- 40. Extra tip: Learn your toolsGreat capabilitiesLots of new featuresNew way of thinkingIt does pay back!34
- 41. Key takeawaysMany improvements for content editors and developersNew capabilities simplify building rich websitesVisual Studio 2010 SharePoint Developer Tools are your friend: take your time and learn themBuilding Internet-facing sites is different: don’t underestimate it35
- 43. ResourcesWaldek Mastykarz – Innovation Mattershttp://blog.mastykarz.nlCommunity Kit for SharePoint: Development Tools Editionhttp://cksdev.codeplex.comSharePoint Developer Centerhttp://msdn.microsoft.com/sharepointMicrosoft SharePoint Team Bloghttp://blogs.msdn.com/sharepointMicrosoft Enterprise Content Management Team Bloghttp://blogs.msdn.com/ecmMicrosoft SharePoint Designer Team Bloghttp://blogs.msdn.com/sharepointdesigner37
Editor's Notes
- #3: Wat doe ik? Oplossingen bedenken en ontwikkelen Adviseren Kennis delenExpertise SharePoint 2010 WCM SharePoint 2007 WCM Toegankelijkheid en webstandaarden Development + Application Lifecycle Management SharePointErvaring (1998) 12 jaar webdesign 7 jaar webdevelopment 6 jaar toegankelijkheid 4 jaar SharePoint 2007 1 jaar SharePoint 2010
- #5: Ontwikkelen van Internet-facing sites heeft ook een aantal uitdagingen ivm. anonymous access
- #8: Ontwikkelaars moeten denken aan veel verschillende aspecten. Soms zie je door de bomen het bos niet meer...
- #12: Demo in FirefoxGo to EditingInsert 2x Lorem IpsumLive PreviewInsert Image from ComputerShow contextual Image TabInsert CQWP in text
- #13: There are still *some* tables, but mostly divsQ: Waarvoor gebruikt SP2010 tables?
- #15: Show DIWUG Item StyleGo to Press ReleasesEdit Web PartChange Item Style to DIWUG: Page Content; Article Date; Article CategoryShow content-to-content Query String (click on category)Click on an articleShow related content: Field value on the current page
- #17: Create Content Type in browser
- #20: Go to archiveShow and explain the pager
- #22: CQWP vs. Managed Metadata- Multivalue only for single list queries- All other single value only!Veel partner opportunityimplementeren van rijke brandingseducatie van gebruikers
- #23: Demo in FirebugNightandday.master line 349
- #24: It works with CEWP with some JavaScript tweaking
- #25: More components in SP2010 = more places things can go wrongRich functionality but it means you have to test it all: not all of it has been used in Internet-facing websites yet
- #37: Quiz1. Met hoeveel verschillende acties kan je