I’d like to start a discussion about working with images in OCMS, including SEO optimization, validation, upload restrictions, and compression. I’m interested in hearing about your approaches and the pros and cons of your solutions.
First, I’ll share my own approach.
I created the MediaGallery plugin, which is connected to the media and saves images to JSON as a widgetInput value.
Pros:
A-Z and Z-A sorting
Searching within additional information
Bulk deletion
Bulk sorting via drag & drop
Add extra fields for additional information
Configure widgetInput
Deleted images or renamed files are marked as missing and not displayed on the front end
Automatic generation of WebP format and HTML tags for the front end
Responsive UI
Cons:
Additional information must be re-entered for every record of every entry
I don’t know where I used which image
After deleting or editing, I have to track down where it was used if I want cleaner data in the DB
Optimization:
WebP format
Additional information on the front end
I plan to implement compression and upload size limits
Great topic! The media manager is showing its age, so I’m interested in this too, especially to hear how others are using it.
My wish list so far:
Sidecar table in the database for metadata (alt text, captions, usage tracking)
Multisite support, as a subfolder inside the disk
Multiple disks support
On upload restrictions: forcing a file size is a more systemic problem. In the eCommerce plugin for example, clients quickly fill up the disk by uploading 4MB product images straight from their phones. A sensible default + per-field override would go a long way.
Curious whether others are solving the “where did I use this image” problem at the media layer or higher up.