Developer docs

Static publishing patterns that stay readable.

These examples are static references for naming files, organizing releases, and linking assets from web pages.

Quick start

Create a release folder, place static files inside it, and reference the final paths from your HTML.

HTML usage

<link rel="stylesheet" href="/assets/css/app.bundle.css">
<script src="/assets/js/app.bundle.js"></script>
<img src="/assets/img/product-preview.webp" alt="Product preview">

File naming conventions

Use stable groups

assets/css, assets/js, assets/img, downloads

Prefer versioned names

app.2026-04.css, catalog.v4.webp, icons.1.2.zip

Keep previews explicit

hero-preview.webp, product-card-small.webp, poster-frame.webp

Example asset paths

Type	Example path	Usage
CSS bundle	`/assets/css/app.bundle.css`	Page styles
JavaScript bundle	`/assets/js/app.bundle.js`	Static app behavior
Image preview	`/assets/img/product-preview.webp`	Product card
Font file	`/assets/fonts/display.woff2`	Brand typography
Download pack	`/assets/downloads/ui-kit.zip`	Sample catalog

Cache headers explanation

Immutable files should use versioned names. Preview files can use shorter freshness windows when teams replace them during active product work.

Example headers

Cache-Control: public, max-age=31536000, immutable
Content-Type: text/css; charset=utf-8
ETag: "asset-release-2026-04"

Manifest example

A manifest helps apps reference the exact asset set published with a release.

asset-manifest.json

{
  "name": "product-launch",
  "version": "1.4.2",
  "updated": "2026-04-24",
  "files": [
    "/assets/css/app.bundle.css",
    "/assets/js/app.bundle.js",
    "/assets/img/product-preview.webp"
  ]
}

Folder structure example

Static project layout

assets/
  css/
    app.bundle.css
  js/
    app.bundle.js
  img/
    product-preview.webp
  fonts/
    display.woff2
  downloads/
    release-pack.zip
asset-manifest.json