FancyBlazor
Blazor, with better lighting.
Blazor is a strong way to build a site, but visual polish usually means dragging in a JavaScript stack you did not want. FancyBlazor keeps the effects in Blazor: components with typed parameters, wrapped around ordinary semantic content.
Wrap a section in a background, add a glowing border, reveal content as it scrolls into view, tilt a card toward the pointer, or rotate the words in a headline. The content underneath stays real HTML. When JavaScript, WebGL, or motion is unavailable — or the visitor has asked for reduced motion — you get a static palette-derived fallback instead of a broken page.
It targets .NET 10 and works with static SSR, Interactive Server, Interactive WebAssembly, and Interactive Auto. An optional WebGL companion package adds shader effects without pulling Three.js into apps that do not want it, and an optional UI companion adds styled site controls. A live demo catalogs the components.
FancyBlazor is MIT-licensed and in preview: the API may change before 1.0. It is published as-is and maintained on a best-effort basis.
[Lights up on FancyBlazor. The content was already standing there; it just looks better now.]
Features
- No. 01
Works in every render mode
Static SSR, Interactive Server, WebAssembly, and Auto, with no script tag, npm package, or CDN.
- No. 02
Semantic first
Your content stays ordinary HTML. Decorative layers are hidden from assistive technology.
- No. 03
Degrades gracefully
Static fallbacks when JavaScript, WebGL, or motion is unavailable, and it honors prefers-reduced-motion.
- No. 04
Effects as components
Backgrounds, glow borders, reveals, parallax, tilt, and kinetic text as Blazor components with typed parameters.