maud-axum-integration

Maud templates render HTML server-side in Axum by implementing IntoResponse for Maud Markup types, allowing routes to return compiled templates as HTTP responses. Wire your Axum handlers to accept AppState, pass data to Maud templates, and return the markup directly—Axum serializes it as HTML.

Yes. Maud integrates with Axum through IntoResponse implementations and the maud crate's axum feature flag. Enable it in Cargo.toml, then return Markup types from route handlers to produce server-side rendered HTML responses with full template composition support.

Build reusable layouts by composing Maud templates that accept state and child content, then nest them within error handlers and route templates. Pass shared AppState through the composition chain so layouts access application context for rendering consistent page structure and error displays.

Maud integration requires Rust 2021 edition, Axum 0.8.x, the maud crate with the axum feature enabled, a Tokio runtime, and routes that implement IntoResponse. Ensure your Cargo.toml includes both crates and the feature flag for seamless template-to-response conversion.

Define an AppState struct, extract it in Axum handlers using State extractor, and pass fields directly to Maud template closures. Templates receive the state data and render it into markup, enabling stateful rendering across layouts, pages, and error responses.

Yes. Maud templates render HTML fragments that HTMX requests consume, and Axum routes return Markup responses with appropriate Content-Type headers. This pattern supports dynamic partial updates, form submissions, and interactive SSR workflows in MASH/HARM stack architectures.