Closed strogonoff closed 5 years ago
Dealing with ImageMagick Ruby bindings seems futile, at least under macOS. Some ways around it:
1) Give up on macOS support. It’s useful for working with local site copies so we sort of implicitly support it, but it’s not essential since using VM is an easy option with Vagrant or Docker.
2) Give up on automatic SVG rasterization and require OP sites to provide an additional PNG render of symbol.svg. It gives a fine-grained control over favicon/touch icon look (doubt that’s essential). On the other hand, it is not DRY and introduces unnecessary human factor.
There is better meta tag support & documentation for favicon now. The solution is suboptimal since it requires a manual render of multiple PNG representations of the original SVG asset, complicating site setup, but I don’t see a good way around it for now.
Following set, and a
/favicon.ico
under site root, may be enough:Related to #14.