barnardos / design-system

The website and components of the Design System
https://design-system.barnardos.org.uk/
MIT License
29 stars 4 forks source link

Update typeface using open source fonts #414

Closed kelliedesigner closed 5 years ago

kelliedesigner commented 5 years ago

The aim of this work is to:

Links and resources

References:

Acceptance Criteria

kelliedesigner commented 5 years ago

Fonts to implement:

  1. Quicksand - https://fonts.google.com/specimen/Quicksand - Single-storey
  2. Rubik - https://fonts.google.com/specimen/Rubik - Double-storey
  3. Vision - https://www.fontfabric.com/vision/ - Single-storey

~https://fonts.google.com/specimen/Sniglet - Too similar to Macmillian~

kelliedesigner commented 5 years ago
  1. Quicksand

    screen shot 2018-11-20 at 16 42 02
  2. Rubik

    screen shot 2018-11-20 at 16 41 35
  3. Vision

    screen shot 2018-11-20 at 16 51 08

Proxima Nova

screen shot 2018-11-20 at 16 57 47
tosbourn commented 5 years ago

Can I ask that one criteria we use when spiking fonts be we print a test page from a website and see how well the font looks when printed.

People print content off the web all the time, and any font we choose should play nice with printers.

kelliedesigner commented 5 years ago

Can I ask that one criteria we use when spiking fonts be we print a test page from a website and see how well the font looks when printed.

People print content off the web all the time, and any font we choose should play nice with printers.

I have added this to the Acceptance criteria.

jeddy3 commented 5 years ago

After an initial investigation, none of the open source fonts were viable candidates. As such, we're going to investigate what can be done to improve the consumption of the Proxima Nova font. See https://github.com/barnardos/design-system/issues/424

jeddy3 commented 5 years ago

investigate what can be done to improve the consumption of the Proxima Nova font

Following up with more information to weigh up the pros and cons...

The good:

This is unsustainable at scale,

Adobe Fonts has taken over Typekit. They seem to have a far more liberal approach to licensing. For example, gone are the:

This makes it easier for teams to implement the typeface

See: https://helpx.adobe.com/fonts/using/introducing-adobe-fonts.html#KitsarenowWebProjects

If we go with Google Suite internally

Proxima Nova seems to be available in the Google Suite.

We would like to avoid spending more money on licensing for a font

It's a fixed monthly fee regardless of the number of domains/products, and that fee isn't prohibitively expensive.

The not-so-good:

It was chosen as it has a single-storey 'a'.

It's the "alternative" version comes with a single-storey 'a', but the licensing (and consumption) around this version isn't clear.

We would like to avoid spending more money on licensing for a font

There's still a monthly fee.


There are still important questions around the suitable of the font from a brand and CYP reading experience perspective but some of the barriers to teams consuming the typeface and costs aren't as tall as initially thought.