Images

[3x071c]

There are multiple components to this, which should be split into their own issues:

• Providing an Image component that serves optimized, responsive images
• Serving an endpoint or script to transform static assets and uploaded images into optimized, response ones
• Adding an "images" tab to the Admin UI to easily administer all currently served images

We should consider delegating image optimization to a dedicated service, such as imaginary, which can be hosted on Fly together with the app itself.

[3x071c]

Update: We can use persistent volumes on Fly to store uploaded images. Via a GitHub cronjob, we can then iterate over the uploaded images every day and optimize them via sharp. The <Image> component then sources the images from the volume mount point and first attempts to load an optimized version for the client before resorting to the original.

Rescheduling to M3