jenny.bruce
My feedback
-
88 votesjenny.bruce
supported this idea
·
-
2 votesjenny.bruce
shared this idea
·
-
1 vote
An error occurred while saving the comment -
7 votesjenny.bruce
supported this idea
·
-
1 votejenny.bruce
shared this idea
·
-
5 votesjenny.bruce
supported this idea
·
-
189 votes
We’ve reduced the height of the hero web part when in full width columns, but still maintain as much of the aspect ratio as possible. On a very large monitor this can still make the hero quite tall. Authors could also drag hero our of the full width column, into a one column layout (with gutters) , which significantly reduces the height. How would you imagine it should work differently in the full width, or is moving to a one column layout the right choice for reduced height? Thanks!
jenny.bruce
supported this idea
·
An error occurred while saving the comment jenny.bruce
commented
Agree with many of the comments here - what would be really useful is a compact version that displays all five tiles when positioned in one of the columns in the two column layout. At present only one tile shows when you put the hero into a two column layout column. Users can of course see the other tiles if they use the forward and back buttons that display if they mouse over the hero. Problem is many of our users just won't be bothered to mouse over the hero tile to find more information.
-
11 votesjenny.bruce
supported this idea
·
-
1 votejenny.bruce
shared this idea
·
-
85 votesjenny.bruce
supported this idea
·
-
2 votesjenny.bruce
shared this idea
·
-
22 votesjenny.bruce
supported this idea
·
-
66 votes
An error occurred while saving the comment jenny.bruce
commented
Alternatively, a JSON whiz might put together something that we can use in column formatting?
jenny.bruce
supported this idea
·
-
3 votesjenny.bruce
supported this idea
·
-
3 votesjenny.bruce
supported this idea
·
An error occurred while saving the comment jenny.bruce
commented
I concur with this idea plus this needs to be extended to the ability to create unique views within folders. This is particularly important for Teams where by default documents for each channel in a team are stored in folders in the main document library of the underlying SharePoint site. The other option here would be for the architecture to be changed so that channels have separate document libraries rather than folders in the main document library
-
3 votesjenny.bruce
shared this idea
·
-
20 votesjenny.bruce
supported this idea
·
An error occurred while saving the comment jenny.bruce
commented
I agree with this suggestion, but also think there should be an option for the vertical section to be positioned to the left of the rest of the page layout.
-
10 votesjenny.bruce
supported this idea
·
-
25 votes
An error occurred while saving the comment jenny.bruce
commented
Document library settings are available from the Settings button in the Office 365 bar. This is clearly not intuitive for users. It would probably be better if it were placed in the document library menu. Suggest it be placed under the 'more' (three dots) menu.
-
11 votes
An error occurred while saving the comment jenny.bruce
commented
Agree with this suggestion completely.
Microsoft have made page creation really intuitive, but we still have to train our authors how to go through a series of (to them) complex steps so that they can delete their pages.
For people with a long history with SharePoint, the process is 'obvious', but regrettably in my organisation we have very few people who have the necessary depth of experience.
It's critical that deleting pages be as simple as creating them. If people delete by mistake, then our power users can help people retrieve things from the recycle bin.jenny.bruce
supported this idea
·
@Nicole - This functionality is available if you embed a list on a page. In the list web part settings you can choose to hide the command bar (aka list controls). Granted people can still get to the full list via the see all button but I suspect your mobile users will be happy to use the list you embed on a standard page