image processing #588
Closed
husenunicorn
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
|
Sveltia CMS already has a built-in image optimizer. I know there is an outstanding issue in the Netlify/Decap CMS repo, but creating multiple variants is not planned with the feature, because your repository will be messed up. If you can’t do it at build time, consider using an external service like Cloudinary and Uploadcare, which are both supported in Sveltia CMS. We also plan to add support for Cloudflare Images in the future. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Suppose I use Zola built-in image processing to generate six image variants during the build process. After the build is completed, all processed images are placed in the public folder and then distributed by Cloudflare as static assets across its edge network.
This approach works well for small websites with only a limited number of pages and images. However, as the project scales such as thousands of pages with tens of thousands of static assets, where most of those assets are images problems start to appear.
Because multiple image variants are generated at build time, the number of static files grows very quickly and can easily reach Cloudflare Workers’ static asset limits.
https://developers.cloudflare.com/workers/platform/limits/#static-assets
For this reason, it would be extremely useful if Sveltia CMS could support image processing outside of the build process in the future, with the results stored in media storage such as Cloudflare R2. This approach would, Reduce the number of static assets served by Workers, Keep builds lightweight and fast.
Currently, I have around 2K pages and 10K static assets generated during the build process:)

Beta Was this translation helpful? Give feedback.
All reactions