Forum Discussion
Modern sites - news webpart limitations
Hi - I'm about to launch a new intranet based on communication sites and finding lots of limitations with the news web part 1) The owner of my homepage would like to be able to identify news arti...
For 1) Try using the + Show/Hide columns option in the All Pages view of Site Pages. You can only expose Promoted State from the "modern" experience. Once you have it showing, you can group by Promoted State (again, from the modern experience) and then use Save As to save the view. I usually save it to All Pages and then make that the default. That makes it easy to find News pages. I haven't found a way to do (2), but should be able to add a SortOrder column (it might have to be a site column) to the library and then map it to an available RefinableStringxx column and use Highlighted Content to create your own list of articles. For (3), I've been using Highlighted Content to organize news articles and filter them with naming conventions (e.g. People Spotlight) but if your site structure follows "the world is flat" model, it won't matter whether news is site or site collection - because you won't have sub-sites. Once Hub Sites are available (Q1 2018), you will be able to roll up news from a family of sites on to the Hub. And from SharePoint home, users see all the News from sites they follow and those suggested by the Graph. News experiences are evolving but with some planning, what we have today is a really great start.
Thanks so much for your help Susan. I had promoted state to be a lookup field (from promoted state) but when I changed that to be calculated as =promotedstate instead it solved the problem and I've now created a view grouped as you suggested which is exactly what our news editor needs.
I hadn't heard about Hub sites coming but will check them out too.
One last thing which is strange on (3) is that all our news stories in the highlighted content web part have in small text the site that they have come from (eg. Intranet Home) above the headline. This is a separate hyperlink that if clicked on just opens the site pages directory which obviously isn't a very good user experience and is confusing for users. Is this something that happens on your site? It never used to be there so I'm not sure what has caused this to suddenly appear.
I've attached a screenshot here if that didn't make sense.
Thanks again for your most helpful response!!
Ian, that link under the graphic and above the headline on our news items all show the correct URL for the site:
https://(name).sharepoint.com/teams/(sitename)
The link to the news sites are all under the /SitePages/ link (and also embedded in the graphic):
https://(name).sharepoint.com/SitePages/(sitepage).aspx
Hi Andrew
I wonder if that's because you are using a team site whereas I'm using a communication site?
The URL above the headline on my communication sites is
https://(name).sharepoint.com/sites/(sitename)/sitepages/
Which is really confusing for users who then see a page of site contents, most of whom then have no idea what they are looking at.
Interestingly some of my older news articles are missing this link under the graphic. I'm wondering if flipping the news webpart to select from 'site' to 'site collection' might be what first made them appear although switching back to 'site' doesn't now remove them.Hi Ian
Just to be clear, both our team and communication sites have the same URL for the news items, both under sitepages. Both include the name of the news page (below as 'newsitem.aspx'):
Communication Sites:
https://(name).sharepoint.com/sites/(sitename)/SitePages/newsitem.aspxTeam Sites:
https://(name).sharepoint.com/teams/(sitename)/SitePages/newsitem.aspxAre you saying that this link on your site doesn't include the news page name, just a link to the general 'sitepages' library?
Hi Andrew - See the attached diagram for a clearer explanation. Things are fine if people click on the news headline
The problem is that when people hover over the site (above the headline) it changes colour - if they click on it they then just get the directory of site pages organised by author leading to end user confusion... I would never want them to see this page.
