Skip to content

Conversation

@louisearchibald
Copy link
Contributor

@louisearchibald louisearchibald commented Dec 17, 2025

Resolves JIRA: WS-1883

Summary

Bringing the ScrollablePromo component out of legacy and in line with our modern component standards. The component has been renamed to ArticleLinksBlock as we have also updated the existing scrollable cards styling entirely and have replaced it with a stacked card format to reflect new designs given by UX (see screenshots below).

LTR:

Screenshot 2025-12-30 at 17 11 23

RTL:

Screenshot 2025-12-30 at 17 10 52

Code changes

  • Moved and renamed the component from ScrollablePromo to ArticleLinksBlock.
  • Removed leftover experiment code from a previous experiment that ran on this component.
  • Updated imports and references to reflect new component name change.
  • Implemented Typescript to relevant files.
  • Removed scrollable styling and renamed some variable names.
  • Updated existing margin/padding values to match newly specced designs.
  • Added Chevron component to src/app/components/ArticleLinksBlock/Promo/index.tsx.

Developer Checklist

  • UX
    • UX Criteria met (visual UX & screenreader UX)
  • Accessibility
    • Accessibility Acceptance Criteria met
    • Accessibility swarm completed
    • Component Health updated
    • P1 accessibility bugs resolved
    • P2/P3 accessibility bugs planned (if not resolved)
  • Security
    • Security issues addressed
    • Threat Model updated
  • Documentation
    • Docs updated (runbook, READMEs)
  • Testing
    • Feature tested on relevant environments
  • Comms
    • Relevant parties notified of changes

Testing

  • Manual Testing required?
    • Local (Ready-For-Test, Local)
    • Test (Ready-For-Test, Test)
    • Preview (Ready-For-Test, Preview)
    • Live (Ready-For-Test, Live)
  • Manual Testing complete?
    • Local
    • Test
    • Preview
    • Live

Additional Testing Steps

  1. Spin up a local server and visit http://localhost:7081/hausa/articles/c07d7nmm1e4o?renderer_env=live to see the component on a local article page.

Useful Links

@louisearchibald louisearchibald self-assigned this Dec 17, 2025
louisearchibald and others added 20 commits January 8, 2026 13:22
…rds' of ssh://github.com/bbc/simorgh into WS-1883-bring-article-link-block-up-to-component-standards
…rds' of ssh://github.com/bbc/simorgh into WS-1883-bring-article-link-block-up-to-component-standards
…rds' of ssh://github.com/bbc/simorgh into WS-1883-bring-article-link-block-up-to-component-standards
css={styles.labelComponent}
id={ariaLabel}
data-testid="eoj-recommendations-heading"
dir={dir}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just checking on the reintroduction of dir, is this because Storybook/Chromatic showed the label in the incorrect position on RTL? I feel like thats more of a Storybook problem as it can sometimes set the root dir to ltr even if you set the service to something like arabic by default.

If you remove these dir attributes and test locally/preview, is the label still in the correct position?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and I couldn't fix it any other way so I reinstated it! 😓 I will remove it again though if it's just a storybook problem. I didn't realise that can sometimes be a problem, drove me bananas yesterday. 😅

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries! I can take a look and see if theres anything obvious in storybook to help fix the display. It can just be a bit temperamental from memory.

@amoore108
Copy link
Contributor

Super minor but could the 2 fixture data files be .ts files?

Otherwise looks good!

…rds' of ssh://github.com/bbc/simorgh into WS-1883-bring-article-link-block-up-to-component-standards
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants