Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Chris O'Brien - Modern SharePoint sites and the SharePoint Framework - reference


Published on

Covers the changes Microsoft are making to team sites in Office 365/on-premises SharePoint - in terms of end-user changes, and also the impact on developers. The second half of the deck covers the SharePoint Framework (the new coding framework for developers).

Published in: Internet
  • Be the first to comment

Chris O'Brien - Modern SharePoint sites and the SharePoint Framework - reference

  1. 1. Independent Consultant Head of Development, Content and Code (UK) @ChrisO_Brien
  2. 2. Increased focus on Office 365 – “cloud first” Hybrid on-premises/online environments becoming more common – but complex! Shift to ‘cloud-friendly’ development approaches e.g. apps/add-ins Core workloads much improved Document management and co-authoring are solid A great intranet platform Even OneDrive for Business now works well! But then…not much else? Fewer end-user functionality updates
  3. 3. Core SharePoint/OneDrive enhancements Focus on mobility
  4. 4. Android app Classification of sites Conditional access controls Copy/move to SharePoint sites Compliance features Data loss prevention Fast site creation Flows Graph enhancements (e.g. SharePoint data) Groups harmonisation Hybrid taxonomy Insights Logging – now unified Mobile views My analytics OneDrive sync for SP sites OneDrive mobile app Page canvas People cards Planner PowerBI SharePoint home page SharePoint mobile app Sharing improvements Sites page pinning Touch-friendly UI User profile enhancements Web parts (new) Yammer enhancements Zero downtime patching
  5. 5. Team site highlights • • New home page • Modern pages - simpler authoring • • • • •
  6. 6. Key items can be pinned Easier metadata entry Easier copy/move (including from a user’s OneDrive)
  7. 7.  No master page on these pages!  Limited extensibility – no web Custom Actions! This means: No real global navigation Branding differences (if custom master page used) ..but, this should be short-term: Microsoft are “looking at this” 
  8. 8. Currently working: Currently NOT working: Likely future state:
  9. 9. New page “canvas” – no classic web part zones Apps, but no IFrames! Similar to recent Delve blog pages
  10. 10. Take note of: Highlighted Content web part PowerBI web part Yammer Embed web part Others to come!
  11. 11. The modern equivalent of Content Search web part… …(or the nearest thing to it) Less functional (at least to begin with)
  12. 12. Pure JavaScript implementation “Baked-in JS injection” Simplified end-user experience (e.g. web part properties)
  13. 13. Modern web parts can work in: But classic web parts can NOT work in modern pages Classic pages Modern pages Classic web parts Y N Modern web parts Y Y
  14. 14. Not just JavaScript, but TypeScript! Use your preferred JS framework – React, Angular, Knockout, jQuery, or none Gulp for build Yeoman for startup No need for Visual Studio!
  15. 15. Pre-requisites: Process:
  16. 16. Fundamentals TypeScript is expected (at least, for now) Client web parts
  17. 17. 1. Variables and types var foo: string var foo: UserProfile var foo: any 2. Typings for libraries (e.g. jQuery, CSOM) 3. Import a module to use it
  18. 18. BaseClientSideWebPart provides:
  19. 19. • Avoid passing web part context around Use of ServiceScope • New “document card” component Consider Office UI Fabric for presentation • Move to a more formal framework if functionality expands Consider React or similar for rendering
  20. 20. Folder Purpose config Settings for bundling/deployment dist Run-time files for your app lib Intermediate folder in build system node_modules JS dependencies src Where you write code typings TypeScript typings
  21. 21. Your files can be hosted anywhere App packages are the deployment vehicle Ensure dependencies are bundled OR referenced
  22. 22. Good news! Likely to be released in a Feature Pack update, some time in 2017
  23. 23. Waldek’s blog: COB blog: DEV.OFFICE.COM developer-tenant
  24. 24. Stefan Bauer Olivier Carpentier: ..and lots of others too 
  25. 25. SharePoint is entering a new era SharePoint dev is changing SPFx does not replace anything – but required to extend new page types