Overview

Rizzy is designed to seamlessly integrate server-rendered Blazor components with the dynamic capabilities of HTMX. It achieves this by providing equivalent components for many of Blazor’s built-in ones. These Rizzy-specific components, often prefixed with Rz, sometimes implement subtle differences behind the scenes to function correctly within an HTMX-driven workflow, which relies on standard HTTP requests and HTML fragments rather than Blazor’s typical SignalR or WebAssembly interactivity models.

Why the Rz* Components? They make standard Blazor components compatible with HTMX and common web techniques. For example, the RzInput* components add the standard data-val-* attributes needed for client-side validation libraries familiar to Asp.net MVC users, based on your model’s Data Annotations. This provides instant validation feedback alongside HTMX updates. Other Rz components handle specific HTMX integration points, like ensuring RzPageTitle updates correctly after swaps, or ensuring Blazor sections (RzSection*) work within Rizzy.

Below is a list of Blazor built-in components alongside their Rizzy equivalents or how they are typically used within Rizzy. Each Rizzy component aims to provide a developer experience nearly identical to its Blazor counterpart while embracing HTMX’s dynamic loading and partial updates.

For detailed documentation on the standard Blazor components, refer to the official Blazor Microsoft documentation. Rizzy’s components aim to align closely with these while enabling HTMX integration.