govuk-design-system
govuk-design-system copied to clipboard
alphagov
Encourage users to take part in the community
What
Create a landing page to tell users about our community activities, which could include:
- co-design workshops for Maps and Task list
- Friday catch-up call
- cross-gov Slack channels
Why
We do not have a place to direct people who are interested in taking part. At the moment we rely on 'push' messaging over emails and Slack.
Who needs to work on this
Community Designer, Content Designer, Interaction Designer
Who needs to review this
Contribution squad
Done when
- [ ] https://github.com/alphagov/govuk-design-system/issues/2349 will create a new top-level page for /community/, which should give this section a clearer purpose
- [ ] https://github.com/alphagov/govuk-design-system/issues/1935 will divide subpages under /community/ into 3 'themes'
Related work
- [ ] https://github.com/alphagov/govuk-design-system/issues/2310 will improve the 'Backlog' subpage to be more community and contributor-focused as part of
- [ ] leftover pages (resources & tools, roadmap, blog posts) can be examined later, perhaps in a future tech docs/resources reorg
@calvin-lau-sig7 following our chat at backlog gardening today about reframing this an epic, I found this https://github.com/alphagov/govuk-design-system/issues/1935. Feel free to change
Hey @calvin-lau-sig7 and @ImranH-GDS. I know you're having conversations about this work. When you've agreed scope, could you update this epic card and write stories for the subsequent work. Can you also check this epic against this #1935 as they look quite similar. Thanks!
Some relevant decisions from 16 August workshop (Mural board):
- new page should be new top-level page in /community/
- no need for 'why get involved section'
- de-emphasise contribution process ('wrap to it' instead), as it's intimidating for new users
Also, as an update on this and a few related works:
- https://github.com/alphagov/govuk-design-system/issues/2349 will create a new top-level page for /community/, which should give this section a clearer purpose
- https://github.com/alphagov/govuk-design-system/issues/1935 will divide subpages under /community/ into 3 'themes'
- https://github.com/alphagov/govuk-design-system/issues/2310 will improve the 'Backlog' subpage to be more community and contributor-focused as part of
- leftover pages (resources & tools, roadmap, blog posts) can be examined later, perhaps in a future tech docs/resources reorg with @claireashworth
Hey I hope this is the right place but is this for anyone to take part in and is this just for GDS or the services built through GDS as whole, there are some services which were built prior to 2019 which don't fully conform to the service standards set out e.g. tracking and publishing data in both service standards for legacy content and anything made post July 2019 there are lots of services which should be tracking things like digital uptake in particular services and online tools which aren't doing so well or are made more complex by having third party contributors. Just from experience I've been down a rabbit hole to find this page so do think it would be a good idea for this community landing page to be linked on most services built by GDS @calvin-lau-sig7?
Hi @Musashi6246, not entirely clear on your question but I'll do my best to give an answer.
This page is for anyone that's interested in working with us to improve the GOV.UK Design System. This could mean things like sharing their user research, helping design a component/pattern or contributing code.
The Design System is a resource to help teams follow the Service Manual to meet the Service Standard. I would not expect any of these pages to be linked on any public-facing services, as it's not usually relevant to their user's needs.
Hope this helps fill you in on things.