Skip to content

Commit e380ee5

Browse files
Ibrahim-HaizelIbrahim-Haizel
authored
Merge pull request #84 from communitiesuk/share-findings-about-your-users-page
Share findings about your users page
2 parents 989aa11 + e8c4ec1 commit e380ee5

File tree

2 files changed

+393
-0
lines changed

2 files changed

+393
-0
lines changed

‎src/routes/community/share-findings/+page.svelte‎

Lines changed: 349 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,349 @@
1+
<script>
2+
import WarningText from "$lib/components/content/WarningText.svelte";
3+
import InsetText from "$lib/components/content/InsetText.svelte";
4+
import CodeBlock from "$lib/package-wrapping/CodeBlock.svelte";
5+
import RelatedContent from "$lib/components/ui/RelatedContent.svelte";
6+
</script>
7+
8+
<svelte:head>
9+
<title>Share findings about your users - MHCLG Svelte Component Library</title
10+
>
11+
<meta
12+
name="description"
13+
content="Help us improve the MHCLG Svelte Component Library by sharing your user research findings and insights about how components work in your service."
14+
/>
15+
</svelte:head>
16+
17+
<div class="govuk-grid-row">
18+
<div class="govuk-grid-column-full">
19+
<h1 class="govuk-heading-xl">Share findings about your users</h1>
20+
21+
<p class="govuk-body-l">
22+
We want to hear how users experience components and patterns in your
23+
service – it helps us improve the component library. You can do this by
24+
taking part in discussions on GitHub or contacting our team directly.
25+
</p>
26+
27+
<p class="govuk-body">Useful findings to share might be things like:</p>
28+
29+
<ul class="govuk-list govuk-list--bullet">
30+
<li>summaries of user research you've done</li>
31+
<li>prototypes or ideas that you've tested</li>
32+
<li>analytics from your service</li>
33+
<li>accessibility testing results</li>
34+
<li>performance data from components in production</li>
35+
<li>
36+
responses to any calls for information
37+
<!-- we give in the 'Research on
38+
this…' section of our component pages -->
39+
</li>
40+
</ul>
41+
42+
<p class="govuk-body">
43+
Your service might be in the alpha or beta phases, or you might be
44+
iterating the service after going live. Feedback from any phase helps us
45+
iterate the component library in line with evolving user needs.
46+
</p>
47+
48+
<h2 class="govuk-heading-l">Where to add findings</h2>
49+
50+
<p class="govuk-body">
51+
Go to our <a
52+
href="https://github.com/mhclg-digital/svelte-component-library/discussions"
53+
class="govuk-link"
54+
rel="external">list of discussions on GitHub</a
55+
>. There are different categories for discussions about:
56+
</p>
57+
58+
<ul class="govuk-list govuk-list--bullet">
59+
<li>components already in the library</li>
60+
<li>new components that could be added in the future</li>
61+
<!-- <li>data visualisation patterns and approaches</li>
62+
<li>accessibility improvements</li>
63+
<li>performance optimisations</li> -->
64+
</ul>
65+
66+
<p class="govuk-body">
67+
Feedback on all of these is useful to us. You'll need to create a GitHub
68+
account to add comments.
69+
</p>
70+
71+
<p class="govuk-body">
72+
Select the component or topic you want to share findings about. If what
73+
you're looking for isn't on the list, read about how to <a
74+
href="/community/propose-component"
75+
class="govuk-link">propose a component or pattern</a
76+
>.
77+
</p>
78+
79+
<p class="govuk-body">
80+
Once you've selected the right discussion, use the template below to add
81+
your findings.
82+
</p>
83+
84+
<WarningText
85+
text="Share information responsibly. You must get informed consent from your participants before you can share findings of any research they've participated in."
86+
/>
87+
88+
<p class="govuk-body">
89+
Remember that all the information on GitHub is open to the public. Do not
90+
share any personally identifiable information about your participants or
91+
sensitive information about your service.
92+
</p>
93+
94+
<h2 class="govuk-heading-l">Research template</h2>
95+
96+
<p class="govuk-body">
97+
Use this template to give the community useful context about your
98+
findings. Copy and paste it into the GitHub comments box and add your
99+
findings.
100+
</p>
101+
102+
<CodeBlock
103+
code={`## Insights
104+
105+
What are your insights about how people use the component or pattern?
106+
107+
Try to include:
108+
- how it helped or hindered users' journeys, using specific observations
109+
- any metrics or hypotheses that helped you measure success
110+
- screenshots of how you implemented it in your service
111+
- accessibility testing results with assistive technologies
112+
- performance impact on your service
113+
114+
## Methods
115+
116+
Give us some context and briefly explain how you gathered the findings.
117+
118+
Try to include:
119+
- which service you used the component in
120+
- when you did your user research or test
121+
- whether it was a qualitative or quantitative study
122+
- whether you tested with users with access needs, noting any assistive technologies they used
123+
- what devices and browsers you tested on
124+
- any specific data visualisation or interaction requirements
125+
126+
## Technical context
127+
128+
Help us understand your implementation context.
129+
130+
Try to include:
131+
- which version of the component library you used
132+
- any customisations or modifications you made
133+
- integration with other systems or data sources
134+
- performance requirements or constraints
135+
- browser support requirements
136+
137+
## More information
138+
139+
Add links to any prototypes, research documents, or live services (where appropriate).`}
140+
filename="Research template"
141+
extension=".md"
142+
language="md"
143+
/>
144+
<br />
145+
<p class="govuk-body">
146+
You can edit your comment after you post it, so do not worry if you get
147+
something wrong or want to change it later.
148+
</p>
149+
150+
<p class="govuk-body">
151+
Community members might respond to your findings on GitHub. Feel free to
152+
take part in the conversation.
153+
</p>
154+
<!--
155+
<p class="govuk-body">For example, you could:</p>
156+
157+
<ul class="govuk-list govuk-list--bullet">
158+
<li>compare findings</li>
159+
<li>learn about each other's users and their needs</li>
160+
<li>see what's worked to improve things, and what has not</li>
161+
<li>share technical solutions to common problems</li>
162+
<li>discuss accessibility approaches</li>
163+
</ul> -->
164+
165+
<p class="govuk-body">
166+
You'll usually be subscribed to get notifications from GitHub when there's
167+
a new comment in the discussion. Find out how to <a
168+
href="https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications"
169+
class="govuk-link"
170+
rel="external">check your notification settings in GitHub</a
171+
>.
172+
</p>
173+
174+
<h2 class="govuk-heading-l">Alternative ways to share findings</h2>
175+
176+
<p class="govuk-body">
177+
If you prefer not to use GitHub, you can also share your findings by:
178+
</p>
179+
180+
<ul class="govuk-list govuk-list--bullet">
181+
<li>
182+
<a
183+
href="mailto:[email protected]"
184+
class="govuk-link">Emailing our team directly</a
185+
>
186+
</li>
187+
<!-- <li>Joining our community calls (contact us for details)</li>
188+
<li>Participating in our user research sessions</li> -->
189+
</ul>
190+
191+
<InsetText>
192+
{#snippet content()}
193+
We particularly welcome findings about data visualisation components,
194+
accessibility testing with assistive technologies, and performance
195+
impact in production services. These insights help us maintain our focus
196+
on creating accessible, performant government data products.
197+
{/snippet}
198+
</InsetText>
199+
200+
<!-- <h3 class="govuk-heading-m">Our prioritisation approach</h3>
201+
202+
<p class="govuk-body">
203+
We prioritise improvements and new additions based on:
204+
</p>
205+
206+
<ul class="govuk-list govuk-list--bullet">
207+
<li>
208+
<strong>User impact</strong> - How many users are affected and how severely
209+
</li>
210+
<li>
211+
<strong>Accessibility issues</strong> - Problems that prevent users with
212+
disabilities from accessing services
213+
</li>
214+
<li>
215+
<strong>Cross-government need</strong> - Components that would benefit multiple
216+
departments and services
217+
</li>
218+
<li>
219+
<strong>Data visualisation gaps</strong> - Missing components for presenting
220+
government data effectively
221+
</li>
222+
<li>
223+
<strong>Performance impact</strong> - Issues that significantly affect service
224+
performance
225+
</li>
226+
</ul>
227+
228+
<p class="govuk-body">
229+
Most major additions to the component library are chosen through a regular
230+
prioritisation process with the community. We share the chosen priorities
231+
on our <a href="/community/roadmap" class="govuk-link">roadmap page</a>.
232+
</p> -->
233+
234+
<h2 class="govuk-heading-l">What happens next</h2>
235+
236+
<p class="govuk-body">
237+
After you share your findings, here's what typically happens:
238+
</p>
239+
240+
<ol class="govuk-list govuk-list--number">
241+
<li>Our team reviews your findings and may ask follow-up questions</li>
242+
<li>We look for patterns across multiple services and user groups</li>
243+
<li>
244+
If we identify a clear need for improvement, we add it to our backlog
245+
</li>
246+
<li>We prioritise the work based on impact and available capacity</li>
247+
<li>
248+
We update the community on progress through our roadmap and blog posts
249+
</li>
250+
</ol>
251+
252+
<!-- <p class="govuk-body">
253+
We aim to acknowledge all feedback within 5 working days and provide
254+
updates on any actions we plan to take.
255+
</p> -->
256+
257+
<h2 class="govuk-heading-l">Acting on feedback</h2>
258+
259+
<p class="govuk-body">
260+
Our team reads all new comments on our GitHub pages and direct feedback.
261+
We do not usually act immediately on feedback – we need to grow a clear
262+
body of evidence before we can be sure that something is a problem.
263+
</p>
264+
265+
<p class="govuk-body">
266+
Even if your findings do not lead to a change to the component library,
267+
it's really useful to share anyway. People across government read the
268+
discussions on GitHub to see how others have approached things and what
269+
they've learned.
270+
</p>
271+
272+
<h2 class="govuk-heading-l">Need help?</h2>
273+
274+
<p class="govuk-body">
275+
If you've got a question about sharing your findings or need help with the
276+
research template, <a
277+
href="mailto:[email protected]"
278+
class="govuk-link">contact our team</a
279+
>.
280+
</p>
281+
282+
<p class="govuk-body">
283+
We're also happy to help you plan user research or provide guidance on
284+
testing our components with your users.
285+
</p>
286+
287+
<RelatedContent
288+
sections={[
289+
{
290+
type: "main",
291+
id: "related-content",
292+
title: "Related content",
293+
links: [
294+
{
295+
title: "Propose a component or pattern",
296+
base_path: "/community/propose-component",
297+
},
298+
{
299+
title: "Develop a component or pattern",
300+
base_path: "/community/develop-component",
301+
},
302+
{
303+
title: "Contribution criteria",
304+
base_path: "/community/contribution-criteria",
305+
},
306+
],
307+
},
308+
{
309+
type: "subheading",
310+
id: "community-resources",
311+
subheading: "Community resources",
312+
links: [
313+
{
314+
title: "Our team and delivery approach",
315+
base_path: "/community/team-approach",
316+
},
317+
{
318+
title: "Projects using the component library",
319+
base_path: "/community/projects",
320+
},
321+
{
322+
title: "Roadmap",
323+
base_path: "/community/roadmap",
324+
},
325+
],
326+
},
327+
{
328+
type: "other",
329+
id: "external-resources",
330+
subheading: "External resources",
331+
links: [
332+
{
333+
title: "GitHub discussions",
334+
url: "https://github.com/communitiesuk/svelte-component-library/discussions",
335+
},
336+
{
337+
title: "GOV.UK Service Manual: User research",
338+
url: "https://www.gov.uk/service-manual/user-research",
339+
},
340+
{
341+
title: "GitHub notification settings",
342+
url: "https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications",
343+
},
344+
],
345+
},
346+
]}
347+
/>
348+
</div>
349+
</div>

0 commit comments

Comments
 (0)