Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I just created the module: Fontello (http://drupal.org/project/fontello). This service includes Font Awesome as one of it's sources.
Comments
Comment #1
markhalliwellI'd be happy to make you a maintainer on Fontello if you'd like :)
Comment #2
RobLoachVery cool! Didn't know of Fontello. I'll stick a link on the project page!
Comment #3
mgiffordWhy would you use one module other than the other (if you're just using the Font Awesome Icons)?
Comment #4
markhalliwellThe goal from a front-end performance standpoint is to reduce the amount of bandwidth required to download the page. If you're loading an entire library of icons and only use say, 10% of them, then you're effectively wasting the other 90% of bandwidth space. The Fontello Service allows you to pick and choose only the icons you actually use (which includes selecting from all the Font Awesome icons), thus reducing the entire file size the client would have to download. Ultimately, when it comes to icons, we really should get away from loading entire libraries and only use them when their needed, which is now the goal of the Icon API module.
Also, FYI @RobLoach, the Fontello module is simply a provider for the Icon API. You might want to take a look at that.
Comment #5
mgiffordInteresting. Thanks Mark!
Comment #6
inders CreditAttribution: inders commentedfontawesome is now providing support for Icon API and bundle fontawesome has been added.
Admin URL:- admin/config/media/icon/bundle/fontawesome
Would like to play also with: Fontello !
Thanks & Regards
-Inder Singh
http://indersingh.com
http://northwebstudio.com
Comment #7
markhalliwellI'm still kind of adamant that this should happen TBH. Aside from using every single icon in Font Awesome on a site (which is highly and extremely unlikely), I really don't see the point of this module. It also wouldn't take much to add the same "library" support in Icon API and even a drush command to download the library on install, if the entire library is desired.
Would appreciate @RobLoach's and @mgifford's feedback.
Comment #8
markhalliwellComment #9
markhalliwellI get support requests in the Icon API module for this module (evidence by the latest #2434441: Overridden bundles should only store overridden properties) and even helped rewrite this module in #2312935: [fontawesome] 7.x-2.x so it would function properly.
I still think that merging this into Icon API is the right approach and it would give people a popular icon library semi out of the box besides just the Lullabot icon bundle. I would also be able to help support it better.
Comment #10
jenlampton> Aside from using every single icon in Font Awesome on a site (which is highly and extremely unlikely), I really don't see the point of this module.
The point of adding all the icons is that sometimes you don't know which icons are necessary when a site is launched. I have two sites that have this use case, we have an icon associated with a content type, and as each new piece of content is added editors select a new (hopefully distinct) icon to pair with the content. As the developer, I have no idea which icons they are going to pick in the future. They need to be able to add the content without calling someone to have another icon added into their library.
I vote to keep this module separate from Icon API. There are different use-cases and both solutions are valid :)
Comment #11
solideogloria CreditAttribution: solideogloria commentedSomeone can feel free to reopen if they want, but I'm guessing this is not going to happen. This module has a Drupal 8 branch, the Icon API doesn't. So the argument that the other module is better maintained is not true.
I also agree with jenlampton. Icons can be easily added/updated in content when they all are there.
Comment #12
Daniel.Moberly CreditAttribution: Daniel.Moberly commentedFont Awesome also launched the option to pick and choose which icons you want included with their icon builder (rather than loading all of them), which is one of the arguments in favor of "Fontello". Agreed with the closure.