Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Assets to Classic #1008

Open
allanaaa opened this issue Jul 10, 2023 · 3 comments
Open

Add Assets to Classic #1008

allanaaa opened this issue Jul 10, 2023 · 3 comments

Comments

@allanaaa
Copy link

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.

@zerocrates
Copy link
Member

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.

@allanaaa
Copy link
Author

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.

@allanaaa
Copy link
Author

Perhaps, in line with S, we can add favicons to this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants