1 / 41

Empowering non-power users to publish and edit content

Empowering non-power users to publish and edit content. From the Trenches…. Mike keenan Rick Krzyminski Manish awasthi. Presenters. Mike Keenan, SharePoint Administrator, Nixon Peabody LLP, Rochester, New York, 700+ Attorneys

aelan
Télécharger la présentation

Empowering non-power users to publish and edit content

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. Empowering non-power users to publish and edit content From the Trenches…. Mike keenan Rick Krzyminski Manish awasthi

  2. Presenters • Mike Keenan, SharePoint Administrator, Nixon Peabody LLP, Rochester, New York, 700+ Attorneys • Richard J. Krzyminski, Assistant Director of Global Knowledge & Web Solutions, Mayer Brown LLP, Chicago, Illinois, 1600+ Lawyers • Manish Awasthi, Chief Global SharePoint Architect, Baker & McKenzie, Chicago, Illinois, 4000+ Lawyers

  3. Current Environments • Nixon Peabody: SharePoint 2003 Portal with separate WSS 2.0 server (150+ sites) and separate WSS 3.0 server (1000+ sites). SharePoint 2010 build-out is in progress with plans for matter-centric environment (site for every matter) and eventual use of SharePoint as a DMS. • Mayer Brown: MOSS 2007, moving to SharePoint 2010 in July. Matter-Centric environment using iManage WorkSite 8.5. Integration with SharePoint provided by Handshake. • Baker McKenzie – Moss 2007 – Intranet, SharePoint 2010 – In production for non Intranet Applications.

  4. Stories from the trenches, “what we’ve learned”…. • Remember the goal: “Get the right information to the right people at the right time” • Considerations: • Ease of publishing • Design, usability and layout • Audience targeting and regional concerns • Governance is KEY

  5. Ease of publishing • Content editor web parts or lists? • Static data or collaboration? • Master data management • Dataflow/automation • Workflow • Approvals? • Data delivery

  6. Design, usability and layout • Publishers often want to be designers • Users want pictures on pages • Users don’t like endless bulleted lists • Templates and standards

  7. Audience targeting/regional concerns • Local laws and culture • Permissions and security • Creating teams • Real-time support

  8. Governance is key • Best practices • Auditing • Rules • Senior committee/evangelists

  9. Demo • Baker McKenzie Intranet • Allowing end users to create and maintain pages

  10. A Typical Intranet Site

  11. Global Navigation

  12. Centrally Governed Area

  13. Locally Governed Area

  14. ungoverned limited options area

  15. Site designer creates a page

  16. Select layout

  17. Add Webpart

  18. Select Webpart

  19. Publish Page

  20. Add Content to Page

  21. example one

  22. example two

  23. example THREE

  24. So, What’s new in sharepoint 2010?

  25. What’s new in 2010, and why should I be concerned? • The Office style ribbon brings familiar editing controls to end users • Ability to put a page in edit mode and just start typing text • Ability to browse to an image file and automatically upload to SharePoint • SharePoint Designer 2010 is much, much more powerful than SharePoint Designer 2007 • Modal Dialogs make accessing page content easier

  26. Any new safeguards introduced in 2010 that will help us? • Text entered on a page using SharePoint Designer cannot be styled using normal ribbon functions by default since it uses the WikiContentWebPart. • To allow users to apply styles etc. using browser, add Content Editor Web Part (CEWP) to page.

  27. Any new safeguards introduced in 2010 that will help us? • Using SharePoint Designer 2010 you can create content zones that can not be edited in the browser, even for those with advanced editing rights

  28. Any new safeguards introduced in 2010 that will help us?

  29. Any new safeguards introduced in 2010 that will help us? • Our new page has no editable zones thru browser so users can’t modify our content • Normal ribbon options for editing page are not present

  30. Any new safeguards introduced in 2010 that will help us? • Using Publishing , Content Types and Page Layouts, you can restrict which options show in ribbon when page is in edit mode • Normal ribbon options for editing page:

  31. Any new safeguards introduced in 2010 that will help us? • In Designer, Page Layout can be modified to restrict things like font changes. When the tag properties are set to true for content sections, normal ribbon settings are in place. • Set a tag property to false….

  32. Any new safeguards introduced in 2010 that will help us?

  33. Any new safeguards introduced in 2010 that will help us? • The page (and any pages built in future from this Page Layout )cannot have fonts altered.

  34. What about Publishing?

  35. 2010 Permission Levels OOTB

  36. 2010 Permission Levels OOTB

  37. tips that can help • Leverage existing data sources to make content maintenance easier • Canned Searches • Build templates that include parts with a variety of data sources. • Build a FAQ library or video help site

  38. Mine existing data sources for matter-centric data

  39. Mine existing data sources for matter-centric data

  40. DEMO • baker mckenzie plans to utilize sharepoint 2010 Oob features to manage pages in intranet

  41. Resources that can help • SharePoint -Videos.com • SharePoint Governance on Technet • Governance Planning White Paper • Governance Book on Amazon (4.5 stars) • Joel Oleson Governance Slide Presentation

More Related