Use visual web parts to make content more engaging

Microsoft 365 and Atlas both provide many visual web parts that can be used to draw attention to particular content. Sometimes you may need to provide information that is very text-heavy, but you can use imagery to keep users engaged, or split the information into smaller chunks on separate pages and use the Quick Links or Related Knowledge web parts for example to make it easy to find related information.

Web parts such as HoverPoint, Hero and Call to Action and more can be used to make pages more visually appealing and therefore more engaging to users.

Tips on how to improve engagement using web parts

• Imagery makes the difference: Use images that are simple but eye catching. You want to attract your user’s eyes to the call to action, so we recommend making use of color and simple images that make it stand out. If you want users to use branded images in their content make sure you have configured an Organisation Assets library and uploaded images to it.
  • Learn more: Configure an Organisation Assets location for images
• Don’t use button labels such as ‘Click Here’: In terms of accessibility and usability best practice, we recommend that you rather use descriptive and action-orientated labels such as ‘Register Now’ or ‘Reserve Your Seat’.
• Keep descriptions short when there is limited space: If your copy is too long, some web parts may truncate (shorten) your text - for example the Call to Action web part. Make sure your text will fit in the expected area or move the web part to a wider column on the page.
• Don’t use the Call to Action Web Part for links: Some authors want their link to get noticed so they use a call to action to promote it. This isn’t the best way to get content promoted. Consider using other web parts like Mandatory Reads or Quick Links in filmstrip mode. 

• Don’t have too many similar web parts on each page: Remember, the whole point of using visual web parts is that you want to draw attention to something important. Having too many CTAs for example on one page will make them less effective as they will be competing for attention. We suggest having some governance both in terms of how many you can have on a page and where they should be positioned.

Example use cases

• Expertise - Instead of using Text web parts to list / link to contacts for particular expertise areas, use the People web part to show their profile cards
• Promoting content - Instead of using Text web parts to provide links to interesting content you have a number of better options:
  • Use some Link web parts,
  • Use the Quick Links web part,
  • Use the Hero web part,
  • Use the Atlas Spotlights (In Focus) web part