Resolve "blocking" decisions

[CharlotteDowns]

What

Resolve "blocking" decisions needed for the code/design – see comment

Outstanding decisions:

• naming of components and parts (e.g. service header)
• styling of service name link
• response to accessibility issues (e.g. placement of links on desktop)

Why

To help us build Navigation that resolves all issues we've become aware of.

Done when

• Documented all resolutions

[CharlotteDowns]

Decisions

Here is our decision log for other relevant decisions and resolutions.

Naming of components and parts (e.g. service header)

We ran this decision as a question to our steering group and wider community. The consensus was to call the components and pattern the following:

'GOV.‌UK header' component, 'Service header navigation' component and 'Help users navigate a service' pattern

Styling of service name link

We asked the community to help us decide whether we should make the service name a link in all instances. If the decision is 'Yes' we will not change the styling of the service name link as the behaviour will always be the same.

Response to accessibility issues (e.g. placement of links on desktop)

I've added a comment about left-aligning navigation on desktop in issue #3811. I think on desktop we are ok to leave it the way it is currently built with flex.