RazorComponentEndpoints

You write Blazor components the way you always have — @page, @inject, OnInitialized, <AuthorizeView>, @layout — and each routed component becomes an ASP.NET Core endpoint that returns plain HTML. Use any HTML client; the design assumption is htmx, but nothing in the library requires it.

Why

Blazor's static rendering is great, but the SSR pipeline assumes a model-binding / circuit world that you don't want when your interactivity comes from htmx. This library is the thin layer that lets you keep the Razor authoring experience without dragging in <EditForm>, anti-forgery, render modes, or SignalR.

Where to go from here

• Install — add the package source and pull the package.
• Quick start — minimal hello-world.
• Authoring patterns — @page, @layout, parameter binding, auth, redirect, 404.
• Gotchas — things that look like Blazor but aren't.
• How it works — the render pipeline, end to end.