Create content to support and encourage users to migrate to v6 of GOV.UK Frontend #4969
Description
Brief
Following the work last cycle to identify users impacted by v6, and ideation how we could address those needs through content and comms, we now looking to create said content.
The user stories we are prioritising are:
- As senior stakeholder / decision maker, I need to know why my team should spend the effort to update, so I can prioritise their time well
- As a designer, I need to understand why changes have been made to colours so I feel confident using them in my service
- As a developer, I need to understand what will break in my service when updating to v6 and what I need to do, so my service continues working for users
A stretch user story, which is dependent on a decision outside of the team, is:
- As a service outside of the GOV.UK proposition, I need to decide how to brand my service, so that I can continue to use the Design System and it's new colour palette
Key messaging
- risks of not updating to the latest version of Frontend
- what will break in v6
- effort / time estimate to update
- tell us about your challenges / barriers to migration
- legacy palette vs refreshed palette, with examples
Channels
- newsletter (v6 preview)
- release comms
Website
- product page or expanded 'What's new' page
- why users should keep GOV.UK Frontend up to date (aimed at teams and decision makers)
GitHub Discussions
- design history for colour changes
- collecting feedback on barriers
- collecting feedback on services outside the proposition
Video conferencing
- community event to introduce v6
Core squad
@calvin-lau-sig7 @seaemsi @owenatgov @Kam-Nijjar
Supporting squad
@kellylee-gds @trang-erskine @MarinaFiliba (for decisions regarding non-GOV.UK users)