User tests: Successful: Unsuccessful:
Pull Request to add an overview of all available Font Awesome Icons to the System Information tab.
For Joomla 3 we have a nice overview of all Icomoon Icons that are in the Joomla core: https://docs.joomla.org/J3.x:Joomla_Standard_Icomoon_Fonts
I find that page very useful:
I needed some default Font Awesome Icons in J4. There wasn't an overview of all Joomla 4 Font Awesome Icons. So I wrote some PHP code to display all the Joomla 4 icons. I used the supplied in the SVGs in /media/vendor/fontawesome-free/webfonts/
to get all the icon glyph names.
The overview that I generated I used to create a J4 "Joomla Standard Font Awesome Fonts" documentation page:
https://docs.joomla.org/J4.x:Joomla_Standard_Font_Awesome_Fonts
However, the documentation page in the Joomla MediaWiki does not support Font Awesome icons and most images are not displayed.
Furthermore I think that it would be useful to have an overview of those Icons in Joomla itself. So that you don't have to visit the documentation website to find some proper icons.
After installing this PR a new "Available Icons" tab will be visible:
In System > System Information > "Available Icons" tab
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_admin Language & Strings |
As far as I know it’s a template‘s decision if it loads fontawesome. What if a 3rd party backend template doesn’t load it?
Besides this, I think the system info is not really the right place, and for me it is sufficient to have it in the documentation.
A nice idea - but it is template related (atum and cassiopeia) not system related.
Adding such a list to cassiopea and atum would be useful for template developers.
Thank you all for your feedback. I understand that not all templates support Font Awesome and that the documentation wiki seems indeed the best place.
I'm closing this issue.
Thanks!
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-05-06 11:35:28 |
Closed_By | ⇒ | pe7er | |
Labels |
Added:
Language Change
?
|
Personally I would just fix the wiki