Modelling content

Media

Packshots, lifestyle photography, campaign video and size guides. Everything is stored in your own S3 bucket and served from your own CloudFront distribution.

Uploading files

Upload before you create the content that references it — the media picker only shows files already in the library.

  1. Go to Media in the sidebar
  2. Drag files onto the upload area Or click to browse. Multiple files at once is fine.
  3. Add alt text Describe what is in the image. This is what screen readers announce and what search engines index.
  4. Done The file now has a URL in your S3 bucket and is ready to attach to any media field.

20 MB per file

Any file type — images, video, PDFs, documents.

Dimensions detected

Image width and height are read automatically and returned by the API.

Isolated per space

Each space has its own library, so brands never see each other's assets.

Alt text is not optional for retail. It is what a screen reader announces to a shopper, and it is a real accessibility obligation in most markets. Describe the product and what is distinctive about the shot: "Navy quilted parka, front view, hood up" beats "product image".

Using media in content

Two field types reference the library. Click either one while editing an entry and the media picker opens.

media

Single media

One file. Hero image, thumbnail, size guide PDF.

media_multiple

Multiple media

Several files. Product galleries, lookbooks, downloads.

How the picker works

  • Browse every uploaded file as a visual thumbnail grid.
  • Select one file for a media field.
  • Select several for a media_multiple field — the order you pick them in is the order the API returns them.

What the API returns

Media fields resolve to full objects by default, so you get everything you need to render a responsive image in one request.

A media object in the response 
{
  "hero_image": {
    "id": 5,
    "url": "https://bucket.s3.amazonaws.com/uploads/parka-front.jpg",
    "filename": "parka-front.jpg",
    "mime_type": "image/jpeg",
    "width": 1600,
    "height": 2000,
    "alt_text": "Navy quilted parka, front view, hood up"
  }
}

width and height let you set the correct aspect ratio before the image loads, which stops product grids jumping about as they render.

Add ?resolve=0 to a request to get raw media IDs instead of full objects. Useful when you are listing hundreds of products and do not need imagery in the payload.

Video

Uploaded video is handed to AWS MediaConvert for transcoding, so campaign video and product demos can be served in web-friendly formats without a separate pipeline. Because MediaConvert bills per minute processed, this is the one media operation with a cost worth watching — see what it costs to run.

Practical advice for large catalogues

  • Name files predictably. apk-2291-blk-front.jpg is findable in a library of thousands; IMG_4471.jpg is not.
  • Compress before uploading. Storage is cheap, but CloudFront data transfer is charged on every request. An oversized packshot is paid for repeatedly.
  • Watch the 20 MB ceiling. Raw photography and long video will exceed it — export web-ready versions.
  • Keep alt text with the asset. Written once on upload, it comes through everywhere the image is used.
  • Set long cache TTLs. Product imagery rarely changes, so let CloudFront hold onto it.
Next Content entries Create the entries that pull your models and media together.