Microsoft Corporate Vice President Jeff Teper took to Twitter on July 10th to answer questions (and share a bit of news). Summarized below are a few of the interesting questions with my thoughts below the tweet (in order as they happened).
Once again, InfoPath will be replaced. But not yet. The support statement on InfoPath is at https://blogs.office.com/en-us/2014/01/31/update-on-infopath-and-sharepoint-forms/. I cannot believe this is still a question people have to ask.
We're supporting InfoPath but our big focus across Microsoft is PowerApps and Flow as you saw us announce last May and ramp over last year— Microsoft SharePoint (@SharePoint) July 10, 2017
Jeff expanded his answer on this in a video: https://twitter.com/SharePoint/status/884454780369739776
We love Publishing Sites. Shipping Comm Sites V1 this summer & will add more branding, workflow, roll-up, news customization, etc.— Microsoft SharePoint (@SharePoint) July 10, 2017
Reading between the lines here, I expect that Publishing Sites will see no further investment. But the most popular Publishing features will get ported to Communication Sites. (Specifically mentioned was variations.) Sadly, we have no time-frame for those ports, so organizations will need to evaluate Comm sites to see if they meet the requirements. I fear that they won't for many, so Publishing sites will get used, pushing the Comm sites roll out far into the future for those orgs. One of the downsides to shipping minimally-viable products.
I have a number of clients using document sets and it is a roadblock for Modern. This is a confirmation that they will be improved.
Yes doc sets will continue - while we've updated a lot of the UX, we know we have more to and this one a candidate for '18— Microsoft SharePoint (@SharePoint) July 10, 2017
When the Modern UI first started to rollout, the messaging was a bit muddied. This should clear it up -- the classic stuff will be there as long as you need it.
We are going to make it easier to adapt modern sites but if you are running classic sites, we have no plans to turn them off. #TeperTakeover— Microsoft SharePoint (@SharePoint) July 10, 2017
So, while Document Sets will get some attention, Contact Lists will not. I suspect that there are other list templates that will get left behind. If there is ont that is important to you, I suggest getting it on [UserVoice](https://sharepoint.uservoice.com/)!
All sites in SharePoint are future proof but we currently have no plans around Contact Lists. #TeperTakeover— Microsoft SharePoint (@SharePoint) July 10, 2017
Another source of confusion -- how to get the new Communication Sites. Of course, I recommend a separate tenant for first release as a #BestPractice.
Oh and SP Mobile for iOS and Android get native Comm Sites support by end of July— Microsoft SharePoint (@SharePoint) July 10, 2017
So, it is possible to "modernize" a site. If you don't want to wait for an automated switch, you could start creating modern pages and set it as the home page. But, I'm not 100% sure the rollup stuff all works as expected.
Modern pages and parts can go into existing sites and subsites which will get you much of this— Microsoft SharePoint (@SharePoint) July 10, 2017
No hope for Modern UI on-premises anytime soon. But there is a new on-premises version coming as we learned earlier.
Too big a change for Feature Pack. Working on plans for next server which will get part of new UX. Will share when plan baked.— Microsoft SharePoint (@SharePoint) July 10, 2017
As is usual for a general-audience event, just a single mention of development at the end.
Graph API expanding to take on more and more SharePoint to simplify x-MS - will happen in steps and well support both— Microsoft SharePoint (@SharePoint) July 10, 2017
Lastly, Jeff's parting message.