That’s my point really, it appears this decision was made on a flawed assumption. The new interface relies on you having the file stored locally, which is the opposite of the behavior Discourse previously encouraged. Previously we could have several logos stored in the Assets for the Site thread under Staff and refer to them as and where required. This is a definite disadvantage to the new UI.
One of the communities I assist has special versions of their logo for particular seasons and holidays. They used the assets topic to store all of these files, any of the staff could update the logo when a particular season was upon them. There shouldn’t be any need for them to each keep local copies in 2018.
I’m really hoping that this is just an interim step before we see some kind of media library implemented. Until then it would be great if we could get a URL field below the new image fields, so as to not cripple the workflow which existed previously.
I don’t think this is fair to say at all, it never superseded the assets topic nor the settings under /admin/ because it was only visible during setup, or to those who knew where the wizard was once the site was live. We could still use the topic which has existed for at least four years to store assets and swap between them whenever needed. Relying on local storage isn’t really any substitute for the flexibility this provided.
That’s an assumption based on a new and highly inflexible option - previously we didn’t have a media library per-se, but we did have an online collection of assets we could easily switch between. It has only become an internal implementation with this change. We didn’t need to be at a particular computer, with access to particular files. If a logo needed to be swapped out we could just dip into the old assets thread, grab a text URL and paste it into a text field. We could also repurpose the same URL into several fields. The new approach offers no such flexibility.
Already noticed, the first step I’ve taken to remedy this is to manually recreate it. In the case of tweaks which don’t warrant a theme component, sites still need somewhere to store assets referred to in CSS and HTML customisations. Without a media library to manage assets we still need a means to get them into Discourse.