Hi, Tony. The idea is to provide some unique, project-specific class name on a tag as far out as possible. This allows css descendant or child-selectors to affect 80-90% of the contained html without any further ado or html modifications. It's a very non-intrusive way to grant CSS control of most of the tag content without having to repeatedly keep tweaking the html inside the tag. 

This makes it possible for the css author attach the LibreOffice icon to the Libre Office project link without having to specifically request a special "fav-libreoffice" class on the exact link where the icon should go.
Also, if we realize that the icon would be better suited at the left edge of the issue headline, only the CSS needs changes to accomplish this.


**Example:** 
.issue-libreoffice a[target="_project"]{ } /*Selects the a-tag for the LibreOffice project only, to insert the ico for example */

.issue-libreoffice .issue-header{ } /* By simply modifying the selector, now the headline is selected instead and the ico goes here. **No changes** to the html at all.*/

Another example
.issue-libreoffice a[href^="/core/user"] /*Selects the a-tag for the LibreOffice project only*/

I did forget though, that the best solution would be to have line 18 like this:

<div class="row **issue** issue-{{issue.project.name|slugify}}">

If you can publish this change I'll make any further pull requests from proper branches. I'll also try to install this locally at my Linux Mint.

Thanks!