Summary
Review the existing Euros 2024/2025 tournament nav/header implementation and adapt it for World Cup 2026, while identifying low-cost changes that move it closer to a reusable/configurable pattern.
Why
The tournament nav/header is a core part of tying together different editorial experiences related to the World Cup. The immediate priority is to get a working version based on previous implementations of headers/nav up and running, but this should also be an opportunity to make pragmatic improvements that reduce future rework.
Where possible, we should structure the implementation so that values can be hard-coded for launch but are easy to make dynamic/configurable and reusable through editorial tooling later.
Scope
- Review the Euros 2024/25 tournament header/nav implementation
- Identify the changes needed for World Cup 2026
- Assess whether the implementation can be structured in a way that improves future reusability/configurability without adding significant complexity or launch timeline risk
- Make any low-cost changes now that support that direction
- Document anything that should remain hard-coded for launch (to minimise complexity) but could be made dynamic/configurable later
Examples
- Hard-code navigation labels, links or tournament metadata for now, but structure them so they can later be moved into editorial tooling/config
- Preserve the existing implementation approach where that is the fastest route, unless managable changes now would clearly make later reuse easier
Out of scope
- Building full editorial configuration through tooling as part of this ticket
- Redesigning the header/nav beyond what is needed for World Cup 2026 launch
Deliverables
- Updated World Cup 2026 header/nav implementation, or a clear recommendation for the implementation approach
- Short note on what was done to support future reusability, if anything
- Follow-up tasks for anything intentionally deferred due to time constraints
Acceptance criteria
- Euros 2024/25 implementation has been reviewed
- World Cup 2026 requirements/updates are identified
- A pragmatic decision has been made on whether to keep the current implementation pattern or adjust it slightly to better support reuse later
- Any low-cost structural improvements have been made where worthwhile
- Deferred follow-up work is clearly documented
Notes/links
Summary
Review the existing Euros 2024/2025 tournament nav/header implementation and adapt it for World Cup 2026, while identifying low-cost changes that move it closer to a reusable/configurable pattern.
Why
The tournament nav/header is a core part of tying together different editorial experiences related to the World Cup. The immediate priority is to get a working version based on previous implementations of headers/nav up and running, but this should also be an opportunity to make pragmatic improvements that reduce future rework.
Where possible, we should structure the implementation so that values can be hard-coded for launch but are easy to make dynamic/configurable and reusable through editorial tooling later.
Scope
Examples
Out of scope
Deliverables
Acceptance criteria
Notes/links