A resource is any kind of media that is loaded by the application. There are three types of media that can be used, each with their own advantages and downsides.
The media manager is the primary tool used to distribute and load images, both with backup and translation.
The idea is to upload an image to one of the media servers, then distribute it from there to other media servers. The database stores which media servers contain that image, and the application will receive this information, requesting the image from whichever server responds (starting with the server selected in the config settings. This way, an unavailable server won't hinder the loading process of images and videos.
The translation system can be used on top of the distribution system. It allows for a group of images to be linked together, each given a language tag. The user's selected language is then used to choose which image to load. This way, the application's media can respond to the user's native language.
These are addressed via their element name, e.g.
The image stored as https://media-de.biozoom.net/image1.png would be rereferenced as image1.png.
The most intuitive option is to use external servers to load images. While this approach does not allow for the redundancy- or the language system descriped in the previous method, it requires no setup work. Any image that is publically accessible can be used (for instance, https://mediaServer.org/image1.png. The whole url would then be copied into the config page background or element.
Note
Some servers prohibit external servers from loading their media from within our application - or any application, for that matter. There is nothing to be done from the app's side. The best approach here is to try and see whether or not the Preview system can load the media.
A variety of basic assets, such as icon-designs or a sample background reside within the application itself. This means that it will always be available, and never needs to be loaded.
They can be addressed via /assets/imgs/<imageName>.