Use anchor tags for feed

[bryophyta]

What does this change?

The main change is to refactor the feed view so that it uses a list of links (<a> tags) instead of a table:

• Clicking on an item is more like navigation than on-page action, as it takes you to a view corresponding to a different URL
• Allows us to leverage the platform for cmd+click behaviour etc.
• Also allows for more control over layout of the cards, without having to wrangle too much with Eui. In particular, it makes it easier to have a more compact layout.

Additional changes:

• Add scroll-into-view behaviour (again, easier when we're not competing with Eui's features for this, I think)
• Adapt the card heading to use an <EuiBadge> to display supplier info, rather than including it at the end of the headline/slug.

How to test

How can we measure success?

Have we considered potential risks?

Images

Before and after

Accessibility

• Tested with screen reader
• Navigable with keyboard
• Colour contrast passed
• The change doesn't use only colour to convey meaning

[github-actions]

Deploy build 612 of Editorial Tools::News Wires to CODE

All deployment options

• Deploy build 612 of Editorial Tools::News Wires to CODE
• Deploy parts of build 612 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[bryophyta]

re-implements some of #81

[sb-dev]

It might be worth moving the Link component to it's own file.

[bryophyta]

currently it's defined within the scope of SearchContext because it needs to access pushConfigState, so if we pulled it out to a separate file we'd need to pass the push function as an argument when constructing the Link component.

Given that we don't currently have a need for multiple Link components with different push functions, I'm inclined to leave it defined inside SearchContext -- what do you think?

[sb-dev]

You can to use handleSelectItem to update the config state?

[bryophyta]

feels like this point is worth a synchronous chat? I'll send you an invite 👍