Modern SharePoint, the Good, the Bad, and the Ugly

Modern SharePoint, the Good, the Bad, and the Ugly

• 1.
  Bob German Principal Architect BlueMetal
• 2.
  Bob is aPrincipal Architect at BlueMetal, where he leads Office 365 and SharePoint development for enterprise customers. Bob German Cloud & Services Content & Collaboration Data & Analytics Devices & Mobility Strategy & Design An Insight company @Bob1German
• 3.
  Microsoft is modernizingthe SharePoint UI! Over the next few years, Microsoft will change the entire SharePoint user experience to meet the needs of a modern, mobile workforce. It’s like upgrading a car, one part at a time – while you’re driving it cross country! Modern Doc Libs June 2016 Modern Lists July 2016 Modern Team Sites August 2016 Web Era Cloud and Device Era
• 4.
  1. Office 365Group Sites / Modern Team Sites 2. Modern Lists and Libraries 3. Modern Pages • Generally turned “on” by default • You can turn them off at the tenant or more granular levels • You can use modern Pages, Lists, and Libraries in classic team sites (not publishing or blog sites) The Modern Experience
• 5.
  demo The Modern Experience •Creating a Modern Team Site • Tour of Modern Team Site • Modern Lists and Libraries
• 6.
  Good Bad andUgly • News feed works well if needs are simple • Get an Office 365 Group with each Team Site • PnP Team is helping allow programmatic site, page creation • Very limited branding • No custom headers/footers • Not listed in Admin UI • No “FrontPage” access • Child sites revert to Classic • “No Script” setting Modern Team Sites
• 7.
  demo Modern Pages andWeb Parts • Modern Web Parts • Using Modern Pages in a Classic Site
• 8.
  Good Bad andUgly • A lot of cool new web parts! • Looks great on a phone or tablet • Greatly improved editing experience • Missing web parts! • No List View or flexible Library View • No Content Search or Query • No Content or Script Editor • One column vertical layout  Big and Clunky web parts • No User Custom Actions • Limited configurability (version 1) • Embeds only with IFrame widgets • Ugly gray Modern Pages
• 9.
  Not Available WebParts Not Available • Save Site as Template • Save document library as template • Solution Gallery • Theme Gallery • Help Settings • HTML Field Security • Sandboxed Solutions • SharePoint Designer • Image Maps / Sprites • Uploading files that might contain scripts: asmx, ascx, aspx, htc, jar, master, swf, xap, xsp • BCS web parts • Community web parts • Content Rollup web parts • Document Set web parts • HTML Form web part • Content Editor web part • Script editor web part • Search web parts • Social collaboration web parts “No Script” Setting
• 10.
  demo Modern Lists andLibraries
• 11.
  Good Bad andUgly • Mobile friendly and responsive • Pin items and Filters • Library Tile View • ECB and no-JavaScript CommandUIRibbon actions work • Many custom actions do not work • No custom view styles (e.g. calendar, basic table, document details) • No RSS, Most Popular Items • No Form Web Parts, Customize in InfoPath • No JSLink • No Declare Record or Send To • Export to Excel for lists only, Edge and IE only • No tree view, metadata navigation • No external data columns, publishing columns, • No paste/import from Excel Modern Lists and Libraries
• 12.
  How do Iturn it off? Modern Team Sites • Tenant Level Only Modern Pages • Tenant Level • Web Level * Modern Lists and Libraries • Tenant Level • Site Collection or Web * • List * Requires PnP PowerShell or custom code
• 13.
  demo Controlling the ModernExperience
• 14.
  References Modern Web Partshttp://bit.ly/SPMod-WP Classic vs. Modern Lists/Libs http://bit.ly/SPMod-VsClassic Modern Document Libraries http://bit.ly/SPMod-DocLibs Modern Customization Options http://bit.ly/SPMod-Custom Programmatically creating http://bit.ly/SPMod-Prog Managing Modern Experiences http://bit.ly/SPMod-Manage @Bob1German
• 15.
  An Insight company Thankyou.