Statico Source
Contents

Building

What statico build writes: pages, assets, sitemap, feeds, search and more.

Build and deploy, page 18

statico build writes _site/:

  • pages rendered in parallel, HTML minified, CSS/JS fingerprinted (main.3f2a91c0.css) with references rewritten
  • local <img> get width/height (no layout shift), loading="lazy" and decoding="async" (the first image stays eager)
  • sitemap.xml (with an absolute URL), Atom feeds
  • llms.txt, llms-full.txt and a .md copy of every markdown page (/blog/hello/ → /blog/hello.md) for AI agents
  • search.json when build.search is true, or a Pagefind index with "pagefind"

Tailwind: assets/css/main.css is compiled with Tailwind v3 (@tailwind base;) or v4 (@import "tailwindcss";), detected automatically. Statico uses, in order, STATICO_TAILWIND, node_modules/.bin, a tailwindcss binary on PATH, a cached standalone binary it downloads itself, then npx. JavaScript in assets/js/main.js is bundled with esbuild the same way. No Node.js is required. Downloaded binaries are checked against SHA-256 hashes pinned in Statico and discarded, never run, if they don't match.

.env: like Vite and Astro, only keys that start with PUBLIC_ reach templates, so the same file can hold API keys for other tools. A template that asks for any other key gets a warning (S109) and nothing is substituted. statico check also fails (S108) if the value of a non-PUBLIC_ key (8 characters or longer) appears anywhere in the output: pages, feeds, search.json, llms-full.txt or .md mirrors.