Build a robust version of Navigation

[CharlotteDowns]

Brief

By the end of the cycle

We want to address issues raised by working group and get the guidance and code ready to publish. We want to establish with developers from One Login how we adopt their component into the proposed GOV.UK header component.

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

• host a post-review session with the working group (sometime w/c 1 July 2024)
• review the code and guidance (2i)

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

• in-depth browser testing
• in-depth accessibility testing
• detailed design tweaks

Aligns with step 5 of the contribution model:

• Build a robust version of the thing

In the next cycle

We want to publish Navigation 🏁.

We worked on step 6 in the previous cycle, Review a working version of Navigation #3795

Epic lead

Charlotte

Driving role(s) as referenced in the team playbook

beeps, Calvin, Brett, Ciandelle

Supporting role(s) as referenced in the team playbook

Anika, Izabela

Further detail

• Here is the Navigation proposal sent to the working group
• 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. Confirm working group review call date (week 1) #3847
   contribution navigation +2
   
4. Establish relationship with One Login coded examples (week 1) #3846
   contribution navigation +2
   

Guidance

Beta Give feedback

1. Decide on way to present 'other elements' guidance in Navigation pattern (all cycle) #3833
   +0
   
2. Confirm we have all guidance that supports development (week 2 / 3) #3871
   0 of 4
   contribution navigation +2

Development

Beta Give feedback

1. Organise and chat with One Login developers (week 1) #3850
   contribution navigation +2
   

   
2. Implement accessibility suggestions
3. Perform browser testing on Service Header component #3836
   contribution navigation +2
   

Accessibility

Beta Give feedback

1. Examine and resolve accessibility findings #3811
   accessibility navigation +2
   

   

Design

Beta Give feedback

1. Preview branch of Design System website (week 1) #3852
   contribution navigation +2
   
2. Finalise design, spacing and function (week 1 / 2) #3873
   contribution navigation +2
   
3. Revisit proposal and communicate with working + steering groups #3824
   contribution navigation +2
   
4. Enable session to feed in Design and Development decisions in to guidance that have been decided (week 2) #3875
   contribution navigation +2
   
5. Decide and add things we want to learn to Github discussions (week 3) #3880
   +0