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).

2. Independent Consultant
Head of Development,
Content and Code (UK)
www.sharepointnutsandbolts.com
@ChrisO_Brien
http://cob-sp.com/COBLinkedIn

3. 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

4. Core SharePoint/OneDrive enhancements
Focus on mobility

5. 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

6. Team site highlights
•
• New home page
• Modern pages - simpler
authoring
•
•
•
•
•

8. Key items can be
pinned
Easier metadata
entry
Easier copy/move
(including from a
user’s OneDrive)

9.  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” 

10. Currently working:
Currently NOT working:
Likely future state:

11. New page “canvas” – no classic web
part zones
Apps, but no IFrames!
Similar to recent Delve
blog pages

12. Take note of:
Highlighted Content web part
PowerBI web part
Yammer Embed web part
Others to come!

13. The modern equivalent of
Content Search web part…
…(or the nearest thing to it)
Less functional (at least to begin with)

14. Pure JavaScript
implementation
“Baked-in JS injection”
Simplified end-user
experience (e.g. web part
properties)

19. 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

22. 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!

23. Pre-requisites:
Process:

24. Fundamentals
TypeScript is expected (at least, for now)
Client web parts

25. 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

26. BaseClientSideWebPart provides:

28. • 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

29. 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
cob-sp.com/SPX-Files

31. Your files can be hosted anywhere
App packages are the deployment vehicle
Ensure dependencies are bundled OR referenced

32. Good news!
Likely to be released in a Feature
Pack update, some time in 2017

33. Waldek’s blog:
https://blog.mastykarz.nl/tag/sharepoint-framework/
COB blog:
http://cob-sp.com/SharePointFrameworkIntroPresentation
http://cob-sp.com/SPFx-WP-Props1
http://cob-sp.com/SPFX-Promises
DEV.OFFICE.COM
http://dev.office.com/sharepoint/docs/spfx/set-up-your-
developer-tenant

34. Stefan Bauer
http://www.n8d.at/blog/tag/spfx/
Olivier Carpentier:
https://twitter.com/OlivierC
..and lots of others too 

35. SharePoint is entering a new era
SharePoint dev is changing
SPFx does not replace anything – but required to extend new page types