Live data from Hacker News

Sweden Sans

identity.sweden.se

71–80 of 190 posts

Re: Sweden Sans

#71
post #62
post #56

Earlier quoted context omitted.

Are you using Cloudflare's 1.1.1.1 DNS by any chance?

Does Cloudflare DNS block it? Or are you proposing Cloudflare DNS as a solution?

It's the other way around. The site blocks Cloudflare for some political reasons that have been mentioned here before, but I can't remember what they were.

Re: Sweden Sans

#74
post #68

France also has its own design system and font (Marianne): https://www.systeme-de-design.gouv.fr/elements-d-interface/f...

Berlin has Berlin Type https://wir.berlin/kampagnen/die-typo

The UK has GDS Transport, which can only be used on gov.uk websites, not even internal UK government websites.

https://design-system.service.gov.uk/styles/typography/

The British government may be an omnishambles, but their websites are remarkably clear and readable, specially for an aging population with worsening eyesight.

Re: Sweden Sans

#76
> Inspired by the old signages system in Sweden

I am interested in this part. Which signage system does it refer to? It does not immediately ring a bell for me.

Re: Sweden Sans

#77
post #44

Earlier quoted context omitted.

Typographic documentation is for designers generally, but there is a world where this can actually help everyone. Designers should make consistent designs. By doing this Developers can create functional designs systems that have sane default behaviors. Once you can get to that point, the system serves to reduce the load from the dev, not increase. I have created a tailwind-based design system interpretation like this…

Good points which I generally agree with, but I still think it's common to see a remarkable level of time and effort spent on typography compared to even other parts of the frontend. Not always, but surprisingly often. Many companies have these style guides around typography. Beautiful, thoughtful, very well made things for sure, yet when some backend dev makes a typo so the custom font drops to arial or whatever, it…

I don't think it's that puzzling. After designing the typeface, those same designers have time to sit down and write up a fancy brochure for it. Engineers on the other hand, have a long list of existing tickets, so the minute they fix the broken magic string, there's another fix to move on to and no time to write a fancy brochure about the SQL schema.

Re: Sweden Sans

#78
post #74
post #68

Earlier quoted context omitted.

Berlin has Berlin Type https://wir.berlin/kampagnen/die-typo

The UK has GDS Transport, which can only be used on gov.uk websites, not even internal UK government websites. https://design-system.service.gov.uk/styles/typography/ The British government may be an omnishambles, but their websites are remarkably clear and readable, specially for an aging population with worsening eyesight.

Building an atlas of these for every country in the world seems like a fun project.

Re: Sweden Sans

#79
post #76

> Inspired by the old signages system in Sweden I am interested in this part. Which signage system does it refer to? It does not immediately ring a bell for me.

I found a Guardian article [1] which quotes one of the people involved:

  "We started to think about how it would work with different typefaces, then started mood boards with different fonts and pictures – especially of old Swedish signs we'd seen from the 1940s and 50s," said Jesper Robinell, Söderhavet’s head of design.
[1] https://www.theguardian.com/world/2014/nov/14/sweden-sans-de...

Re: Sweden Sans

#80
post #77
post #44

Earlier quoted context omitted.

Good points which I generally agree with, but I still think it's common to see a remarkable level of time and effort spent on typography compared to even other parts of the frontend. Not always, but surprisingly often. Many companies have these style guides around typography. Beautiful, thoughtful, very well made things for sure, yet when some backend dev makes a typo so the custom font drops to arial or whatever, it…

I don't think it's that puzzling. After designing the typeface, those same designers have time to sit down and write up a fancy brochure for it. Engineers on the other hand, have a long list of existing tickets, so the minute they fix the broken magic string, there's another fix to move on to and no time to write a fancy brochure about the SQL schema.

The irony, of course, is that codebases would be a lot better if developers did sit down at the end of a project and wrote high quality documentation for it. Even better if they did it while developing the codebase.

Also, this comment is especially ironic on HN where the top 10 comments on every Show HN submission will be nitpicking about the design of the website or the wording used, etc.

Post reply on HN