-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
Right now, if you want to use images inside a Doenet activity, you have to upload them to some external site and link to it in Doenet. It is more convenient for authors to upload images directly on Doenet.
The goal: build infrastructure to host images and allows authors to upload/use them
Design questions:
- Images are expensive. What should the storage cap be per user?
- What should the upload image UI look like? (See old doenet.org for an example)
- How should we store images - directly in the database or an S3 bucket?
- Do we worry about who can access these images? "If you have the link, you can see it" vs more sophisticated approach
- How do we deal with the scenario where one user remixes an activity with an image?
- How do we clean up unused images?
Reactions are currently unavailable