Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tools & Data: UI/UX Review #560

Open
ramyaragupathy opened this issue Jun 3, 2019 · 0 comments
Open

Tools & Data: UI/UX Review #560

ramyaragupathy opened this issue Jun 3, 2019 · 0 comments

Comments

@ramyaragupathy
Copy link
Member

From #557 - @katia-utochkina's review on Tools & Data page:

  • Information on tools isn’t presented in a scannable format
  • Card layout used for tools’ listing doesn’t support scannability
  • Inconsistent use of headings across pages

Information on tools isn’t presented in a scannable format

The content should be presented in a way that optimises scanning. At the moment, that’s not the case. Paragraphs with tool descriptions aren’t even lengthy. But they’re written in superfluous language which makes scanning the content difficult.

It’d be great to make the content more to the point and present all information in an outline format.

Card layout used for tools’ listing doesn’t support scannability

Looking for a particular piece of content in a card-based layout is difficult. This is because the items aren’t predictably arranged, and it’s hard to anticipate where to look on the page to find necessary information. This can make the search for a specific tool on the “Tools and Data” page frustrating.

Inconsistent use of headings across pages

On some pages (“Country” page, “Tools & Data” page), the site indicates where a user is with headings. On others (“Project” page), it doesn’t. This lack of consistency is a problem. When pages look different from the rest, it can be disconcerting to users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant