Heine design records

These records explain why a feature has its current boundary. They are useful when you need to understand a trade-off, contribute to Heine, or evaluate a future proposal. For configuration and template rules, start with the focused guides and the reference instead.

Implemented features

• Absolute URLs
• Copied-asset licensing coverage
• Draft publication
• Kits
• Localized value formatting
• Markdown block components
• Markdown facts
• Multilingual sitemap alternates
• Margin footnotes
• Search
• Series
• Table of contents
• Plugins and renderer adapters
• Generated color-scheme pictures

Deferred proposals

• Percentage and currency formatting: extensions that await stable ICU4X formatter APIs.
• Renderer output dependencies: a future typed resource-manifest boundary for embedded renderer results.

Exploratory records

• External asset manifests: why a per-URL cache-busting helper is insufficient, and the boundary a future external asset-manifest integration would need.

Rejected proposals

• Markdown template fragments: an investigated Tera2-in-Markdown proposal that conflicts with Heine's existing content-and-template composition boundary.