Statico Source
Contents

Project structure

The folders of a Statico site and what each one is for.

Getting started, page 4

pages/        routes          pages/about.html → /about/   pages/blog/index.html → /blog/
layouts/      page shells     <layout src="main.html" title="…"> … </layout>
includes/     partials        <include src="nav.html" />
collections/  data files      menu.json | .yaml | .toml | .csv
content/      markdown        content/blog/hello.md → /blog/hello/
assets/       css, js, images (css/main.css → Tailwind, js/main.js → esbuild)
public/       copied to the site root as-is (favicon.ico, robots.txt, CNAME)
statico.json    optional config (static.json also works)
.env          optional; PUBLIC_ keys available as {env.PUBLIC_KEY}

Output goes to _site/. Never edit _site/ by hand; it is rebuilt from scratch.

Special pages:

  • pages/404.html → /404.html (what static hosts serve for missing pages)
  • pages/<folder>/[content].html → template for every content/<folder>/*.md
  • pages/<folder>/[tag].html → one page per tag (see taxonomies)