-
Notifications
You must be signed in to change notification settings - Fork 0
/
be-aware-of-how-components-work-together.html
94 lines (60 loc) · 3.75 KB
/
be-aware-of-how-components-work-together.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width,maximum-scale=2">
<link rel="stylesheet" type="text/css" media="screen" href="/website/assets/css/style.css?v=74925587a2dbb4564e0f966645145991d68bccda">
<!-- Begin Jekyll SEO tag v2.5.0 -->
<title>Be aware of how your components work together</title>
<meta name="generator" content="Jekyll v3.7.4">
<meta property="og:title" content="Samantha Wright">
<meta property="og:locale" content="en_US">
<link rel="canonical" href="https://samantharwright.github.io/website/">
<meta property="og:url" content="https://samantharwright.github.io/website/">
<meta property="og:site_name" content="Samantha Wright">
<script type="application/ld+json">
{"headline":"Samantha Wright","@type":"WebSite","url":"https://samantharwright.github.io/website/","name":"Samantha Wright","@context":"http://schema.org"}</script>
<!-- End Jekyll SEO tag -->
<div id="header_wrap" class="outer">
<header class="inner">
<div class="blog-link">
<a href="https://samantharwright.github.io/website/">Samantha Wright</a>
</div>
<h1 id="project_title">Be aware of how your components work together</h1>
<p>18 July 2019</p>
</header>
</div>
</head>
<body>
<div id="main_content_wrap" class="outer">
<section id="main_content" class="inner">
<p>It’s very useful if your organisation has a design system with well-tested components. At NHS Digital we have the NHS UK frontend components.</p>
<p>But having components and guidance on when to use them isn’t enough. You need to understand how your components you’re using work together, not just how they work in isolation.</p>
<p>For example, the inset text component. You should use the inset text component to help users identify important content on the page.</p>
<p>Here’s the inset text component:</p>
<img src="inset-text.png" width="600" alt="Inset text component">
<p>The inset text component is really useful for making content stand out amongst other content. Particularly if a user is scrolling through lots of content.</p>
<p>The warning callout is similar but helps users understand warning content on the page, even if they don't read the whole page.</p>
<p>Here’s the warning callout component:</p>
<img src="warning-callout.png" width="600" alt="Warning callout component">
<p>The warning callout should be used for information that:</p>
<ul>
<li>is time critical</li>
<li>could have a significant effect on someone's health</li>
<li>addresses a common or significant misconception or mistake</li>
</ul>
<p>But imagine you use a warning callout close to some inset text. How will users know what content is important?</p>
<p>Although the inset text and warning callout components have different purposes, on the whole they still indicate to a user that this content is important.</p>
<p>Using too many of these components close together could:</p>
<ul>
<li>make your components less effective</li>
<li>confuse your users</li>
</ul>
<p>Make sure you’re aware of how your components work together, not just how they work in isolation.</p>
<nav class="pagination">
</nav>
<p>
Copyright Samantha Wright
</p>
</section>
</div>
</body>