Earlier quoted context omitted.
Yup. I run Federalist at 18F and absolutely love the work, the challenge and colleagues. We do everything in the open, so feel free to follow our work here: https://github.com/18F/federalist We also implement the USWDS, which you can follow here: https://github.com/18F/federalist-uswds-jekyll Let me know if you have any questions!
Curious to hear if your group is still well supported budget wise?
Public Sans – A strong, neutral typeface for text or display
81–90 of 245 posts
Re: Public Sans – A strong, neutral typeface for text or display
#82I appreciate the tailed 'l'.
Re: Public Sans – A strong, neutral typeface for text or display
#83It is sad that any nice font looks like crap with Windows font rendering.
Windows does not have crap font rendering, Windows has advanced hinting support that varies by typeface and is infinitely customizable. Other operating systems apply a global hinting that typically discards the font designer's own preferences for how the font should look (especially at smaller scales). Fonts without that manual hinting look like crap on Windows because Windows does not force through its own rendering…
you mean that big:
http://www.unics.uni-hannover.de/nhtcapri/quotation-marks.ht...
not even able to provide correct quotation marks!
Re: Public Sans – A strong, neutral typeface for text or display
#84Re: Public Sans – A strong, neutral typeface for text or display
#85Re: Public Sans – A strong, neutral typeface for text or display
#86Earlier quoted context omitted.
https://openforest.fs.usda.gov/christmas-trees/forests has a pretty heavy dependency on Javascript (read: there's no fallback to anything non-javascript, so I get a white page). It feels like that goes against some of the things that 18F is about.
Pages don't need a fallback to non-Javascript in 2019. Accessibility technologies now fully support a JS enabled web, with accessibility standards following suit. That leaves only those who have voluntarily disabled JavaScript ( I've worked on public facing government websites (not 18F). We simply don't support this edge case, and our legal department supports our legal right to do so (in particular in relation to AD…
Re: Public Sans – A strong, neutral typeface for text or display
#87For 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.
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.
Re: Public Sans – A strong, neutral typeface for text or display
#88This 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: https://federalist.18f.gov/
Yup. I run Federalist at 18F and absolutely love the work, the challenge and colleagues. We do everything in the open, so feel free to follow our work here: https://github.com/18F/federalist We also implement the USWDS, which you can follow here: https://github.com/18F/federalist-uswds-jekyll Let me know if you have any questions!
Some of those are the worst.
Re: Public Sans – A strong, neutral typeface for text or display
#89I'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?
Primarily because they focus on interfaces, not publishing. Serif is traditionally used for legibility of long text. Sans always wins for actual interface design (at least those with some manner of complexity) because it's much less visually distracting when used in a variety of weights and sizes. Interfaces tend to have much more mixed usage so we usually go with sans. Generally just using the system font is fine fo…
Re: Public Sans – A strong, neutral typeface for text or display
#90This 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: https://federalist.18f.gov/
Yup. I run Federalist at 18F and absolutely love the work, the challenge and colleagues. We do everything in the open, so feel free to follow our work here: https://github.com/18F/federalist We also implement the USWDS, which you can follow here: https://github.com/18F/federalist-uswds-jekyll Let me know if you have any questions!
In my country, all tax-funded government works are copyrighted. It's an ongoing battle to make each department release their works under a free license, and massive bodies of government-owned digitized cultural works sadly remain accessible only to those who pay for them.