Build a robust version of Navigation
CharlotteDowns opened this issue · comments
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
