- Issue created by @G4MBINI
- 🇺🇸United States MegaKeegMan
I'm also looking at this, but was looking on the 1.x branch. Regardless of branch, do you think it makes sense to just add https://www.drupal.org/project/fontawesome → as a dependency, rather than trying to manage the fontawesome library directly?
- 🇫🇷France G4MBINI Bègles
Hi @megakeegman ,
In branch 4.0.x we are leveraging UI Suite so, regarding Icons, we are using UI Icons (built on top of new Drupal core Icon API).
To be able to declare fontawesome Icon packs and use them in Drupal thanks to UI Icons, we only need fontawesome library to be present. I'm afraid https://www.drupal.org/project/fontawesome → is doing too much for what we want to achieve here ...
In the current situation I did put the library directly in the theme which is not a good practice. So, the point of this issue is to manage it the "good way".
ONE IMPORTANT point for branch 1.0.x : all UI Suite modules are independent from one another. So, if you want to use UI Icons / fontawesome as it is done in 4.0.x, you can do it ;) It's really kool and powerful to use Icons with UI Icons as all icons are usable directly via site building in Drupal UI (in menus, fields, field formatter, ckeditor, media).