Better image handling (1): Reuse images and assets

I want to propose two significant changes in terms of image handling, that will vastly improve the performance, cost-effectiveness and userfriendliness of the platform

1. Make it possible to reuse images and assets
2. Have an automatic scaling process

Make it possible to reuse images and assets

(I’m using the example of hero images, but this also works for other images and assets on inSided.) If a community wants to use the same hero image for different parent categories and categories, you have to upload the same local file several times, which creates several online files (one for each upload).

• So if if this hero image is 200kB large and you want to use it in ten different (parent) categories, your cloud space now occupies around 2MB of data instead of 200kB. This costs money (maybe primarily for inSided, but still).
• If you open each of the (parent) categories in the frontend, the hero image loads every single time, instead of loading it once and then storing it in the cache. This costs loading time (and negatively affects the platform performance).

Therefore, I propose to have an asset (or media) center. You can upload images and assets into this cloud directory, can pick files from this directory and use them in different places and use cases. This will improve the performance of the platform because the caching can be utilized more effectively and loading time will go down significantly.