Skip to main content

Blazor UI (Refraction)

Overview​

Refraction is the Mississippi UX component library for Blazor applications.

Its defining model is state down and events up: components receive state through parameters and report user intent through events so application logic remains outside the component and composes cleanly with external state management.

Why This Area Exists​

Use Refraction when you want a UI layer that keeps rendering concerns and interaction contracts separate from application state and domain behavior.

It is meant to make Blazor component composition cleaner, more reusable, and easier to pair with external state-management approaches.

Representative Packages​

  • Mississippi.Refraction.Abstractions
  • Mississippi.Refraction.Client
  • Mississippi.Refraction.Client.StateManagement

What This Area Owns​

  • Reusable Blazor UI components
  • Contracts and conventions for state-down, events-up component design
  • Composition helpers for applications that want to build on the Refraction interaction model

How It Fits Mississippi​

Refraction is a UI-layer concern and can be used independently.

It is not the state-management layer. Reservoir is the Redux-style state-management subsystem that can sit underneath Refraction-based applications when that composition is useful.

Use This Section​

Start here when you need to understand the Mississippi UI layer, the state-down and events-up contract, or how Refraction relates to Reservoir in client applications.

Current Coverage​

This section now includes typed boundary pages for getting started, concepts, package selection, reference, and troubleshooting.

They make the Refraction boundary explicit while deeper component and pattern documentation is still being written.

Learn More​