Home > Blog > SharePoint Online: Highlighted Content Web Part

If you think that the modern experience ties your hands behind your back and rolling up specific content on your home page is not possible in SharePoint Online, think again…

Like all SharePoint specialists, we are following the SharePoint Online feature updates closely, avidly waiting for new feature releases every month or so, wondering what marvels will be unveiled this time around. The “Modern” page or Site page is at its infancy and until recently I was quite frustrated with it, as the few available web parts did not provide anywhere near the kind of functionality the “classic” web parts provided. They looked fantastic, but that was about it.

It had been a long and arduous journey but by 2013, we enjoyed a great set of tools in the SharePoint Web Parts gallery, especially the content web parts, Content Query (CQWP), Content Search (CSWP) and Search Results. Armed with this trio, we could

  • Provide a dynamic display of content
  • Avoid duplication of content by surfacing any document across sites or site collection
  • Quickly create some great look and feel with Display Templates, all reusable and easy to develop

But more importantly, these web parts also influence the design of the taxonomy and SharePoint architecture, knowing that content can be maintained on any site but surfaced in a Content web part on any page. For example, store and manage your processes and policies on a dedicated site or across multiple sites but show the latest updates on your intranet home page or roll up all your project updates on a Projects home page. The list of scenarios where these web parts can be used is endless.

These tools became an integral part of our design strategy, and we became very comfortable, leading our clients down the metadata path, fearlessly facing the big SharePoint structure monster.But after many years of relative peace, Microsoft introduced a new framework with the modern experience, and here we were, back at square one again. Or so it seemed…

Looking in depth at the new features incrementally added to the modern web parts, we can find our savior in the Highlighted Content web part (HCWP). It could be described as the all-in-one version of the classic content rollup web parts, or a content query web part on steroids.

So, let’s take a closer look at this newcomer.

The search Scope settings:

Just like the CQWP, the HCWP settings allows us to scope our search to a site collection, Site or a specific list or library. But it also offers the option to search across all sites, like the CSWP.

The Query

Based on your search scope selection, the HCWP will offer either to filter by column, or by managed properties, plus some other convenient options. You can add as many filters as you like, which is an improvement over the CQWP. You still need to create Managed Properties if your search extends beyond a specific list or library, but the fact is, we still get this option.

The Presentation options

The presentation options are the equivalent of our display templates of CQWP “Styles”, only the Group Styles or Control display templates. We don’t yet have any options for item display.

What’s still missing…

Property mappings of course!

Maybe not as commonly used as the other settings, the Fields to Display or property mappings in the case of the CSWP allows us to change what column / managed property is displayed for each item preview, take the user to a specific page instead of the item path. This is especially convenient when configuring no code solutions.

The flexibility of Display Templates

For now, we are limited to Cards, List, Carousel and Filmstrip display, and whichever properties are displayed by default for each item. We cannot easily manipulate the displays with groupings, color schemes, and many other personalizations we got used to. But, let’s not forget that:

The simplest SharePoint page designs do not involve complex configuration of web parts templates and the layout options available for the Highlighted Content web part are more than adequate for the SharePoint DIY site owners. And that is the goal after all, empowering users to design their web page themselves.

  • These web parts are totally responsive, on your pc or laptop monitor as well as on mobile devices, so that definitely earns them some points.

Other web part properties not yet available

  • Target audience
  • Web part connections

There is still some ground to cover but this is most certainly tremendous forward progress.

0 Comments

[wpforms id="1422"]
<div class="wpforms-container wpforms-container-full" id="wpforms-1422"><form id="wpforms-form-1422" class="wpforms-validate wpforms-form" data-formid="1422" method="post" enctype="multipart/form-data" action="/blog/sharepoint-online-long-live-highlighted-content" data-token="abf3b5d95ffac1eab434cd3d75764d79"><noscript class="wpforms-error-noscript">Please enable JavaScript in your browser to complete this form.</noscript><div class="wpforms-field-container"><div id="wpforms-1422-field_0-container" class="wpforms-field wpforms-field-name" data-field-id="0"><label class="wpforms-field-label" for="wpforms-1422-field_0">Name <span class="wpforms-required-label">*</span></label><input type="text" id="wpforms-1422-field_0" class="wpforms-field-large wpforms-field-required" name="wpforms[fields][0]" required></div><div id="wpforms-1422-field_1-container" class="wpforms-field wpforms-field-email" data-field-id="1"><label class="wpforms-field-label" for="wpforms-1422-field_1">Email <span class="wpforms-required-label">*</span></label><input type="email" id="wpforms-1422-field_1" class="wpforms-field-large wpforms-field-required" name="wpforms[fields][1]" required></div><div id="wpforms-1422-field_3-container" class="wpforms-field wpforms-field-phone" data-field-id="3"><label class="wpforms-field-label" for="wpforms-1422-field_3">Phone <span class="wpforms-required-label">*</span></label><input type="tel" id="wpforms-1422-field_3" class="wpforms-field-large wpforms-field-required wpforms-masked-input" data-inputmask="&#039;mask&#039;: &#039;(999) 999-9999&#039;" data-rule-us-phone-field="true" name="wpforms[fields][3]" required></div><div id="wpforms-1422-field_2-container" class="wpforms-field wpforms-field-textarea" data-field-id="2"><label class="wpforms-field-label" for="wpforms-1422-field_2">How can we help you? <span class="wpforms-required-label">*</span></label><textarea id="wpforms-1422-field_2" class="wpforms-field-small wpforms-field-required" name="wpforms[fields][2]" required></textarea></div><div id="wpforms-1422-field_15-container" class="wpforms-field wpforms-field-html" data-field-id="15"><div id="wpforms-1422-field_15"><p style="padding-top: 10px; padding-bottom: 10px; font-family: 'Open Sans', sans-serif; font-size: 10px; color: #333333;">By clicking the button below, you are agreeing to our <span style="text-decoration: underline;"><span style="color: #000000;"><a style="color: #000000; text-decoration: underline;" href="https://www.incworx.com/privacy-policy">Privacy Policy</a></span></span>.</p></div></div><div id="wpforms-1422-field_7-container" class="wpforms-field wpforms-field-hidden" data-field-id="7"><input type="hidden" id="wpforms-1422-field_7" name="wpforms[fields][7]" value="SharePoint Online: Highlighted Content Web Part"></div><div id="wpforms-1422-field_9-container" class="wpforms-field wpforms-field-hidden" data-field-id="9"><input type="hidden" id="wpforms-1422-field_9" name="wpforms[fields][9]" value="3.226.241.176"></div><div id="wpforms-1422-field_10-container" class="wpforms-field wpforms-field-hidden" data-field-id="10"><input type="hidden" id="wpforms-1422-field_10" name="wpforms[fields][10]"></div></div><div class="wpforms-field wpforms-field-hp"><label for="wpforms-1422-field-hp" class="wpforms-field-label">Phone</label><input type="text" name="wpforms[hp]" id="wpforms-1422-field-hp" class="wpforms-field-medium"></div><div class="wpforms-submit-container" ><input type="hidden" name="wpforms[id]" value="1422"><input type="hidden" name="wpforms[author]" value="2"><input type="hidden" name="wpforms[post_id]" value="612"><button type="submit" name="wpforms[submit]" class="wpforms-submit " id="wpforms-submit-1422" value="wpforms-submit" aria-live="assertive" data-alt-text="Sending..." data-submit-text="Submit">Submit</button></div></form></div> <!-- .wpforms-container -->