Max Duval

Bump Node to v14.20.0

4

## What does this change? Bump Node to the latest LTS version Fermium: [v14.20.0](https://nodejs.org/es/blog/release/v14.20.0/) ## Why? Keep things up-to-date.

We should ensure that our `` elements have a label. Follow-up on #5036 > ## Multiple landmarks > > If there is more than one complementary landmark role or [](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/aside)...

> **Note** > Follow-up on #5930 If we don’t support an article type (Immersive, Quiz), we should redirect amp.theguardian.com URLs.

Rotate adops AWS key

1

@OllysCoding to provide context

fix(Switches): organise owners

1

## What does this change? Remove people that have left the organisation. Use groups over individuals where relevant. Is the owners field relevant, if it most of the time identical...

Currenty, all the switches are `AtomicBoolean` individually stored in memory. It would be probably beneficial to simplify the logic to simply rely on the Properties of the S3 config.

Bump standard library to v180

2

## What does this change Bump the specified standard library to v180, which is compatible.

Yarn 1 is no longer supported. We should consider: - NPM - PNPM - Yarn 4 See https://github.com/guardian/csnx/discussions/445

Top nav improvements

1

Here’s a series of step I think we should take to follow-up on https://github.com/guardian/dotcom-rendering/issues/6436 : - Remove the [`headerTopNav`](https://github.com/guardian/frontend/blob/0a32dba0b76eb63ab7babe946ce00854f0bd9034/common/app/conf/switches/FeatureSwitches.scala#L496-L504) switch - Refactor the [`headerContent`](https://github.com/guardian/frontend/blob/0a32dba0b76eb63ab7babe946ce00854f0bd9034/common/app/html/HtmlPage.scala#L32-L35) logic to only have two possible...