Hey, we are looking into favicons together with <@...
# general
f
Hey, we are looking into favicons together with @James and a question came up: Not all browsers support svg (yet), the correct way in my oppinion would be to: 1. take an svg 2. scale it up with libvips to the correct size converting to png Imagemagick has spotty and not well working support for that. As imagemagick is on the way out, do we want to allow two different features according to presence of one or the other?
t
You probalby talk about the starter frontend? I am pretty sure this is handled by the devs that build their storefront with that generated Rails app. Not sure how Solidus is involved here. Can you explain what your goals are?
f
In my mind solidus environments should store and serve the favicon as they everything from seo information to products. Favicons enjoy a varying browser support regarding formats but I’d like to generate the four important ones from solidus after uploading an svg one. Libvip actually can do all transformation tasks required so we could store an svg and throw out the favicon in the three four required versions easily. For me storefront is logic and not branded content so in my head it goes into the store setting with url meta tittle and description.
The idea would be to offer a simple upload interface and afterwards serve three sizes as png generated from the svg.
t
Ok, so your idea is, that Solidus should have a self service interface for admins? Currently our audience is skilled Rails developers who build their store for their clients (store admins). Where do you want to draw the line for that interface?
f
Content should in my opinion always be stored on solidus, that’s for me not a rails developer or not discussion. Visual outcome of content is template, content itself is solidus and the favicon is content :)
t
Valid point. I am not oposed to such feature.
❤️ 1
f
Which brings back to the question :) what’s the general feeling about imagick vs Libvip support?
t
Currently this is a decission the store programming team makes. Since we use activestorage this should be no problem, tbh. The picture manipulating is abstracted into https://rubygems.org/gems/image_processing
f
We saw that, the real issue is the output quality and size of the pngs with imagick
I checked yesterday and pngs grow massively in size, my question is do we want to create feature variability depending on dependencies and how to determine the presence of a dependency
t
Questions a developer can answer for the client needs 🙂 I think these are two things. An admin interface to upload the favicon and B) How to integrate this into the starter frontend
f
Ok I will get back to you on this one :)