` replaces the current title - keyed `<meta>`, `<link>`, and `<script>` entries are upserted - stable framework runtime assets stay in place unless the incoming document explicitly replaces the same keyed entry - use `data-iwf-key` for app-owned head entries, such as a canonical link whose `href` changes from page to page Use a top-level `<head>` when the page needs metadata beyond a title: ```idris articlePage : Article -> Html articlePage article = fragment [ <head> <title>{article.title}

# HTMX, Auto Refresh, and Modals Iwf's default HTML stack is hypermedia-first. Internal links and forms are boosted by htmx, swaps use morphdom, and the server still owns rendering. ## 1. Default Boosted Shell The default shell includes: - htmx - morphdom-swap extension - Basecoat CSS/JS - Iwf client script - stable flash host - stable modal host - canonical `#main-content` The shell adds: ```html hx-boost="true" hx-target="#main-content" hx-swap="morphdom" hx-ext="morphdom-swap" hx-sync="this:queue" ``` Use `hx-boost="false"` only for external links, downloads, full-page escapes, or explicit hard-navigation cases. ## 2. Rendering Rules `render` returns: - full document for normal HTML requests - only `#main-content` fragment for HTMX HTML requests - no HTMX fragment when the request prefers JSON This lets the same controller action serve first page loads and boosted navigation. For direct `Html` pages, Iwf normalizes the returned title/head and main content internally. The HTMX response contains the extracted `#main-content` plus a `

{article.title}

Live page