🛠️
Wazimap technical handbook
  • Introduction
  • System Architecture
    • Database Models
    • IndicatorData
    • Geography Hierarchies
    • Choropleth Maps
    • Determine which instance to use
  • Development
    • Code Deployment
    • Component Architecture
    • Development Process
    • Pull Request Template Explanation
    • Code Review Process
    • Pull Request Template (FE)
    • Webflow Integration
    • Merging webflow exports
    • Rules for Webflow exports
    • Webflow exports & changelog
      • June 2023
      • March 2023
      • February 2023
      • December 2022
      • November 2022
      • October 2022
      • May 2022
      • April 2022
      • March 2022
      • January 2022
      • December 2021
      • November 2021
      • October 2021
    • Translation
    • Map components
  • Testing
    • Testing guidelines
    • Critical Paths
    • GUI Tests
    • Heroku Review Apps
  • Design
    • Iconography
  • Change Proposals
  • NGPx - Template
  • NGP1 - Changing the data model (Implemented)
  • NGP2 - Presenting Geographical Hierarchies to users
  • NGP3 - Change Geography Hierarchies
  • NGP4 - Format configuration
  • NGP5 - Multiple count columns
  • NGP6 - Profile-specific open graph metadata
  • NGP7 - Wazimap profile domain management
  • NGP8 - Replacing Webflow as frontend framework
  • Tutorials
    • Creating a new profile
    • Loading new geographies
    • Loading Data
    • Creating a new admin user
    • Creating a non-admin user for a private profile
    • Changing the Geography level name
    • Deployment to Dokku
  • Configuration
  • Profile Configuration
  • Profile Indicator Configuration
  • Profile Collection Configuration
  • Geographies, hierarchies and versions
  • API
    • General API Information
    • Upload API
    • Task Status
    • Point data API
Powered by GitBook
On this page
  • Icon choice
  • Size
  • Visual weight

Was this helpful?

Export as PDF
  1. Design

Iconography

Guidance for decision making around choosing the correct icon and using it in a way that makes sense.

PreviousHeroku Review AppsNextNGPx - Template

Last updated 2 years ago

Was this helpful?

Icon choice

When choosing an icon, the following things should be taken into consideration.

  1. The icon should be generalized and not reliant on knowledge of a specific language or region.

  2. The icon should follow established norms for icons of it's type in similar applications.

  3. When the choice deviates from a norm, it should only be done for very good reasons.

  4. Icons should be made distinct enough from others in the UI

Some examples:

Size

Icons should generally have the following size properties:

  1. Icons should be no larger than 24px wide and 24px tall.

  2. Icons that are smaller than 24px in size, should fit within a bounding box that is 24px.

Visual weight

Visual weight refers to the amount of prevalence an icon has when looking at it's role in the UI combined with how important the action that icon represents is to the user. When deciding on the visual weight of an icon, the following considerations need to be made.

How unique is the icon in the UI

If there is only 1 instance of this icon in the entire UI, it generally denotes it requiring a higher visual weight. eg. search, data mapper, rich data view.

How important is the action the icon represents

If the action has high importance it should generally be given more weight in the UI, either through, size, colour or containing element settings (eg. size of button, space around button etc.).

This is generally the approach taken for icon sets like and .

Material
FontAwesome
Poor icon choice: An example of a legacy icon that was poorly chosen as it is specific to a region and not generalized.
Good icon choice: Example of an icon that follows regular norms and is widely understood.
A 24px bounding box with an icon that is actually smaller than 24px wide.
When an icon appears multiple times in the UI, it needs to be given less visual weight (left) in order to not overwhelm the user and attract undue attention (right). In this case, the icon was shaded in a lighter colour.
Download is given similar weight to zoom in/out when placed in the same context as "map options"
Core functions have a larger button size and are given more space and prominence.