This is so interesting. These modern sites clash really hard with my mental visual of "Government technology." And it led me to this, which is maybe even more interesting: <a href="https://federalist.18f.gov/" rel="nofollow">https://federalist.18f.gov/</a>
Before I submit a bug report-- is there a good reason that the zero isn't dotted in this font?<p>For example, executive order numbers have both "O" and "0" appearing in them. But I'm sure there are stronger examples in various gov't depts. where those characters can occur in sequence and create errors. Not to mention any code snippets that already appear in government web sites.<p>I suppose the extra ink could be a concern, but we should be moving away from paper printouts anyway. And as we do that, extinguishing a small dot in this great nation's zeros would be an important symbolic first step in combating climate change.
The github page has more info <a href="https://github.com/uswds/public-sans/blob/master/README.md#design-principles" rel="nofollow">https://github.com/uswds/public-sans/blob/master/README.md#d...</a>
What is the advantage of this over Open Sans? Is it less encumbered legally? Or are there other advantages? Or is it simply another alternative, which is also great.
The older I get, the more skeptical I become. Kudos to the author for releasing their project, it looks like a lot of effort went into it, so I hate to sound overly negative, but I just can't help wonder if there is a practical reason for the US government to develop its own font?<p>Is Sans Serif Fonts the department where the US government can really make a difference, or is this just a designer who happened to get a job with the US government and designed a font because they always wanted to and now they got the opportunity?
I've been wondering why all these new fonts tend to have a strong focus on sans serif font (Fira has no serif variant, Source Serif Pro came later than the other Source fonts). Aren't there a lot of situations (namely, lengthy legal documents) where you'd prefer a serif font before you want a sans serif?
Good choice to base this on Franklin Gothic. Given that IRS tax forms already use it, it's effectively been part of the US government's "brand identity" for a long time.
AUR package for easy install on Arch: <a href="https://aur.archlinux.org/packages/ttf-public-sans/" rel="nofollow">https://aur.archlinux.org/packages/ttf-public-sans/</a>
The question neither this page nor the GitHub answers is... why? I understand a lot of corporations did their own fonts to escape font licensing. Is there fonts the government is currently licensing and trying to get out from under? Where will I see this font? Is there a reason other open source fonts weren't already adequate?
Interesting that this web site uses a Let's Encrypt certificate. I suppose it saves the maintainers from being gouged by a beltway bandit charging thousands to monitor and then update an ordinary CA-issued certificate.
Interesting take: Does Public Sans' OFL-1.1 license violate the Establishment Clause?<p><a href="https://github.com/uswds/public-sans/issues/31" rel="nofollow">https://github.com/uswds/public-sans/issues/31</a>
You know that something that says it's neutral is always anything but.<p>Very readable, and it screams "America" which makes sense given who made it.
I can only imagine the hours of meetings and deliberation that went into developing a one-size-fits-all, cross agency font. That meets all sorts of weird political and accessibility guidelines.<p>Still, it only has to be done once! I'm a huge fan of what the USWDS has done so far. I love the model of an internal tech resource for the government.
Check out the Digital Services Act, a current bill going through congress to throw some gas on efforts like this: <a href="https://www.wired.com/story/kamala-harris-digital-services-act-2019/" rel="nofollow">https://www.wired.com/story/kamala-harris-digital-services-a...</a>
I am really impressed with 18F and how the federal government has really stepped up their game on the digital/open source front.<p>It does make me wonder though if the usage rights of these projects should be restricted to use by US taxpayers though since that is who is ultimately paying for this work.
Fantastic font. I've long seen Helvetica (literally meaning "Swiss" with one added letter) used in official US forms, communication and the like. If this becomes the "US brand" and replaces Helvetica as a national font, it's a really great choice.
Just installed it as my system UI font under Linux (previously I was using B612, and before that CMU Sans). Took me by surprise how readable it is even at small sizes.<p>I just wish there was a monospaced variant/equivalent so I can run it in my terminal/Emacs windows.
Is it legal for the federal government to specify a font license other than “This is released into the public domain”? They automatically give up all copyright upon publication, which ought to exhaust any licensing terms.
No FVAR version mentioned on the website? (If there isn't one: it's rather entirely worth converting your different masters into a single FVAR master instead)
What if the progression ends up being:<p>1. Publicly-funded font(s) created<p>2. Use on govt websites grows<p>3. Publicly-funded CDN used for said govt site assets<p>4. Other, non-govt sites use said font(s)<p>5. Govt becomes asset host for web basics across thousands of non-govt sites<p>This may be another step in CDN lifecycle of startup --> megacorp --> commoditization --> govt service.
I dislike it! Especially how the curved base appears to drop below the flat base!<p>In my mind this font lacks symmetry and consistency needed to be easily readable. It hurts my eyes.
Sans is overused. Please do not use (or carefully consider before using) sans fonts for long blocks of text you expect people to read.[1]<p>[1] <a href="https://www.youtube.com/watch?v=soYKFWqVVzg#t=34m53s" rel="nofollow">https://www.youtube.com/watch?v=soYKFWqVVzg#t=34m53s</a><p>"I disagree, I like sans [for long prose] better" comments miss the point; this is not an anecdata competition, it's about <i>how many</i> people prefer each one (and also it would be worth considering <i>how strongly</i> they hold that preference, since mildly pissing off even a slight majority of your readers/customers is better than <i>really</i> pissing off a smaller percentage). Even if you're skeptical of the studies Mayer looked at, Google (literata) and Amazon (bookerly) seem to be in the serif camp. Do you think Amazon made a mistake, too?