It would be useful if ExpressionEngine's native image manipulation modifiers, especially :webp, allowed an optional custom output filename.
For example:
{image_field:webp width="350" quality="82" filename="portrait"}
could generate something like:
portrait-350.webp
instead of the current hashed cache filename.
The current hashed filenames make sense for cache uniqueness, but for public-facing image URLs it would be helpful to have clean, predictable filenames while still keeping EE's existing caching behaviour internally.
A possible implementation could keep the hash/cache logic behind the scenes, while exposing a cleaner filename or allowing a filename="" parameter.
Use case:
We use EE's on-the-fly WebP conversion for images across a site and want readable, stable image URLs without having to build a custom add-on.
That should be enough for a useful FR without overcomplicating it.
It would be useful if ExpressionEngine's native image manipulation modifiers, especially :webp, allowed an optional custom output filename.
For example:
{image_field:webp width="350" quality="82" filename="portrait"}could generate something like:
portrait-350.webpinstead of the current hashed cache filename.
The current hashed filenames make sense for cache uniqueness, but for public-facing image URLs it would be helpful to have clean, predictable filenames while still keeping EE's existing caching behaviour internally.
A possible implementation could keep the hash/cache logic behind the scenes, while exposing a cleaner filename or allowing a
filename=""parameter.Use case:
We use EE's on-the-fly WebP conversion for images across a site and want readable, stable image URLs without having to build a custom add-on.
That should be enough for a useful FR without overcomplicating it.