Office 365 Developer Podcast: Episode 018 with Steve Walker on SharePoint UX developer guidance

Share on Facebook Share on Twitter Share on Linkedin Share via OneNote Share via Email Print

In episode 18, Jeremy Thake chats to Steve Walker, from Office 365 engineering, about developer guidance when it comes to customization the SharePoint user interface.

Download the podcast.

Weekly Updates

Show Notes

Got questions or comments about the show? Join the O365 Dev Podcast on the Office 365 Technical Network.

The podcast RSS has been submitted to all the stores and marketplaces but takes time, please add directly with the RSS

About Steve

SteveprofileSteve Walker is a senior program manager on the Office 365 Customer Adoption team, focusing on developer extensibility and application development scenarios across the Office suite of servers and clients. You can follow Steve on Twitter on @sharepointing.

About the host

An image of Jeremy Thake, a newly appointed tTechnical pProduct mManager at Microsoft responsible for the Visual Studio Developer story for Office 365 developmentJeremy is a newly appointed technical product manager at Microsoft responsible for the Visual Studio Developer story for Office 365 development. Previously he worked at AvePoint Inc., a large ISV, as the chief architect shipping two apps to the Office Store. He has been heavily involved in the SharePoint community since 2006 and was awarded the SharePoint MVP award four years in a row before retiring the title to move to Microsoft.

You can find Jeremy blogging at and tweeting at @jthake.


Useful links

  1. Great show (best yet)! So it looks like with these recent additions to PnP, we’re getting close to being able to make SharePoint fully responsive without using a custom masterpage (e.g. inject bootstrap at run-time, use the custom nav pattern and custom page layouts with bootstrap markup). Just wondering if anyone has tried this and are there any major gaps/issues with this approach?

    • jthake User">

      (adding reply here as thread was also started on Office 365 Technical Network too – )

      I would highly recommend against trying to make SharePoint UI as it stands fully responsive in this way. This is really hacking at the DOM if you’re moving div elements around like that in master pages as the engineering team don’t expect you to do that and this will cause an overhead tax on making sure what you do works as the master pages change…which they will.
      Even if you didn’t change the master page and inject javascript files into the pages using the PnP to purposely try and make pages responsive…essentially you are modifying the DOM which will still lead to these issues as things are updated.
      The Publishing Scenario for Public Web Sites is really a SharePoint Server story right now using Full Trust Code where you have more control over when you update the server that will impact the DOM manipulation you choose to do or Master Page/Page Layout manipulation.
      What we really strongly recommend against is doing these things in standard collab workloads, say for instance in SharePoint Team Sites.
      There will naturally be HR Portals or Corp Comm portals where they mandate customizations but again, just be aware of the customization tax of doing this.

Comments are closed.