Incrementally Migrate Layout, Theming, and Modules from MudBlazor to Radzen

[sfmskywalker]

Goal

Incrementally transition Elsa Studio UI towards Radzen Blazor, first converting core layout/theming and shared UI shells, followed by module-level work. This ensures central app functionality is preserved and migration is parallelizable.

Phases

Phase 1: Core Layout & Theming

• Migrate BasicLayout.razor (src/framework/Elsa.Studio.Shared/Layouts/BasicLayout.razor) and MainLayout.razor & .razor.cs (src/framework/Elsa.Studio.Shared/Layouts/MainLayout.razor), including theme providers, snackbar, dialog, and popover logic.
• Update all hosts to use Radzen providers and CSS/JS (see host files in audit issue for links).

Phase 2: Module/Component Migration

• For each module below:

  • Remove MudBlazor/MudExtensions from _Imports.razor, individual components, and view models.
  • Replace with Radzen equivalents, update imports/usings and member types.
  • Migrate themes, layout references, and styles.

• Elsa.Studio.UIHints: Module Link

• Elsa.Studio.Workflows.Designer: Module Link

• Elsa.Studio.Login: Module Link

• Elsa.Studio.Localization: Module Link

• Elsa.Studio.Security: Module Link

• Elsa.Studio.Counter: Module Link

• Elsa.Studio.Dashboard: Module Link

(Adjust breakdown as needed based on sub-component audits. Include references to key components in each module.)

Deliverables

• PRs per phased migration
• Status documentation per module
• References to updated files in checklists