860 votesworking on it · AdminSharePoint Experiences Team (email@example.com, Microsoft SharePoint) responded
We are hard at work on this capability now. We’ll release it early next year.
149 votestell us more · AdminSharePoint Experiences Team (firstname.lastname@example.org, Microsoft SharePoint) responded
Thanks for the feedback. It would helpful to know the specific scenarios where users aren’t able to get to the content they need.
We’ve observed that with sites shared publicly, or sites attached to a public Office365 Group, it’s not very meaningful to see every SharePoint Site a user can access, because there could be a huge number, most of which the user isn’t interested in.
Is the focus here more like “show me all sites I’m a member of”?
There is one comment that says search isn’t working, please open a support ticket for that.
177 votesthinking about it · 10 comments · Sites and Collaboration » Site Scripts & Site Designs · Flag idea as inappropriate… · Admin →
230 votesworking on it · AdminSharePoint Experiences Team (email@example.com, Microsoft SharePoint) responded
We are currently working on an Image gallery web part that would meet those requirements.
257 votesworking on it · AdminSharePoint Experiences Team (firstname.lastname@example.org, Microsoft SharePoint) responded
A consolidated admin view of where published content types are being used is still being evaluated, but for folks voting for the related use case of “better creation and management of content types” please refer to site designs (aka.ms/spsitedesigns) as a modern mechanism to create/apply content types to site libraries. We are also looking at how this could be more easily supported from hub sites.
We’re working on this! The first web part we’re enabling it on is the News web part, followed by the highlighted content and events web parts. We’d love to hear about other audience targeting scenarios you’d like us to enable. Thanks!
It has taken us longer than we expected, but the feature is in development and as noted in comments was demo’d at Ignite 2018. We expect to start rolling out by January 2019.
Thanks for flagging this one — we are working jointly with MS Teams on a solution for keeping consistency when you rename a channel in Teams. Don’t have an ETA to share yet.
Thanks for your feedback! Just a note to let you know that we’re building your suggestion now.
Corporate lifecycle is a real and constant pressure in business, often resulting in a need to rename the Office 365 Tenant. To that end we are working on the solution to change the SharePoint domain URL (contoso.sharepoint.com renamed to fabrikam.sharepoint.com). This capability will also then enable the renaming of an individual site collection (contoso.sharepoint.com/sites/abc to contoso.sharepoint.com/sites/xyz).
While we don’t have an estimated delivery date to share at this time, we’ll update your suggestion with details as they become available.
Bill Baer MSFT
We’ve recently released new Title area layout options for modern pages which will allow you to make the title area both much smaller, or showing a larger image. This does not impact the Site header above the pages. However we are also working on other options for different Site header sizes also.
This was just demoed at Ignite 2018 session BRK2136. Read more about it : https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Build-your-modern-intranet-with-SharePoint-in-Office-365-Ignite/ba-p/255453Grant commented
Ideally a Communication site, but even a Modern Team Site (without associated o365 group) would be ok.
Still think it's crazy that you can't do this - would have thought that the root site collection would have been the first one to allow for the Modern Sites as it's almost every tenant's landing page.