Update backlog page

[christopherthomasdesign]

This PR updates the backlog page to:

• rename it 'Upcoming components and patterns'
• show what we're working on and what we've prioritised to work on next
• link out to a re-structured backlog repo that hosts discussion about all the other non-prioritised things

The idea is that we use the website to communicate what we're working on and what we're working on next. And we're removing the statuses / project stages from the backlog and re-framing it as a discussion space.

Reviewers should review the page itself, but also look at the content for the new Github discussions about our 3 priorities, and the re-structured backlog. We'll be sending out comms to notify the community that this has changed.

When we publish the new page, we'll need to change the new backlog project board's permissions – it's currently private.

Part of https://github.com/alphagov/govuk-design-system/issues/2310

[netlify[bot]]

✅ You can preview this change here:

Name	Link
🔨 Latest commit	57034ea290538c6b8fb22f558fb83158140f75fd
🔍 Latest deploy log	https://app.netlify.com/sites/govuk-design-system-preview/deploys/6345877bb3a613000a950acb
😎 Deploy Preview	https://deploy-preview-2354--govuk-design-system-preview.netlify.app/community/design-system-working-group
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[36degrees]

Reviewers should review the page itself, but also look at the content for the new Github discussions about our 3 priorities, and the re-structured backlog. We'll be sending out comms to notify the community that this has changed.

A couple of thoughts on the discussions:

• Have we considered moving the discussions into the Design System repo? Thinking if we wanted to use discussions for something else (like sharing updates, technical proposals etc) it might make sense to have everything in one place and use categories to separate them.
• It looks like we're planning on potentially having multiple discussions relating to the same component which I am very on board with. Could we use labels to group them together and to improve discoverability? (We'd need to create new labels for the prioritised components)

On the project board:

• It'd make more sense to use the Status field to separate components into published / not published, rather than the label.
• We could also add a new 'Type' field to split things into components, patterns and styles – the advantage of this over labels is that the project knows that these concepts are related to each other, so you can e.g. group things by their type, which you can't do with labels.

Give me a shout if it'd be useful to talk about discussions and/or projects in more detail!

[christopherthomasdesign]

Thanks for looking @36degrees, these are all good suggestions! Will have a play around with it today. I hadn't considered putting discussions in the Design System repo, does kinda make sense.

[christopherthomasdesign]

Ok, based on the above, I've:

• moved the discussions into the Design System repo
• added labels to each discussion so they can be grouped with other related discussions in the future
• used the status field in the backlog repo to show whether something is published or not

I decided against using the 'type' field for components, patterns etc, but only really because it's a bit of a faff and I'm not sure how much of a need there is for it. We can obvs change this in the future if we think it's a good idea.

[christopherthomasdesign]

Thanks @owenatgov – I was just gonna squash it all into one commit, so if you think there are things in there worth preserving, would deffo appreciate your help

[owenatgov]

@christopherthomasdesign If you're happy to squash it into one then that's fine by me! It's not a significant enough change that it needs to be split. Go ahead 😃

[trang-erskine]

Just one thing, otherwise it looks great.

Right now, we link to the community backlog page at the start of the discussion. However, is there a way to link the discussion to the community backlog pages? Some people might be aware of our existing community backlog pages, but not about the new changes. It might be good to write a little update in the community backlog to say we are actively looking at these components right now, join the chat in the discussion pages.

This does mean that past conversations are on the community backlog and new discussion on the discussion pages. Which is probably okay for now. Later on we will need to think about whether we want to do anything about it.

[calvin-lau-sig7]

@trang-erskine, that's a good point!

We've added some posts in the comms plan to direct people from existing backlog discussions to the new discussion pages.

We considered whether we'd want to lock the old issue pages whilst there's a discussion happening, but agreed to wait and see what the conversations look like.