Images and files
Images, fonts, video and documents live in the site’s files folder and are served straight from there. You hand a file to your agent; it uploads it as a draft, and it goes live when you publish.
What may go in
The site accepts a fixed list of file types — images, fonts, video, PDF, and stylesheets, scripts and structured data — with a size limit per file. The exact list and caps: Styling and assets.
A file is judged by its contents, not its name: a photo.jpg that is not a JPEG does not get in. Vector images (SVG) are refused if they carry a script or anything else that could act on the page they are drawn into — an icon’s styling may colour the icon, never the site around it. Executable code and raw web pages can never be uploaded: a file that can run under your site’s name is a danger.
Uploads are public
Anything in the files folder is reachable by anyone who knows its address, whether or not a page links to it — and an agent with the right to read the files can find one by name (search { in: "assets" }). Treat an upload as published the moment it goes live. Do not upload contracts, identity documents or anything you would not print on a public page; link to a secure service instead.
Images that describe themselves
The page that shows an image carries a name and a caption, read alike by screen readers, search engines and AI assistants. Your agent asks for one when it adds an image, or writes one from what the image shows. There is no separate alt-text chore.
Replacing and removing
Replacing an image is uploading a new one under the same name; live keeps the old one until you publish, and history keeps it after. Removing a file is taking it back and dropping it, like a page — refused while something still uses it. See Drafts and going live.