Review how we indicate component lifecycle

[GCHQ-Developer-718]

What component is this related to?

All

Description

Acceptance criteria

Consider the following and make any required updates

• Review the releases and versions page and check canary/beta information is up to date
• Do we need the full paragraph about canary components on the guidance page or is a sentence in the alert and a link to further information sufficient?
• Consider whether we should use an alert or alternative component on the component pages for beta components, as there is currently no easy way to find out what beta actually means. Note that all non-canary components are currently in beta. It would need to be distinct from the canary one so users don't get used to seeing it and not notice the canary one.
• Add the canary component alert to all tabs on the component page (e.g. code, accessibility)

Why do we need it?

Ensure users can make an informed choice about whether to use a new component in an application

🚨 Urgency (low, medium or high)

Priority 3

Related open issues

[Link to other GitHub issues]

[mi6-577]

Could this be as simple as a compact stepper near the top of each component page to show the current place in the component lifecycle?