Show HN: Webfont for Press Logos
fontfamous.com
fontfamous.com
How the author will choose to capitalise on that awareness, it's up to him, but he needs to gets there first and getting there is not easy.
That said, I understand where you're coming from. Some people have not been able to capitalise their open source contributions. Even companies struggle (e.g. twitter). Others were able to capitalise though. At this stage, I wouldn't worry about that, we can't even see all possibilities here.
Success can be defined in multiple ways. Getting some visibility to the ever-growing web-dev community is a great first step towards success IMHO and here's a very good chance of doing just that.
"Be respectful. Anyone sharing work is making a contribution, however modest.
Instead of "you're doing it wrong", suggest alternatives. When someone is learning, help them learn more.
When something isn't good, you needn't pretend that it is. But don't be gratuitously negative."
A few years ago I tried my hand at a similar project[0], but using SVG, CSS, and hand-written sizing[1] for each logo.
It was useful for us at Segment[2] because we needed to our partners's logos all over the place, and I didn't want to have to create new assets for every possible size/color combination, and to keep them all visually aligned too.
And then I started adding more non-Segment-partner logos too, like Heroku[3] or GitHub[4]. Here's an example in use from a side project[5].
Using CSS and SVG meant that we could keep "full color" and "full color reversed" version of the logos, in addition to just flat colors. Trouble was that hand-writing the sizes is something that only people with a trained-enough eye can do, since they need to be nicely optically aligned, so it got unmaintainable quickly, especially once we wanted to let partners onboard themselves. At one point my co-founder Peter had even written a Slack bot that would create vector versions of the logos automagically using Nightmare[6] and Swiftly[7] under the covers.
Anyways, some of the vector files or prior thinking might be useful for expanding your collection. Good luck!
[0]: https://github.com/logo/logo
[1]: https://github.com/logo/heroku/blob/master/index.css
[2]: https://segment.com
[3]: https://github.com/logo/heroku
[4]: https://github.com/logo/github
[5]: http://www.hn-button.com/
[6]: https://github.com/segmentio/nightmare-swiftly
[7]: https://99designs.com/blog/inside-99designs/swiftly-now-99de...
As it currently stands, anyone using the font will need to do this themselves.
Looks fine to me, the NYT would be dominatingly wide if normalised alongside CNN.
If any looks out of place, I'd say it's PH.
> Stop wasting time searching Google Images
I don't think there's much of an advantage in development time to find, download, and implement this over doing the same with images. That's an odd angle to take in the opening paragraph IMO.For me, the attraction is purely at 'runtime': I'd much rather serve a font over someone else's CDN than a bunch of images on my own host.
Plus, if the companies' logos/fonts change; I trust the community to be more on top of patching that than me noticing and grabbing a new image!