Gregg M
My feedback
-
354 votesnot in our plans right now ·
AdminSites Product Team
(Product Owner, Microsoft SharePoint)
responded
Thanks for making this suggestion. We don’t currently have plans to implement this, but would love to better understand the scenarios and need.
Do you expect that people are deleting pages, or changing pages/content names frequently enough that they’re breaking other pages/content without knowing it?
Is the site owner responsible for fixing that content or the authors/editors moving the content around?An error occurred while saving the comment Gregg M
supported this idea
·
-
277 votesGregg M
supported this idea
·
-
11 votesGregg M
supported this idea
·
-
231 votesnot in our plans right now ·AdminSites Product Team
(Product Owner, Microsoft SharePoint)
responded
We don’t intend to support hiding hub navigation per site, however there are a few key solutions you can use (now and soon):
Audience targeting in navigation https://support.microsoft.com/en-us/office/target-navigation-news-and-files-to-specific-audiences-33d84cb6-14ed-4e53-a426-74c38ea32293
We’re working on delivering global navigation, you can read more about it in this blog post: https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/innovations-for-workplace-communications-and-employee-engagement/ba-p/1696149
Gregg M
supported this idea
·
-
324 votesnot in our plans right now ·
AdminSharePoint Sites & Collaboration
(Admin, Microsoft SharePoint)
responded
Thank you for the feedback. Creating a Modern Content Editor Web part is not in our plans right now
An error occurred while saving the comment Gregg M
commented
Although a bit extreme, you could use a React Content Query Web Part to insert custom script and CSS like many used CEWPs for in the past. We are using this on our site, and in some cases I inject CSS for OOB web parts to modify where this is otherwise not possible.
https://github.com/pnp/sp-dev-fx-webparts/tree/master/samples/react-content-query-webpart
-
349 votesworking on it ·
AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, 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.
Gregg M
supported this idea
·
-
378 votes
We’ll be updating the Image gallery web part on modern pages shortly to display images dynamically from a document library, if you have that library backed by a CDN.
Gregg M
supported this idea
·
-
484 votes55 comments · Sites and Collaboration » App bar & navigation · Flag idea as inappropriate… · Admin →Gregg M
supported this idea
·
-
482 votesGregg M
supported this idea
·
-
580 votes
Thank you for everyone’s feedback around the use of white space on modern pages. We are continually looking for ways to refine our designs and the use of white space is an important part of this. While the custom control of sections or the custom control of columns is not likely to happen, there could be other optimizations we will be thinking about in the future. Thank you.
An error occurred while saving the comment Gregg M
commented
I've been using Custom Extensions to "Inject Custom CSS" on SharePoint Online. This works, but we shouldn't have to go to measures like this to tighten up the white space. We are at a constant risk of Microsoft updating their pages and breaking the Custom CSS enhancements.
I realize I do this at my own risk, but I'm doing it because it's needed and Microsoft isn't giving us the options to tighten (or loosen) the web parts and white space.
Gregg M
supported this idea
·
-
2,260 votes
Thanks for the suggestion. While this can accomplished via PnP Powershell today, we understand the desire to have a way to do it in the UX. We’ll add it to our backlog.
Gregg M
supported this idea
·
-
1,913 votes
In modern pages, we open links within SharePoint in the same tab by default, and external links in a new tab. In the text web part, users can specify to open links in a new tab, but that isn’t the default behavior. Similarly, for navigation links, they follow the same rule (within SharePoint, same tab, external to SharePoint in a new tab). This is true of the modern web parts that support linking as well (hero, quick links, images, etc.) This is the pattern we’ve adopted for consistency.
After reviewing other areas of modern sites, like the site pages library, document libraries, lists, site contents, etc. we did find some different opening behaviors which we’ll review and resolve.
Can you help us understand if this pattern isn’t meeting your expectation, if we have some inconsistencies within modern pages we’ve missed, or if it’s the other areas of modern sites where…
Gregg M
supported this idea
·
-
2,362 votesworking on it ·AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
We are continuing to make our large list experiences better, please keep the feedback coming.
Spring 2018 update:
- We now support being able to manually add indexes to lists of any size (increased from lists up to 20,000 items previously).
- Starting with the February release of the Office 365 Excel client, you will be able to export your full list instead of getting cut off part of the way through.What we are working on now:
- Predictive indexing will start to work for lists larger than 20,000 items so your views will automatically cause the right indexes to be added to your lists.In our backlog:
- Being able to index/sort/filter by lookup column types (like person, lookup or managed metadata columns) without being throttled.
- Making sure that our REST APIs support querying in ways that will guarantee that the call will not be throttled.For…
Gregg M
supported this idea
·
-
527 votes
An error occurred while saving the comment Gregg M
commented
I've been using Custom Extensions to "Inject Custom CSS" on SharePoint Online. This is essentially hacking the default CSS to give us custom fonts. For the most part it works, but it also breaks icons in the least expected areas, which requires yet more CSS hacks.
Please give us the ability to change system fonts, seems like a basic request.
Gregg M
supported this idea
·
-
88 votesGregg M
supported this idea
·
-
463 votes
Thanks you for the suggestion. We’ve discussed adding additional column layout options (e.g. 4 columns, the specific example provided by the initial suggester 25/50/25, etc.) If we wanted to keep pages consistent (so there aren’t 50 layouts), but allow additional flexibility, what would be the next three layout choices you’d add? Thanks!
An error occurred while saving the comment Gregg M
commented
To Site Product Team. If you added just the 4 column, and the 25/50/25, that would be enough in my humble opinion.
An error occurred while saving the comment Gregg M
commented
There is a way to do a 25-50-25 layout.
1. Edit the page and go to Section Layout
2. Add a Vertical Section
3. Change your page layout to One-Third Left columnThis gives you a smaller column on the right and left, and a larger column ~50% in the middle. This also expands the sections so that it uses more of the screen. Less white space on left and right sides.
The disadvantage here is that the "Vertical Section" goes all the way down the page, regardless of how many additional sections you have.
Not ideal, but it works.
An error occurred while saving the comment Gregg M
commented
25-50-25
An error occurred while saving the comment Gregg M
commented
This is a big one for my team too. We would love to see the 25/50/25 layout.
Gregg M
supported this idea
·
-
6 votesGregg M
supported this idea
·
-
397 votesGregg M
supported this idea
·
-
4 votesGregg M
supported this idea
·
-
117 votesGregg M
supported this idea
·
Microsoft, a broken link checker should be a core feature of any web content management system.
I can't believe you even launched this product without a broken link checker and still do not "currently have plans to implement this" and need "scenarios" to understand why.
Ultimately you are right, the "site owner" or "authors/editors" are responsible for fixing broken links in their content, but not all site owners control every site, nor do they even know to do this or have the time to do this in most cases.