RizzyUI 1.0.0-preview.2
dotnet add package RizzyUI --version 1.0.0-preview.2
NuGet\Install-Package RizzyUI -Version 1.0.0-preview.2
<PackageReference Include="RizzyUI" Version="1.0.0-preview.2" />
<PackageVersion Include="RizzyUI" Version="1.0.0-preview.2" />
<PackageReference Include="RizzyUI" />
paket add RizzyUI --version 1.0.0-preview.2
#r "nuget: RizzyUI, 1.0.0-preview.2"
#:package RizzyUI@1.0.0-preview.2
#addin nuget:?package=RizzyUI&version=1.0.0-preview.2&prerelease
#tool nuget:?package=RizzyUI&version=1.0.0-preview.2&prerelease
<img src="https://jalexsocial.github.io/Rizzy/media/rizzy-logo.png?cache=bust3" width="600"/>
RizzyUI: Modern UI Composition for ASP.NET SSR
<div align="center">
</div>
Composable SSR UI for ASP.NET Core - no WASM runtime, no SignalR circuit, no SPA rewrite.
If you like MVC or Razor Pages because they’re explicit, stateless, and easy to debug, RizzyUI keeps that model and modernizes the view layer:
- SSR Razor Components for composition
- Tailwind CSS v4 for styling
- Alpine.js for local interactivity
- HTMX for hypermedia-driven updates
RizzyUI runs in the normal ASP.NET Core request/response lifecycle. You can View Source, set breakpoints, and reason about what happened.
Documentation Site
For detailed documentation and examples, please visit the Rizzy Documentation Site. You can find a demo of all components along with documentation of RizzyUI at the RizzyUI Component Documentation site.
Who this is for
RizzyUI is a good fit if you want component reuse without switching to a SPA.
- ASP.NET Core teams that want a modern component model but still want SSR.
- MVC/Razor Pages apps suffering from partial-view sprawl, global JS, and CSS leakage.
- SSR-first projects where SEO, initial render, and debuggability matter.
Not a fit for
- Offline-first applications that depend on heavy client-side sync/storage.
- Ultra high-frequency real-time experiences where WebSockets/streaming is the product.
- Teams avoiding Tailwind—RizzyUI is Tailwind-first.
Tech stack (what you’re actually using)
RizzyUI is not a new platform. It’s a set of components + conventions built on common web primitives.
- Structure: Razor Components (C#) — SSR only
- Styling: Tailwind CSS v4
- Interactivity: Alpine.js
- Updates: HTMX (HTML fragments over HTTP)
Quick start
Create a new app with a sidebar layout and starter pages:
dotnet new install RizzyUI.Templates
dotnet new rizzyui -o MyApp
cd MyApp
dotnet run
You need the .NET 10 SDK or later and Node.js 20 or later; the first build installs the npm packages and compiles the Tailwind CSS. To add RizzyUI to an existing app instead, follow the steps below.
Installation
You install:
- the .NET package (components + server integration), and
- the NPM package (client-side assets and build pipeline).
1) Install packages
dotnet add package RizzyUI
npm install @jalexsocial/rizzyui
npm install -D tailwindcss @tailwindcss/cli
RizzyUI targets Rizzy 6 (htmx 4) and .NET 10. The RizzyUI package brings the matching
Rizzy package. Upgrading from a release built on Rizzy 5 (htmx 2)? See
docs/migration/rizzy5-to-rizzy6.md.
2) Register services + middleware
In Program.cs:
using Rizzy;
using RizzyUI;
var builder = WebApplication.CreateBuilder(args);
// Rizzy 6: registers htmx support and Razor components too.
builder.Services.AddRizzy();
builder.Services.AddRizzyUI(config =>
{
config.DefaultTheme = RzTheme.ArcticTheme;
});
var app = builder.Build();
app.UseAntiforgery();
app.UseRizzy();
app.Run();
3) Wire up the document head
In App.razor (or your main layout):
@inject Rizzy.Htmx.IRizzyNonceProvider NonceProvider
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<base href="/" />
<link rel="stylesheet" href="app.css" />
<RzHeadOutlet />
<RzScripts />
<script type="module" nonce="@NonceProvider.GetNonce()" src="_content/RizzyUI/js/rizzyui.min.js"></script>
<RzThemeProvider />
</head>
<body>
<Routes />
</body>
</html>
RizzyUI owns Alpine.js: rizzyui.js bundles and starts it, so do not add a separate Alpine script
(RizzyUI logs a console warning if it finds one). Components render without the runtime, but stay
non-interactive until rizzyui.js (or rizzyui-csp.js) loads as a module.
RizzyUI does not load htmx itself: <RzScripts /> does, from jsDelivr with subresource integrity
by default (set HtmxConfig.Scripts to serve your own copy). If your layout has no
<base href="/">, set RizzyConfig.ClientScriptUrl = "/_content/Rizzy/js/rizzy.js", because the
default script URL is relative.
The shift: component-driven SSR (without changing your architecture)
RizzyUI isn’t asking you to replatform. It’s a better way to compose views.
Before: partials + global JS
Partials tend to leak styling and force manual ID management for JS.
<div class="card @ViewData["Classes"]" id="card-@Model.Id">
<h3>@Model.Name</h3>
<button onclick="toggleDetails(@Model.Id)">Toggle</button>
<div id="details-@Model.Id" style="display:none;">...</div>
</div>
After: components + local state
You get encapsulated markup, typed parameters, and scoped behavior via Alpine.
// UserCard.razor
<RzCard class="w-[350px]">
<CardHeader>
<CardTitle>@User.Name</CardTitle>
</CardHeader>
<CardContent>
<div x-data="{ open: false }">
<RzButton x-on:click="open = !open" Variant="ThemeVariant.Outline">
Toggle Details
</RzButton>
<div x-show="open" x-collapse>
<p>@User.Email</p>
</div>
</div>
</CardContent>
</RzCard>
@code {
[Parameter] public UserData User { get; set; } = default!;
}
Advanced: the Alpine “code-behind” pattern
Inline Alpine strings (x-on:click="...") are great until they aren’t. For more complex behavior, RizzyUI supports a code-behind approach:
- your JS lives next to the component
- RizzyUI handles bundling/registration
- CSP nonces are handled automatically
1) Component (Counter.razor)
@attribute [RzAlpineCodeBehind]
<RzAlpineComponent For="this" Name="counter" AsChild>
<div class="flex gap-4">
<span x-text="count"></span>
<button x-on:click="increment">Increment</button>
</div>
</RzAlpineComponent>
2) Logic (Counter.razor.js)
export default () => ({
count: 0,
increment() {
this.count++;
}
});
Tradeoffs (honest costs)
RizzyUI is intentionally “boring tech,” but there are still costs:
- Build tooling: Tailwind implies Node.js + a build step.
- Logic near markup: Alpine keeps things local, but you’ll want conventions to avoid messy templates.
- Hypermedia mindset: HTMX shines when you’re comfortable returning HTML fragments, not just full pages.
License
RizzyUI is licensed under the MIT License.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Blazicons (>= 3.0.12)
- Blazicons.Ionicons (>= 3.1.22)
- Blazicons.Lucide (>= 1.14.37)
- Blazicons.MaterialDesignIcons (>= 2.2.26)
- Markdig (>= 0.45.0)
- Rizzy (>= 6.0.0-preview.3)
- RizzyUI.Tasks (>= 1.3.5)
- TailwindVariants.NET (>= 0.2.9)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.0.0-preview.2 | 41 | 11/19/2026 |
| 1.0.0-preview.1 | 93 | 11/17/2026 |
| 0.9.2-alpha | 162 | 6/9/2026 |
| 0.9.1-alpha | 106 | 6/9/2026 |
| 0.9.0-alpha | 143 | 2/7/2026 |
| 0.8.6-alpha | 269 | 5/26/2025 |
| 0.8.5-alpha | 211 | 5/23/2025 |
| 0.8.0-alpha | 253 | 5/6/2025 |
| 0.7.0-alpha | 301 | 4/20/2025 |
| 0.6.2-alpha | 577 | 3/25/2025 |
| 0.6.1-alpha | 271 | 3/10/2025 |
| 0.6.0-alpha | 343 | 3/6/2025 |
| 0.5.0-alpha | 215 | 3/2/2025 |