Asset pipeline

Files in your assets/ directory can be minified, bundled, and fingerprinted on the way into the build. Every switch is off by default, so assets are copied verbatim until you ask for more.

output {
  assets {
    minify #true
    bundle #true
    fingerprint #true
  }
}

What each switch does

minify

CSS is minified with Lightning CSS JavaScript is minified as part of bundling.

bundle

JavaScript entry points are bundled with rolldown, with imports resolved and dead code shaken out. Files whose name starts with _ are partials: pulled in through imports, never emitted on their own.

fingerprint

Output filenames get a content hash, turning style.css into style.9f3c1a2b4d6e8f01.css, and every reference in your pages is rewritten to match. Now you can cache assets forever and never serve a stale one.

Image optimization lives in its own images block, separate from these switches.

How references are rewritten

Write the plain path in your template:

#html.elem("link", attrs: (rel: "stylesheet", href: "/assets/style.css"))
#html.elem("script", attrs: (type: "module", src: "/assets/main.js"))

After the build those point at the hashed filenames. The rewrite works on the typed HTML tree, never on the serialized string, so it can’t corrupt your markup. This site’s stylesheet and script go through exactly this path.

In JavaScript

A bundled entry can import the site’s build data, including this fingerprint map, from the baudelaire:* virtual modules, so client code references a hashed asset by its logical path.

Bypassing the pipeline

Some files must reach the output root untouched: a robots.txt override, .well-known/, a CNAME, an install.sh. Put them in the static/ directory (configured under paths) and they are copied verbatim to the site root: no minify, no bundle, no fingerprint, no prefix. A generated page at the same path wins, so static/ is the lowest-priority source.