Overview

Alright, so you’ve got RizzyUI installed and configured (or you’re thinking about it!). Now, let’s peek under the hood a bit. Understanding the why behind RizzyUI’s design choices will make using it much smoother and help you customize things effectively.

Think of this section as the conceptual foundation. We’re not diving deep into every component parameter here (that’s what the Components section is for!), but rather exploring the main pillars that hold RizzyUI together:

1. Styling Philosophy: How do components get their looks? We’ll talk about Tailwind CSS, design tokens (CSS variables), and how you can add your own styles without breaking things.
2. Theming: How can you change the overall appearance (colors, borders, dark mode) easily and consistently across all components? This covers the <RizzyThemeProvider /> and creating custom themes.
3. Client-Side Interactivity: How do things like dropdowns open or modals appear without Blazor’s full interactive modes? We’ll touch on the role of Alpine.js.
4. Accessibility (A11y): How does RizzyUI ensure components are usable by everyone, including those using assistive technologies?

Grasping these core concepts will give you the context needed to leverage RizzyUI effectively in your server-rendered ASP.NET applications. Let’s dive in, starting with how components are styled.