Files
Files in Content
How Obelism Content uses media's files. Picking them in entries, optimized image URLs for sites, alt text and focal point per use, and what a change updates.
Obelism Content's asset fields and rich text use media's files. Content's sidebar Media opens the library on the same Space, and the asset picker in Content's editor browses the same folders and uploads into them.
What sites get
Sites never get raw files. Content's delivery API hands out content.obelism.studio/assets/{id}/{filename} URLs: Content reads the original through a signed link and serves an optimized version, in a modern format, without metadata, cropped around the focal point. Files that aren't images are served as they are.
The URL parameters, private files, caching and the asset object a site receives are in Content's assets guide and images.
Video stills
The library, Content's asset picker and its asset fields show a video by a still of it, taken one second in. Content cuts it for the dashboards only; sites get no stills in delivery. A private video's still opens only with the video's own signature, so it is as private as the video.
Cloudflare cuts the stills from videos up to 100 MB and 10 minutes long, best from MP4. For a video it can't read, the library shows the video's own first frame where the browser plays it, and a dark tile with a play mark otherwise.
One use, its own alt text
A file's title, alt text and focal point are set in media and used everywhere. One use in Content can have its own alt text, focal point, or show the file's Shopify products, without changing the file or its other uses: see alt text and focal point for one use.
When a file changes in media
Changing a file's title, alt text, focal point, tags or Shopify products, replacing it, or making it private or public, is announced to Content. Content then gives every environment whose content uses the file a new content version and sends asset.updated webhooks, as for its own edits, so sites pick up the change.
Moving a file to another folder changes no URL, so it announces nothing.
Where a file is used
Content records which entries use a file, in every environment, as drafts and published. While any do, the file can't be deleted; agents see the list in getFile's usages.