MudBlazor Login Form

## What's implemented - Tabbed authentication UI with "Sign In" and "Register" panels. - Login form with email and password fields, remember-me checkbox and a submit button. - Registration form with username, email, password, confirm password fields and password strength/confirm validators. - Password visibility toggle via input adornment click. - Client-side validation using DataAnnotations and custom Func validators. ## Key components - MudTabs, MudTabPanel - MudForm (Model binding, @bind-IsValid) - MudTextField (Email, Password, Confirm) - MudButton, MudCheckBox, MudLink - MudGrid, MudItem - @ref usage for MudForm and MudTextField ## How it works - Model binding uses LoginViewModel and RegisterViewModel instances as the form Models and MudForm tracks IsValid via @bind-IsValid. - Input values bind via @bind-Value on MudTextField; submit buttons use ButtonType.Submit to rely on MudForm validation state. - Password strength runs in PasswordStrength(string) returning IEnumerable<string> for field Validation; confirm password uses PasswordMatch via a Func<string,string> validator and accesses the referenced passwordField.Value. - Password visibility toggles InputType between Password and Text and swaps an adornment icon in TogglePasswordVisibility (OnAdornmentClick handler). ## Styling - Uses MudBlazor components and theming (no Tailwind or Bootstrap utilities detected). - Layout constrains width with MudContainer MaxWidth.Small and uses MudGrid/MudItem for responsive alignment (xs breakpoints used). - Visuals rely on MudBlazor defaults; additional theme configuration or CSS can adjust spacing and colors. ## Reuse steps 1. Install MudBlazor NuGet package and static assets (MudBlazor). 2. Register MudBlazor services in Program.cs (e.g., builder.Services.AddMudServices(); and add MudThemeProvider/MudDialogProvider if needed). 3. Import MudBlazor namespace in _Imports.razor or pages and include MudBlazor CSS/JS in the layout (_Host.cshtml or index.html). 4. Copy models (LoginViewModel, RegisterViewModel) and wire server-side submit handlers to replace the current client-only submit behavior. 5. Adjust validation and navigation: add authentication service, handle errors, and route to secured pages on success. ## Limitations & next steps - This is a single page generated by Instruct UI and provides client-side validation only; server-side authentication, password hashing, and API wiring are required. - No submit event handlers are implemented for actual sign-in or registration flows; integrate with an auth service and handle responses and error messages. - Consider adding loading state, accessibility attributes, localization, and unit tests for validators. - Add rate-limiting and proper server-side validation to avoid trusting client-side checks alone.

Login and Registration Screen