Static sites, checked.
Heine compiles a configured content tree and Tera templates into a managed output tree. Before writing it, Heine resolves pages, copied assets, locale-specific content, and generated resources against one site model.
A missing internal page or copied asset should fail where it is named, not become a broken link discovered later in a browser.
A small model, visible in the source
Pages declare their Markdown inputs and templates. Templates receive resolved pages, assets, and generated-resource views instead of arbitrary filesystem access. Collections, taxonomies, feeds, sitemaps, and search indexes consume the same resolved model rather than creating output from template-side guesses.
The build is synchronous and deterministic: discover inputs, resolve the site, render deliberate values, then publish a complete managed output tree.
A deliberate boundary
Heine owns relationships that require knowledge of the resolved site: internal page and asset links, locale-aware routes, generated listings, and declared content. It does not become a general frontend toolchain.
CSS and JavaScript processing, media transformation, deployment, audits, and external services remain ordinary tools around the generator.
Current status
Heine is pre-release software and is not published yet. The source repository will contain the build instructions, a tutorial, focused guides, the complete reference, and a working starter site.