Create a GitHub Discussions space for Exit this Page

[kellylee-gds]

What

Create a GitHub Discussions space to collect user feedback and research findings on specific aspects of Exit this Page component and pattern.

Why

so we can learn how it is being used in services and iterate accordingly.

Who needs to work on this

Kelly

Who needs to review this

Steve, Katrina

Done when

• [x] Revisited GitHub discussions documentation
• [x] Identified appropriate host location
• [x] Agreed discussion threads
• [x] Published

[calvin-lau-sig7]

Summary of what I reckon how the links for #2848 and #2849 will look on the component and pattern pages:

On the ‘Help improve this component/pattern section’, replace the link to the backlog issue page (example) to a new GitHub discussion category (example) page.

• Discussion category will be the main space for users to discuss Exit this page and for the team to make announcements, making use of the discussion features
• Backlog issue page will probably still be needed for consistency and findability for people browsing the backlog repo, but will be locked down and with text redirect users to the discussion category. This is to reduce duplication and confusion on where to go.

In the same section, also add a button to a survey or form tool:

• Survey or form will collect info about their implementation of Exit this Page, also service name, organisation, contact email, and questions asking which other components and patterns the use.

[kellylee-gds]

Draft content

[36degrees]

Thinking ahead a little, in case this works really well and we want to roll it out to the other components and patterns.

I don't think we'd want a category for each individual component / pattern – especially if we wanted to start including space for all the 'unpublished' things in the backlog. That would be far too many categories.

Could we instead use an exit this page label to group discussions, and link to the discussions filtered by that label?

[kellylee-gds]

@36degrees So we've chosen Discussions specifically because we want to be targeted in the feedback we ask for (to explore some of our riskier assumptions with the EtP mvp).

My current draft for mvp of this is here.

This might be out of scope for this exercise because we'd need to tidy up the existing Discussions threads, but longer term we could have Discussions grouped by types of feedback we want to collect and then filtered by component / pattern / style labels?

[kellylee-gds]

@calvin-lau-sig7 your above proposal sounds great for mvp. If we see users are struggling to find the appropriate place to share feedback on EtP, then we can reconsider and iterate 👍🏻

In my absence, can you please create the Discussion threads on govuk-design-system repo ready for when we ship, thanks!

[calvin-lau-sig7]

No problem, I'll work with @Katrina-Birch on this to post the discussions we need.