Review a working version of Navigation

[CharlotteDowns]

Brief

By the end of the cycle

We want to have a working version of Navigation in review. It would be good to involve the wider community in an activity as well as conducting a second working group review.

The second working group will make sure the Navigation contribution is usable, consistent and versatile.

Here are some tasks we can probably do as a team:

• have a more detailed version of the guidance
• bring in resolutions from accessibility and design work in the previous cycle

Here are some of the tasks that the steering group can support us with:

• help us in naming the components and pattern.
• assist with accessibility and browser testing
• help write more detailed guidance
• determine a convention to service name linking and associated styles

Aligns with step 5 of the contribution model:

• Build a working version of the thing

In the next cycle

We want to build a robust version of Navigation.

We also worked on step 5 in the previous cycle, Build a working version of Navigation #3738
(#3738)

Epic lead

Charlotte

Driving role(s) as referenced in the team playbook

beeps, Patrick

Supporting role(s) as referenced in the team playbook

Calvin

Further detail

• We have a squad slack group #ds-navigation, we use the canvas for tracking documents we create

Tasks

Team and planning

Beta Give feedback

1. Onboarding new team members to Navigation squad #3778
   0 of 7
   +0
2. Review of Navigation Decision Log, ensure it's up-to-date
3. Plan a working group review #3808
   navigation +1
   

Make needed decisions to resolve blockers, update code where possible, also involving steering group where possible

Beta Give feedback

1. Revisit proposal, update with our current knowledge, and communicate with working + steering groups – Google Doc
2. Set some preferred options for 'naming decisions' and survey the steering group #3809
   +0
   
3. Decide on naming of the components and patterns
4. Examine and resolve accessibility findings #3811
   accessibility navigation +2
   

   
5. Resolve 'unclear service name' accessibility issue – Google Doc
6. Resolve "blocking" decisions needed for the code/design – [see comment](https://github.com/alphagov/govuk-design-system/issues/3795#issuecomment-2115245135)) #3816
   +0
7. Prep steering group to help with browser testing on Service Manual list?

Revise content into 3-page structure

Beta Give feedback

1. Draft a more detailed version of the guidance, based on proposed structure in Padlet #3810
   +0
2. Gather input from working+steering groups on 'best practice' guidance
3. Check the relationship of the new component with existing components in the Design System

Build preview branch of GOV.UK Frontend and preview page

Beta Give feedback

1. Decide on specific variants we present in the component pages
2. Upload content and examples into branch of DS website
3. Build preview branch of GOV.UK Frontend, build the coded examples to be used in "preview pages" for review

[calvin-lau-sig7]

From @querkmachine: main outstanding decisions needed:

• 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)