Any ideas of how to handle this task efficiently? I am not using any web-development frameworks, I have hand-coded everything and am using a browser-based host.
If I were doing this without a framework, personally I'd just use an image CDN like Imgix or Cloudinary (which does all the optimizations serverside, including automatic conversion to webp or avif depending on browser). They handle all the transformations for you, and you can use a simple script/regex replace to generate a bunch of srcsets: https://docs.imgix.com/getting-started/tutorials/responsive-...
Or maybe just consider a basic WYSIWYG host with galleries, like Wix (https://support.wix.com/en/article/wix-pro-gallery-adding-an...) or SquareSpace (https://support.squarespace.com/hc/en-us/articles/206542467-...).
If you really wanted to do this manually, it could go something like:
- First use ImageMagick or GraphicsMagick or IrfanView or Photoshop or similar to bulk-convert all your images to a suitable format & compression level. Personally I'd just go with all JPEGs (maybe quality 80% or so?) and skip the webps/avifs because it's a lot less complicated and less likely to break on various operating system/browser version combos.
- You can use a simple bash script (or any sort of programming language) to name them whatever you want, including different versions by size. Some image utilities might also have bulk renames built-in. ChatGPT can probably help you figure out the specific parameters.
- Either using a script or just a regex replace, you can go from a list of filenames to - Then the hard part is figuring out how you want to display and maintain them in HTML/JS (i.e. you probably want a gallery of some sort, as opposed to 300 pictures one after another). So that means finding or writing a template. ------------ I don't know what you mean by a "browser-based" host; can you please explain? Other than that, everything is pretty standard, and was how we did image galleries back in the 90s and 2000s or so. It's less common these days because that takes several hours of work vs the several minutes it'd take in a modern framework.