The pain it solves: Fully custom design usually means an expensive developer engagement every time you want to update colors, fonts, or layout.

How it helps:

• Built-in design/theming tools let administrators tailor colors, fonts, and layout options directly from Backstage — no code required for common adjustments.
• Auto theme mode (light/dark switching) is supported out of the box, so your site adapts to visitor preference automatically.
• Because design settings are stored as platform configuration rather than hard-coded, changes apply instantly across the whole site — no redeploy needed.
• For organizations that do want deeper customization, the same clean architecture that powers the rest of the platform makes bespoke design work straightforward for a developer, without fighting the platform's conventions.

The happy workday: Update your brand colors or try a new look in minutes, not a multi-week development cycle.

Why This Matters for Your Organization

Design tailoring that doesn't require a developer for every tweak means your site can evolve alongside your brand — a rebrand, a seasonal look, or an accessibility improvement can happen on your own schedule.

Technical Details

Design/theme configuration is implemented in ExireNexus.Backstage/Components/Editors/Developer/Settings/Design.razor, backed by SettingsService (ExireNexus.Services/Services/System/SettingsService.cs) and the SystemSettings enum definitions (ExireNexus.Shared/Enums/SystemSettings.cs).

Key implementation points:

• Settings are persisted as key-value configuration rather than compiled into the UI, so theme changes take effect without a rebuild or redeploy — read at render time by the Blazor components that consume them.
• The UI layer uses Fluent UI Blazor v4 components, which have built-in support for light/dark/auto color modes, letting the platform offer auto theme switching without custom CSS-variable plumbing.
• Because theme settings are scoped per tenant, each organization's design choices are fully isolated from others sharing the same deployment.
• For deeper, code-level customization, the platform's Clean Architecture separation (Shared components, Web/Backstage projects) means a developer can override specific components or styles without needing to modify core platform logic.

This balances "tailor it yourself" simplicity for common design changes with a clean, extensible foundation for organizations that need bespoke development.