Why Heine?

Heine began as the static-site generator I wanted for my own sites. I had used Hugo and then Zola. Over time, I encountered several problems that were small in isolation but expensive in attention:

Those experiences shaped a narrower aim: turn authored content into a static site while checking relationships that can otherwise fail late or silently.

What Heine checks

Before it writes a full output tree, Heine resolves pages, copied assets, templates, generated resources, and their routes into one site model. That turns ordinary authoring mistakes into build errors:

As a site gains pagination, taxonomies, translations, or generated resources, those features make more claims about the same output tree.

Localization without template forks

A multilingual site needs content, routes, and interface text to work together, but each has different rules. Heine keeps them separate. Pages have explicit locale identities and optional translation groups. Fluent resources supply localized labels and plural forms through a fallback chain that Heine checks at each template call.

That keeps translated page relationships visible in the content model, while templates can keep using the same structural markup. It also lets a site state text direction per locale instead of assuming that every locale is left to right.

Math in Markdown

When math is enabled, Heine recognizes inline and display math before ordinary Markdown punctuation can reinterpret TeX. It can preserve TeX for a client renderer or render checked MathML during the build.

The same Markdown boundary provides checked internal links, citations, syntax highlighting, tables, task-list labels, footnotes, margin footnotes, and native picture blocks. Each construct has defined output.

Preview the generated site locally

heine serve serves the generated output tree with live reload and HTTP byte-range responses. Browser media controls can therefore seek audio and video while you preview a site locally. Production hosting remains the web server's responsibility.

The server serves the output tree from the build. Local preview therefore uses the same output that Heine publishes in a full build.

What Heine leaves out

Dedicated tools remain better suited to CSS and JavaScript processing, media transformation, deployment, audits, and external services. Heine concentrates on the relationships within a static site.

Choose Heine when you want a static-site generator with an explicit content model, deterministic output, and diagnostics for site relationships. It is less suitable when an existing theme marketplace, a broad plugin ecosystem, or a framework-managed frontend pipeline is the central requirement.

How Heine is developed

Heine’s design, scope, and non-goals come from my own experience building and maintaining static sites. I make those decisions.

AI assistance, principally Codex, has contributed substantially to the implementation and to design and code review. I direct that work, review the result, run the project’s checks, and remain responsible for Heine’s design, releases, and maintenance.

No independent audit has assessed Heine. The test suite exercises its behavior through focused tests, checked-error cases, and fixture builds of the tutorial and starter site.