What

Get something working in Frontend, close SPIKE issue 4915, start a new branch of Navigation contribution. Consideration for mobile first development. Transferring the spike into production code.

Pair developers to introduce Design System ways of working and codebase.

Determine actions from build related decisions in Decision Log

Work includes:

• Building a navigation component - essentially the grey bar with a service name and some links with similar functionality to the current header.
• Figuring out what we need to change about the current header
  • Deprecating links?
  • Do we want to the rearranging as part of this work?
  • Figure out One Login
• Doing some “things between the GOVUK bar and the service navigation bar” exploration (phase banners, emergency alerts, etc)
• Figuring out who’s actually using our header without any customisation? Including libraries which just reimplement our component

Help from the team:

We’ve currently wrapped the One Login links in “things we don’t want to implement” in the decision log, but that integration feels like a fairly major part of what we’re doing. It’d be good to get a decision on how we work with/proceed on One Login stuff.

Why

More detail

Done when

• SPIKE 4915 is closed
• new branch for Navigation component opened
• have navigation component as it's own separate component
• decide on whether navigation will sit within the element – desk research, documenting considerations and accessibility concerns of doing so
• build the thing (logo in a black bar, service name and nav links in a grey bar)
• write up decisions that we need to make to move forward
• have it working for mobile
• have it working for desktop
• plan for testing

Steering group done whens

• put toolbox idea in front of the steering group