This adds a hard requirement to use font awesome in all front end templates. Is that really desirable?

It's an overridable layout (the whole voting capability should still just be inlined into com_content but ¯\_(ツ)_/¯)

@brianteeman com_content is already using Font Awesome icons in other elements
A couple of examples:
https://github.com/joomla/joomla-cms/blob/4.0-dev/layouts/joomla/content/info_block/hits.php#L16
https://github.com/joomla/joomla-cms/blob/4.0-dev/layouts/joomla/content/info_block/modify_date.php#L17

it may well be right now but one of the aims was to remove that requirement not add to it

@brianteeman this "let's not stick with Bootstrap" but at the same time "let's use it partially" approach is inconsistent. I find impossible to know where is fine and where is not to make use of dependencies like BS4 (and now same case with Font Awesome).

A clear guidance on this matter would be useful.

My two cents. We're never going to have a core UI that is 100% decoupled from any framework. So, as long as we have all this "framework coupling" in overridable layouts, at this point I'm leaning toward "who cares, replace it if you want".

I am just repeating what "powers that be" have said about frontend decoupling - not giving an opinion as thatis too dangerous

Keeping consistency is a good practice, and also is my personal opinion.

Regards

I would rather go with joomla/40-backend-template#441. I'v used a similar technique in DPCalendar. Like that it is possible for a template to override icons. If there is interest, I can migrate the pr here.

@laoneo is that needed? This is a front-end layout that can already be overridden

Icons have always been a pain in Joomla. There should be an easy way to change them and to have a strategy which serves the core and extension devs.

Making always an override of every view when you want to change the icon set sounds for me not optimal. Keep in mind we have forms, etc. with icons. Having a common layout where you can pass a string and it returns an icon is for me the way to go.

Having a common layout where you can pass a string and it returns an icon is for me the way to go.

Explain this bit in more detail. Because right now I'm afraid you're going to have this as a layout file, which would be about as crappy as that endtab.php file:

<?php
$icon = $displayData['icon'];
?>
<span class="<?php echo $icon; ?>"></span>

We do load them inline in a JLayout. So the template dev can override the layout itself or place the required icons in the template folder itself.