Because Content Assets copies all images from content sources to a public assets folder, there's no reason they couldn't have additional processing done on them, such as resizing, image optimisation, etc.
Proposal
Investigate image resizing and processing libraries and see if their output is any good.
Determine a system to provide instructions to do this:
global config
folder config
file name
path query string
Notes
Also, check out existing libs such as NuxtImg and Cloudinary to see if using them would just be better.
Background
Because Content Assets copies all images from content sources to a public assets folder, there's no reason they couldn't have additional processing done on them, such as resizing, image optimisation, etc.
Proposal
Investigate image resizing and processing libraries and see if their output is any good.
Determine a system to provide instructions to do this:
Notes
Also, check out existing libs such as
NuxtImg
and Cloudinary to see if using them would just be better.