TWE-9 - BE - Featured services block (Division page)

[SharmaineLim]

Link to Ticket

Description of Changes Made

This ticket adds a new block for signposting to featured services from the division page.

FE styling was done in #340 and has been merged in. You can view only BE changes by clicking here.

Additional changes

Add an explicit field for accessible link/button text because having a descriptive link text is visually less appealing.

How to Test

1. Create/Edit a division page.
2. Try to add a new block in the Body field. You should see "Featured services" as a block.
3. Adding the "Featured services" block and filling in the required fields should display the new content on the preview.

Screenshots

Division page editor

MR Checklist

• Add a description of your pull request and instructions for the reviewer to verify your work.
• If your pull request is for a specific ticket, link to it in the description.
• Stay on point and keep it small so the merge request can be easily reviewed.
• Tests and linting passes.

Unit tests

• Added
• Not required

Documentation

• Updated build docs
• Updated editor guidelines (See https://intranet.torchbox.com/torchbox-com-project-docs for the private link, for Torchbox employees only)
• Updated field spec (See https://intranet.torchbox.com/torchbox-com-project-docs for the private link, for Torchbox employees only)
• Not required

Browser testing

• I have tested in the following browsers and environments (edit the list as required)
  • Latest version of Chrome on mac
  • Latest version of Firefox on mac
  • Latest version of Safari on mac
  • Safari on last two versions of iOS
  • Chrome on last two versions of Android
• Not required

Data protection

• Not relevant
• This adds new sources of PII and documents it and modifies Birdbath processors accordingly

Light and dark mode

• I have tested the changes in both light and dark mode
• The change is not relevant to dark and light mode

Accessibility

• Automated WCAG 2.1 tests pass
• HTML validation passes
• Manual WCAG 2.1 tests completed
• I have tested in a screen reader
• I have tested in high-contrast mode
• Any animations removed for prefers-reduced-motion
• Not required

Sustainability

• Images are optimised and lazy-loading used where appropriate
• SVGs have been optimised
• Perfomance and transfer of data considered
• If JavaScript is needed alternatives have been considered
• Not required

Pattern library

• The pattern library component for this template displays correctly, and does not break parent templates
• The styleguide is updated if relevant
• Changes are not relevant the pattern library

[SharmaineLim]

@helenb @albinazs What are your thoughts on me adding a new field explicitly for accessible link text?

I tried having a descriptive link_text (i.e. "Read more on out charity services") on staging but it doesn't look great, and appending {{ link_text }} about {{ heading }} division can get a bit clunky depending on the content of link_text.