-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
51 lines (43 loc) · 3.07 KB
/
index.html
File metadata and controls
51 lines (43 loc) · 3.07 KB
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
---
layout: default
title: Considerations for KLRD Website
---
<div class="one-column">
<h1>KLRD Site considerations</h1>
<p><strong>1. Rebuild site to better serve mobile devices.</strong></p>
<p>The site should “respond” to the user’s screen size, and adjust automatically so that all content fits. The website’s layout should be easy to navigate by finger taps. <em>Example: this website.</em></p>
<p> </p>
<p><strong>2. Change layout of site to clarify order of importance.</strong></p>
<p>Change layout from three columns to two columns. Format all content for easy visual scanning.
<ul>
<li>Example: <a href="https://www.nngroup.com/articles/layer-cake-pattern-scanning/">Nielsen Norman Group</a> uses two-column layouts throughout their site. (This article also has some great information on creating scannable content.)</li>
</ul>
</p>
<p> </p>
<p><strong>3. Reduce reliance on PDFs.</strong></p>
<p>Improve accessibility by building more content in HTML. Clicking on links that result in PDF downloads still tends to surprise web users. Warn users about PDFs with every download URL.
<ul>
<li>Example of HTML's improved accessibility: Resize this text by using CTRL+ or CTRL- on the keyboard. The page size adapts to the text size. </li>
<li>Style example of PDF warning: <a href="#">Appropriations Report (PDF)</a></li>
<li>Further reading: <a href="https://gds.blog.gov.uk/2018/07/16/why-gov-uk-content-should-be-published-in-html-and-not-pdf/">Why GOV.UK content should be published in HTML and not PDF</a></li>
<li>Example HTML document: <a href="https://www.gov.uk/government/publications/patient-confidentiality-in-nhs-population-screening-programmes/nhs-population-screening-confidential-patient-data">National population screening programmes: the information we use and why, and your options</a></li>
</ul>
</p>
<p> </p>
<p><strong>4. Improve search feature, and search results.</strong></p>
<p>Most web users aren’t “browsers” — they’re motivated hunters with a pre-conceived result in mind. Search results and website navigation need to be useful tools that aid a visitor in bagging their bounty. Add filtering and sorting options; use categories and tags to organize content.
<ul>
<li>Example of great, filter-able search results from the UK Government's site: <a href="https://www.gov.uk/search/all?keywords=population+screening&order=relevance">Search results for "population screening"</a></li>
</ul>
</p>
<p> </p>
<p><strong>5. Move to a template-based website or CMS.</strong></p>
<p>Bring more writers and website editors into the process of managing KLRD content. Limit access where needed; but bring more democracy into the process.</p>
<p>A Content Management System, or CMS, is a great tool for separating a website’s content from its source code.
<ul>
<li>WordPress is the recommended choice. <a href="https://www.wp101.com/tutorial/what-is-wordpress/">Here's an introductory video about it.</a> </li>
<li><a href="https://wordpress.com/pricing/">Pricing and features</a> ("Business" level recommended)</li>
</ul>
</p>
<p> </p>
</div>