Asset delivery

Predictable paths and explicit releases make published assets easier to understand.

Choose an object path

A path should tell you which project and release a file belongs to. Avoid replacing bytes at a URL that has already been published with a long cache lifetime.

/projects/catalog/releases/site-v1/card.8ac420.webp

Reference a versioned asset

The URL below is a documentation example on a reserved domain. It demonstrates the shape of a public image reference; it is not a hosted customer asset.

<img
  src="https://assets.example/releases/site-v1/card.8ac420.webp"
  alt="Product preview"
  width="640"
  height="480"
>

Use standard HTTP semantics

A public asset should answer GET and HEAD with consistent metadata. Missing resources should return 404. Conditional requests can use ETag or Last-Modified rather than downloading unchanged bytes.

Separate public and private objects

This installation serves public reference files only. Do not place secrets, private exports, credentials, or unpublished business material in a public asset directory.