How to best support non-media assets?
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 1.8k
- Forks
- 150
- Avg merge
- 11h 46m
- Merged PRs (30d)
- 8
Description
People might want to store other files on their website (e.g. some.pdf) and just link them. There's currently no UI for that, but we could add support for Attachments on pages or something.
I'd just have concerns storing large files in assets, because Fly.io volume storage is more expensive than S3. So if you have a lot of files, it might still make sense to have your own S3 bucket or something, and then just link from your site.
Need to reflect on that a bit, but generally happy to add a more integrated support for "Attachments".
Context: https://bsky.app/profile/anthonymoser.com/post/3mvastco3p22q
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the existing page editing and asset-storage entry points, then compare local volume storage with external S3-style storage. Done means the attachment scope, storage behavior, and linking experience are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100