Media Library Should Be A Java FTP Client
-
Why am I forced to keep all my media assets (images, video, etc) on the same domain as my WordPress site? It would be way more efficient to make the Media Manager allow us to store images in another domain. That way, when the page loads, Javascript, CSS, the HTML, etc loads in a separate browser CPU threads, and the images load in other browser CPU threads concurrently.
The Media Library should act like a FTP client. I hate this dumbed down user interface. It offers ZERO in the organization of media assets. When you got thousands of images to work with, do you really expect us to find it based on Month and Year? C’mon!
I can’t believe that WordPress can’t get this right. This is a Content Management System. We are supposed to be able to manage Content. Not poke our eyes out searching for one image in a haystack among many.
The worst thing is, now that responsive content is important to deliver to many different screen sizes, the Media Library is tied into the Featured Image/Thumbnail system. When you upload the default image, it is resized into different sizes for the purpose of responsive image delivery.
So I can’t put my images on a separate image server because WordPress knows nothing about it, let alone resize the original image.
If I want to reuse a picture on Site A and Site B, I have to keep multiple images and not share them. An external media repository would be beneficial in that it can be mirrored across many geographic servers, thus increasing page load.
Create a Java FTP client in its place and let us do the asset management and organization.
- The topic ‘Media Library Should Be A Java FTP Client’ is closed to new replies.