Open allanaaa opened 12 months ago
The file shortcode can be a path to enabling some of this with the "it's just stored on an item" approach, though won't work with a private item.
That might help, in some cases, if individual files could also be set as public or private (yet still shareable). Not really for sites assets that aren't related to a particular public item.
Perhaps, in line with S, we can add favicons to this feature.
Classic, and particularly .net, has no ability to add site asset files other than logo+header. For people who are using .net as an affordable and reliable hosting solution, it makes little sense to limit their file-hosting access when images are needed elsewhere on the site.
(I have been attempting to host asset files on a private item and call the images with HTML, but that obviously isn't working because of AWS token expiry.)
I think we can encourage better (and more visually appealing) use of Omeka Classic and .net by adding broader asset hosting.