FEATURE: Implement component for displaying Favicons in frontend

[crydotsnake]

No description provided.

[mhsdesign]

Thanks for your work ^^ Is it normal that this seems so complex / verbose?

I mean this is supposed to be a exemplary demo - im not sure if this wouldnt scare people away :P

... But if this is the way. I would not oppose.

[crydotsnake]

Well. You could also use a fluid file with the HTML for the favicons. And a fusion file that inherits from Neos.Fusion:Template and just has the package and the Fluid file as the templatePath as propertys.

But the idea as I have solved it here came to me as the first thought.

But both solutions are not complex at all IMO 🤔

[Sebobo]

Today you don't need so many icons anymore, see https://evilmartians.com/chronicles/how-to-favicon-in-2021-six-files-that-fit-most-needs or other articles. Also the manifest should be adjustable or have safe placeholders, as it contains something about Sandstorm and Neos and people might just copy it.
To make the manifest adjustable, similar to the Robots.txt in Neos.Seo would actually be a cool example I think. Also I would not use the ResourceUri but directly use the StaticResource Eelhelper in the Tag. They should anyway be a bit more individual and not all have the 32px size attribute.

[crydotsnake]

Today you don't need so many icons anymore, see https://evilmartians.com/chronicles/how-to-favicon-in-2021-six-files-that-fit-most-needs or other articles.

First i thought about using a favicon generator. For example: https://realfavicongenerator.net/

But was not sure if this would be a good solution. Wdyt?

[Sebobo]

Why not just remove the tags you don't need and keep the rest and just do a few adjustments?
Don't fully understand your question regarding the generator and how it would help?

[Sebobo]

Should target 8.4 though

[crydotsnake]

Should target 8.4 though

Done.