Arguably, what many users want from Image Process, is a simple way to get responsive images across their website. In order to set this up, they'll typically have to configure a srcset transformation (https://github.com/pelican-plugins/image-process#responsive-images), which might be daunting for some users. They need to understand srcset vs img-tag, the various image formats and figure out what actual sizes to use.
For this simple use case, it should be possible to come up with some sensible srcset-default, that will convert all images to avif (or webp) and 3-4 sensible sizes (unless there is an explicit image process tag defined) which is what most users probably want.
That would make Image Process a lot easier to use for users who don't care for art direction and all the nitty, gritty details - while retaining all options for power users.
To stay backward compatible, there could be an explicit switch to turn this feature on, or alternatively, when it's on by default, a special image-process css class (e.g. image-process-ignore), that disables processing of the associated image.
What do you guys think?
Arguably, what many users want from Image Process, is a simple way to get responsive images across their website. In order to set this up, they'll typically have to configure a srcset transformation (https://github.com/pelican-plugins/image-process#responsive-images), which might be daunting for some users. They need to understand srcset vs img-tag, the various image formats and figure out what actual sizes to use.
For this simple use case, it should be possible to come up with some sensible srcset-default, that will convert all images to avif (or webp) and 3-4 sensible sizes (unless there is an explicit image process tag defined) which is what most users probably want.
That would make Image Process a lot easier to use for users who don't care for art direction and all the nitty, gritty details - while retaining all options for power users.
To stay backward compatible, there could be an explicit switch to turn this feature on, or alternatively, when it's on by default, a special image-process css class (e.g.
image-process-ignore), that disables processing of the associated image.What do you guys think?