Config option for name of "processed_images" folder

[matthillco]

Please could we have a config option to rename the "processed_images" folder?

This name doesn't fit the model that most of our devs are familiar with and we'd prefer to use something like "cache" instead.

Thanks in advance.

[Keats]

I mean we could but it's something internal that only gets exposed via the URL, is it really important? I would wait to see if more people need that

[husenunicorn]

I mean we could but it's something internal that only gets exposed via the URL, is it really important? I would wait to see if more people need that

For SEO reasons and to comply with Google’s best practices, if it is possible to rename processed_images, I am willing to change it to processed-images.
Although the processed images are currently indexed in search results, it would be better to follow Google’s recommendations.

https://developers.google.com/search/docs/crawling-indexing/url-structure#use-hyphens-to-separate-words

[matthillco]

I mean we could but it's something internal that only gets exposed via the URL, is it really important? I would wait to see if more people need that

Aside from the reason already given for this request, consider pages with a lot of images, all using complex <picture> elements and/or multiple srcset attributes. Long path names here all add up to increasing the size of the delivered HTML. Sure, HTML is highly compressible and from that perspective it doesn't really matter how long those paths are, but if you can reduce the length of the path in the first place, then it's a reasonable consideration.

Plus "cache" is well understood, terse, and much easier to type if necessary. :)