sufi-chain/sufi-blazor
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update documentation and references from Wish Theme to KomTheme across various files, including README, installation guides, and component documentation. Add NuGet.Config to solution structure.
Release NuGet Packages / pack-and-push (release) Successful in 8m35s
Details

Browse Source
This commit is contained in:
Pooria Shariatzadeh
2026-05-25 19:27:29 +03:30
parent e1474c232b
commit 6a0e724eb0
25 changed files with 57 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -2
View File
@@ -5,7 +5,7 @@
[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
[![Repository](https://img.shields.io/badge/git-git.sabp.ir-2b6df6.svg)](https://git.sabp.ir/sufi-chain/sufi-blazor) [![Repository](https://img.shields.io/badge/git-git.sabp.ir-2b6df6.svg)](https://git.sabp.ir/sufi-chain/sufi-blazor)
SufiBlazor is an independent Blazor UI component library and design system for ASP.NET Core 10+ applications. It can be used inside Sufi Platform, but it is not tied to Sufi Platform, ABP, Wish Theme, or any other third-party application framework. Any Blazor project that targets modern ASP.NET Core can use it as its primary UI layer. SufiBlazor is an independent Blazor UI component library and design system for ASP.NET Core 10+ applications. It can be used inside Sufi Platform, but it is not tied to Sufi Platform, ABP, KomTheme, or any other third-party application framework. Any Blazor project that targets modern ASP.NET Core can use it as its primary UI layer.
For Sufi Platform, SufiBlazor is the default component system used by generated hosts and first-party modules. Outside Sufi Platform, it can still be adopted on its own as a self-contained component library for forms, data display, overlays, navigation, theming, RTL support, and application-level UI composition. For Sufi Platform, SufiBlazor is the default component system used by generated hosts and first-party modules. Outside Sufi Platform, it can still be adopted on its own as a self-contained component library for forms, data display, overlays, navigation, theming, RTL support, and application-level UI composition.
@@ -50,7 +50,7 @@ In other words, SufiBlazor is a standalone product that Sufi Platform consumes,
Inside Sufi Platform: Inside Sufi Platform:
- `SufiBlazor` provides the base UI component system - `SufiBlazor` provides the base UI component system
- `Wish Theme` provides the host shell, layout, and branded navigation frame - `KomTheme` provides the host shell, layout, and branded navigation frame
- `SufiAbp` provides the broader platform abstractions and host integration patterns - `SufiAbp` provides the broader platform abstractions and host integration patterns
That relationship is important, but it should not hide the fact that SufiBlazor can also be used on its own in any Blazor project targeting ASP.NET Core 10+. That relationship is important, but it should not hide the fact that SufiBlazor can also be used on its own in any Blazor project targeting ASP.NET Core 10+.
SufiChain.SufiBlazor.slnx
+2 -1
View File
@@ -1,11 +1,12 @@
<Solution> <Solution>
<Folder Name="/Solution Items/"> <Folder Name="/Solution Items/">
<File Path="NuGet.Config" />
<File Path="versions.props" /> <File Path="versions.props" />
</Folder> </Folder>
<Folder Name="/src/"> <Folder Name="/src/">
<Project Path="src/SufiChain.SufiBlazor/SufiChain.SufiBlazor.csproj" />
<Project Path="src/SufiChain.SufiBlazor.Demo.Localization/SufiChain.SufiBlazor.Demo.Localization.csproj" /> <Project Path="src/SufiChain.SufiBlazor.Demo.Localization/SufiChain.SufiBlazor.Demo.Localization.csproj" />
<Project Path="src/SufiChain.SufiBlazor.Demo/SufiChain.SufiBlazor.Demo.csproj" /> <Project Path="src/SufiChain.SufiBlazor.Demo/SufiChain.SufiBlazor.Demo.csproj" />
<Project Path="src/SufiChain.SufiBlazor/SufiChain.SufiBlazor.csproj" />
</Folder> </Folder>
<Folder Name="/tests/"> <Folder Name="/tests/">
<Project Path="tests/SufiChain.SufiBlazor.Tests.csproj" /> <Project Path="tests/SufiChain.SufiBlazor.Tests.csproj" />
docs/README.md
+2 -2
View File
@@ -1,6 +1,6 @@
# SufiBlazor # SufiBlazor
SufiBlazor is an independent Blazor UI component library and design system for ASP.NET Core 10+ applications. It can be used inside Sufi Platform, but it is not tied to Sufi Platform, ABP, Wish Theme, or any other third-party application framework. Any Blazor project that targets modern ASP.NET Core can use it as its primary UI layer. SufiBlazor is an independent Blazor UI component library and design system for ASP.NET Core 10+ applications. It can be used inside Sufi Platform, but it is not tied to Sufi Platform, ABP, KomTheme, or any other third-party application framework. Any Blazor project that targets modern ASP.NET Core can use it as its primary UI layer.
For Sufi Platform, SufiBlazor is the default component system used by generated hosts and first-party modules. Outside Sufi Platform, it can still be adopted on its own as a self-contained component library for forms, data display, overlays, navigation, theming, RTL support, and application-level UI composition. For Sufi Platform, SufiBlazor is the default component system used by generated hosts and first-party modules. Outside Sufi Platform, it can still be adopted on its own as a self-contained component library for forms, data display, overlays, navigation, theming, RTL support, and application-level UI composition.
@@ -30,7 +30,7 @@ In other words, SufiBlazor is a standalone product that Sufi Platform consumes,
Inside Sufi Platform: Inside Sufi Platform:
- `SufiBlazor` provides the base UI component system - `SufiBlazor` provides the base UI component system
- `Wish Theme` provides the host shell, layout, and branded navigation frame - `KomTheme` provides the host shell, layout, and branded navigation frame
- `SufiAbp` provides the broader platform abstractions and host integration patterns - `SufiAbp` provides the broader platform abstractions and host integration patterns
That relationship is important, but it should not hide the fact that SufiBlazor can also be used on its own in any Blazor project targeting ASP.NET Core 10+. That relationship is important, but it should not hide the fact that SufiBlazor can also be used on its own in any Blazor project targeting ASP.NET Core 10+.
docs/assets/sufi-chain.png
BIN
View File
Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 143 KiB

After

Width:  |  Height:  |  Size: 45 KiB

docs/components.md
+2 -2
View File
@@ -27,13 +27,13 @@ Feature-oriented catalog. See **SufiChain.SufiBlazorDemo** and component XML doc
- **SbStack** — Flex row/column, gap, justify, align. - **SbStack** — Flex row/column, gap, justify, align.
- **SbGrid** — CSS grid; column counts, gap. - **SbGrid** — CSS grid; column counts, gap.
- **SbAppShell**, **SbSidebar** — App chrome; Wish Theme uses these. - **SbAppShell**, **SbSidebar** — App chrome; KomTheme uses these.
## Navigation ## Navigation
- **SbTabs** / **SbTab** — Tabbed content. - **SbTabs** / **SbTab** — Tabbed content.
- **SbBreadcrumb** / **SbBreadcrumbItem** — Breadcrumbs. - **SbBreadcrumb** / **SbBreadcrumbItem** — Breadcrumbs.
- **SbNavMenu** / **SbNavItem** — Hierarchical nav; used in Wish layouts. - **SbNavMenu** / **SbNavItem** — Hierarchical nav; used in Kom layouts.
## Overlays ## Overlays
docs/components/layout/LAYOUT_REVIEW.md
+14 -14
View File
@@ -1,34 +1,34 @@
# SufiBlazor Layout Components – Review vs Wish Theme # SufiBlazor Layout Components – Review vs KomTheme
## Summary ## Summary
The **Wish theme uses its own layout components** (`WishAppShell`, `WishDualSidebar`, `WishTopBar`, `WishSidebar`, `WishIconRail`, `WishExpandPanel`) in `SufiChain.SufiAbp.WishTheme.Blazor/Components/Layout/`. The SufiBlazor design system shell components (`SbAppShell`, `SbDualSidebar`, `SbTopBar`, `SbSidebar`, `SbIconRail`, `SbExpandPanel`) are **not used** in any application or in the Wish theme. The **KomTheme uses its own layout components** (`KomAppShell`, `KomDualSidebar`, `KomTopBar`, `KomSidebar`, `KomIconRail`, `KomExpandPanel`) in `SufiChain.KomTheme.Blazor/Components/Layout/`. The SufiBlazor design system shell components (`SbAppShell`, `SbDualSidebar`, `SbTopBar`, `SbSidebar`, `SbIconRail`, `SbExpandPanel`) are **not used** in any application or in the KomTheme.
## Usage by Component ## Usage by Component
| Component | Used in Wish theme? | Used elsewhere? | Verdict | | Component | Used in KomTheme? | Used elsewhere? | Verdict |
|-----------|---------------------|-----------------|---------| |-----------|---------------------|-----------------|---------|
| **SbContainer** | Yes – `TopMenuLayout.razor` | SufiBlazorDemo | **KEEP** | | **SbContainer** | Yes – `TopMenuLayout.razor` | SufiBlazorDemo | **KEEP** |
| **SbContainerMaxWidth** | Yes – with SbContainer | SufiBlazorDemo | **KEEP** | | **SbContainerMaxWidth** | Yes – with SbContainer | SufiBlazorDemo | **KEEP** |
| **SbAppShell** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishAppShell | | **SbAppShell** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomAppShell |
| **SbAppShellVariant** | No | No (not even used by SbAppShell) | **REMOVED** – dead code | | **SbAppShellVariant** | No | No (not even used by SbAppShell) | **REMOVED** – dead code |
| **SbDualSidebar** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishDualSidebar | | **SbDualSidebar** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomDualSidebar |
| **SbTopBar** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishTopBar | | **SbTopBar** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomTopBar |
| **SbSidebar** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishSidebar | | **SbSidebar** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomSidebar |
| **SbIconRail** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishIconRail | | **SbIconRail** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomIconRail |
| **SbExpandPanel** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishExpandPanel | | **SbExpandPanel** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomExpandPanel |
| **SbStack** | Yes (class names in layouts) | Identity, FileManager, Audit, Feature, Setting modules | **KEEP** | | **SbStack** | Yes (class names in layouts) | Identity, FileManager, Audit, Feature, Setting modules | **KEEP** |
| **SbAlign, SbJustify, SbStackDirection** | Yes | Many modules | **KEEP** | | **SbAlign, SbJustify, SbStackDirection** | Yes | Many modules | **KEEP** |
| **SbGrid, SbGridItem** | No | SufiBlazorDemo only | **KEEP** – design system primitives | | **SbGrid, SbGridItem** | No | SufiBlazorDemo only | **KEEP** – design system primitives |
| **SbSpacer** | No | SufiBlazorDemo only | **KEEP** – design system primitive | | **SbSpacer** | No | SufiBlazorDemo only | **KEEP** – design system primitive |
## Wish Theme Layouts ## KomTheme Layouts
- **DualSidebarLayout.razor** – Uses `WishAppShell`, `WishDualSidebar`, `WishIconRail`, `WishExpandPanel`, `WishTopBar`. - **DualSidebarLayout.razor** – Uses `KomAppShell`, `KomDualSidebar`, `KomIconRail`, `KomExpandPanel`, `KomTopBar`.
- **SideMenuLayout.razor** – Uses `WishAppShell`, `WishSidebar`, `WishTopBar`. - **SideMenuLayout.razor** – Uses `KomAppShell`, `KomSidebar`, `KomTopBar`.
- **TopMenuLayout.razor** – Uses `WishTopBar`, **SbContainer** (only Sb layout component used), `SbDrawer`, `SbNavMenu`, etc. - **TopMenuLayout.razor** – Uses `KomTopBar`, **SbContainer** (only Sb layout component used), `SbDrawer`, `SbNavMenu`, etc.
## Conclusion ## Conclusion
- **Keep:** SbContainer, SbContainerMaxWidth, SbStack, SbAlign, SbJustify, SbStackDirection, SbGrid, SbGridItem, SbSpacer (used by apps or by design-system demo). - **Keep:** SbContainer, SbContainerMaxWidth, SbStack, SbAlign, SbJustify, SbStackDirection, SbGrid, SbGridItem, SbSpacer (used by apps or by design-system demo).
- **Removed:** SbAppShell, SbAppShellVariant, SbDualSidebar, SbTopBar, SbSidebar, SbIconRail, SbExpandPanel – unused and redundant with Wish theme components; removing them avoids confusion and mistaken use during feature development. - **Removed:** SbAppShell, SbAppShellVariant, SbDualSidebar, SbTopBar, SbSidebar, SbIconRail, SbExpandPanel – unused and redundant with KomTheme components; removing them avoids confusion and mistaken use during feature development.
docs/components/layout/SbContainer.md
+1 -1
View File
@@ -84,7 +84,7 @@ public enum SbContainerMaxWidth
### Page Layout ### Page Layout
Use `SbContainer` inside your layout (e.g. Wish theme layouts use it for main content): Use `SbContainer` inside your layout (e.g. KomTheme layouts use it for main content):
```razor ```razor
<SbContainer MaxWidth="SbContainerMaxWidth.Xl"> <SbContainer MaxWidth="SbContainerMaxWidth.Xl">
docs/components/layout/SbSpacer.md
+1 -1
View File
@@ -93,7 +93,7 @@ public enum SbSpacerSize
### In Navigation Menu ### In Navigation Menu
Use `SbSpacer Grow="true"` inside a vertical stack to push items to the bottom (e.g. in Wish theme's `WishSidebar` or `WishIconRail`): Use `SbSpacer Grow="true"` inside a vertical stack to push items to the bottom (e.g. in KomTheme's `KomSidebar` or `KomIconRail`):
```razor ```razor
<SbStack Direction="SbStackDirection.Column" Gap="0"> <SbStack Direction="SbStackDirection.Column" Gap="0">
docs/components/navigation/SbBreadcrumb.md
+1 -1
View File
@@ -123,7 +123,7 @@ public class SbBreadcrumbItem
### In Page Layout ### In Page Layout
Breadcrumbs are typically rendered in the layout's top bar (e.g. Wish theme's `WishTopBar`). Content area example: Breadcrumbs are typically rendered in the layout's top bar (e.g. KomTheme's `KomTopBar`). Content area example:
```razor ```razor
<SbContainer> <SbContainer>
docs/components/navigation/SbNavMenu.md
+1 -1
View File
@@ -55,7 +55,7 @@ A navigation menu container component for organizing navigation items.
### Inside a layout sidebar ### Inside a layout sidebar
Use `SbNavMenu` inside the Wish theme's sidebar (e.g. `WishSidebar` or `WishExpandPanel`): Use `SbNavMenu` inside the KomTheme's sidebar (e.g. `KomSidebar` or `KomExpandPanel`):
```razor ```razor
<SbNavMenu> <SbNavMenu>
docs/components/overlays/SbTooltip.md
+1 -1
View File
@@ -122,7 +122,7 @@ A lightweight tooltip component that appears on hover or focus to provide additi
### Icon rail tooltips ### Icon rail tooltips
In an icon rail (e.g. Wish theme's `WishIconRail`), wrap nav items with `SbTooltip` and `Placement="SbPlacement.End"` so the tooltip appears to the right: In an icon rail (e.g. KomTheme's `KomIconRail`), wrap nav items with `SbTooltip` and `Placement="SbPlacement.End"` so the tooltip appears to the right:
```razor ```razor
<SbStack Direction="SbStackDirection.Column" Gap="1"> <SbStack Direction="SbStackDirection.Column" Gap="1">
docs/components/theming/SbThemeProvider.md
+1 -1
View File
@@ -115,7 +115,7 @@ Place `SbThemeProvider` at the root of your application:
### Full Application Setup ### Full Application Setup
App shell and top bar are provided by the **Wish theme** (e.g. `WishAppShell`, `WishTopBar`). For a minimal layout using only SufiBlazor primitives: App shell and top bar are provided by the **KomTheme** (e.g. `KomAppShell`, `KomTopBar`). For a minimal layout using only SufiBlazor primitives:
```razor ```razor
@* Minimal layout using design system only *@ @* Minimal layout using design system only *@
docs/installation.md
+2 -2
View File
@@ -59,10 +59,10 @@ Create a simple page with a few components such as `SbCard`, `SbButton`, and `Sb
If the host already uses Sufi Platform conventions: If the host already uses Sufi Platform conventions:
- SufiBlazor is usually part of the expected UI stack already - SufiBlazor is usually part of the expected UI stack already
- Wish Theme builds on top of SufiBlazor rather than replacing it - KomTheme builds on top of SufiBlazor rather than replacing it
- the same package, static asset, and theme-provider concepts still apply - the same package, static asset, and theme-provider concepts still apply
## Optional notes ## Optional notes
- If your app uses dialog, toast, or similar UI services, follow the host-specific registration guidance used by your application. - If your app uses dialog, toast, or similar UI services, follow the host-specific registration guidance used by your application.
- If Wish Theme is part of the host, it still depends on SufiBlazor as the base component system. - If KomTheme is part of the host, it still depends on SufiBlazor as the base component system.
docs/overview.md
+1 -1
View File
@@ -44,7 +44,7 @@ You can use SufiBlazor in:
When SufiBlazor is used inside Sufi Platform: When SufiBlazor is used inside Sufi Platform:
- it provides the base interactive component layer - it provides the base interactive component layer
- Wish Theme builds the host shell and layout on top of it - KomTheme builds the host shell and layout on top of it
- SufiAbp provides the platform abstractions, host wiring, and module composition rules around it - SufiAbp provides the platform abstractions, host wiring, and module composition rules around it
That relationship matters for platform developers, but the library remains usable outside that stack. That relationship matters for platform developers, but the library remains usable outside that stack.
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/LAYOUT_REVIEW.md
+14 -14
View File
@@ -1,34 +1,34 @@
# SufiBlazor Layout Components – Review vs Wish Theme # SufiBlazor Layout Components – Review vs KomTheme
## Summary ## Summary
The **Wish theme uses its own layout components** (`WishAppShell`, `WishDualSidebar`, `WishTopBar`, `WishSidebar`, `WishIconRail`, `WishExpandPanel`) in `SufiChain.SufiAbp.WishTheme.Blazor/Components/Layout/`. The SufiBlazor design system shell components (`SbAppShell`, `SbDualSidebar`, `SbTopBar`, `SbSidebar`, `SbIconRail`, `SbExpandPanel`) are **not used** in any application or in the Wish theme. The **KomTheme uses its own layout components** (`KomAppShell`, `KomDualSidebar`, `KomTopBar`, `KomSidebar`, `KomIconRail`, `KomExpandPanel`) in `SufiChain.KomTheme.Blazor/Components/Layout/`. The SufiBlazor design system shell components (`SbAppShell`, `SbDualSidebar`, `SbTopBar`, `SbSidebar`, `SbIconRail`, `SbExpandPanel`) are **not used** in any application or in the KomTheme.
## Usage by Component ## Usage by Component
| Component | Used in Wish theme? | Used elsewhere? | Verdict | | Component | Used in KomTheme? | Used elsewhere? | Verdict |
|-----------|---------------------|-----------------|---------| |-----------|---------------------|-----------------|---------|
| **SbContainer** | Yes – `TopMenuLayout.razor` | SufiBlazorDemo | **KEEP** | | **SbContainer** | Yes – `TopMenuLayout.razor` | SufiBlazorDemo | **KEEP** |
| **SbContainerMaxWidth** | Yes – with SbContainer | SufiBlazorDemo | **KEEP** | | **SbContainerMaxWidth** | Yes – with SbContainer | SufiBlazorDemo | **KEEP** |
| **SbAppShell** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishAppShell | | **SbAppShell** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomAppShell |
| **SbAppShellVariant** | No | No (not even used by SbAppShell) | **REMOVED** – dead code | | **SbAppShellVariant** | No | No (not even used by SbAppShell) | **REMOVED** – dead code |
| **SbDualSidebar** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishDualSidebar | | **SbDualSidebar** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomDualSidebar |
| **SbTopBar** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishTopBar | | **SbTopBar** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomTopBar |
| **SbSidebar** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishSidebar | | **SbSidebar** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomSidebar |
| **SbIconRail** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishIconRail | | **SbIconRail** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomIconRail |
| **SbExpandPanel** | No | No (docs only) | **REMOVED** – redundant; Wish uses WishExpandPanel | | **SbExpandPanel** | No | No (docs only) | **REMOVED** – redundant; Kom uses KomExpandPanel |
| **SbStack** | Yes (class names in layouts) | Identity, FileManager, Audit, Feature, Setting modules | **KEEP** | | **SbStack** | Yes (class names in layouts) | Identity, FileManager, Audit, Feature, Setting modules | **KEEP** |
| **SbAlign, SbJustify, SbStackDirection** | Yes | Many modules | **KEEP** | | **SbAlign, SbJustify, SbStackDirection** | Yes | Many modules | **KEEP** |
| **SbGrid, SbGridItem** | No | SufiBlazorDemo only | **KEEP** – design system primitives | | **SbGrid, SbGridItem** | No | SufiBlazorDemo only | **KEEP** – design system primitives |
| **SbSpacer** | No | SufiBlazorDemo only | **KEEP** – design system primitive | | **SbSpacer** | No | SufiBlazorDemo only | **KEEP** – design system primitive |
## Wish Theme Layouts ## KomTheme Layouts
- **DualSidebarLayout.razor** – Uses `WishAppShell`, `WishDualSidebar`, `WishIconRail`, `WishExpandPanel`, `WishTopBar`. - **DualSidebarLayout.razor** – Uses `KomAppShell`, `KomDualSidebar`, `KomIconRail`, `KomExpandPanel`, `KomTopBar`.
- **SideMenuLayout.razor** – Uses `WishAppShell`, `WishSidebar`, `WishTopBar`. - **SideMenuLayout.razor** – Uses `KomAppShell`, `KomSidebar`, `KomTopBar`.
- **TopMenuLayout.razor** – Uses `WishTopBar`, **SbContainer** (only Sb layout component used), `SbDrawer`, `SbNavMenu`, etc. - **TopMenuLayout.razor** – Uses `KomTopBar`, **SbContainer** (only Sb layout component used), `SbDrawer`, `SbNavMenu`, etc.
## Conclusion ## Conclusion
- **Keep:** SbContainer, SbContainerMaxWidth, SbStack, SbAlign, SbJustify, SbStackDirection, SbGrid, SbGridItem, SbSpacer (used by apps or by design-system demo). - **Keep:** SbContainer, SbContainerMaxWidth, SbStack, SbAlign, SbJustify, SbStackDirection, SbGrid, SbGridItem, SbSpacer (used by apps or by design-system demo).
- **Removed:** SbAppShell, SbAppShellVariant, SbDualSidebar, SbTopBar, SbSidebar, SbIconRail, SbExpandPanel – unused and redundant with Wish theme components; removing them avoids confusion and mistaken use during feature development. - **Removed:** SbAppShell, SbAppShellVariant, SbDualSidebar, SbTopBar, SbSidebar, SbIconRail, SbExpandPanel – unused and redundant with KomTheme components; removing them avoids confusion and mistaken use during feature development.
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/SbBreadcrumb.md
+1 -1
View File
@@ -123,7 +123,7 @@ public class SbBreadcrumbItem
### In Page Layout ### In Page Layout
Breadcrumbs are typically rendered in the layout's top bar (e.g. Wish theme's `WishTopBar`). Content area example: Breadcrumbs are typically rendered in the layout's top bar (e.g. KomTheme's `KomTopBar`). Content area example:
```razor ```razor
<SbContainer> <SbContainer>
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/SbContainer.md
+1 -1
View File
@@ -84,7 +84,7 @@ public enum SbContainerMaxWidth
### Page Layout ### Page Layout
Use `SbContainer` inside your layout (e.g. Wish theme layouts use it for main content): Use `SbContainer` inside your layout (e.g. KomTheme layouts use it for main content):
```razor ```razor
<SbContainer MaxWidth="SbContainerMaxWidth.Xl"> <SbContainer MaxWidth="SbContainerMaxWidth.Xl">
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/SbNavMenu.md
+1 -1
View File
@@ -55,7 +55,7 @@ A navigation menu container component for organizing navigation items.
### Inside a layout sidebar ### Inside a layout sidebar
Use `SbNavMenu` inside the Wish theme's sidebar (e.g. `WishSidebar` or `WishExpandPanel`): Use `SbNavMenu` inside the KomTheme's sidebar (e.g. `KomSidebar` or `KomExpandPanel`):
```razor ```razor
<SbNavMenu> <SbNavMenu>
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/SbSpacer.md
+1 -1
View File
@@ -93,7 +93,7 @@ public enum SbSpacerSize
### In Navigation Menu ### In Navigation Menu
Use `SbSpacer Grow="true"` inside a vertical stack to push items to the bottom (e.g. in Wish theme's `WishSidebar` or `WishIconRail`): Use `SbSpacer Grow="true"` inside a vertical stack to push items to the bottom (e.g. in KomTheme's `KomSidebar` or `KomIconRail`):
```razor ```razor
<SbStack Direction="SbStackDirection.Column" Gap="0"> <SbStack Direction="SbStackDirection.Column" Gap="0">
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/SbThemeProvider.md
+1 -1
View File
@@ -115,7 +115,7 @@ Place `SbThemeProvider` at the root of your application:
### Full Application Setup ### Full Application Setup
App shell and top bar are provided by the **Wish theme** (e.g. `WishAppShell`, `WishTopBar`). For a minimal layout using only SufiBlazor primitives: App shell and top bar are provided by the **KomTheme** (e.g. `KomAppShell`, `KomTopBar`). For a minimal layout using only SufiBlazor primitives:
```razor ```razor
@* Minimal layout using design system only *@ @* Minimal layout using design system only *@
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/SbTooltip.md
+1 -1
View File
@@ -122,7 +122,7 @@ A lightweight tooltip component that appears on hover or focus to provide additi
### Icon rail tooltips ### Icon rail tooltips
In an icon rail (e.g. Wish theme's `WishIconRail`), wrap nav items with `SbTooltip` and `Placement="SbPlacement.End"` so the tooltip appears to the right: In an icon rail (e.g. KomTheme's `KomIconRail`), wrap nav items with `SbTooltip` and `Placement="SbPlacement.End"` so the tooltip appears to the right:
```razor ```razor
<SbStack Direction="SbStackDirection.Column" Gap="1"> <SbStack Direction="SbStackDirection.Column" Gap="1">
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/components.md
+2 -2
View File
@@ -27,13 +27,13 @@ Feature-oriented catalog. See **SufiChain.SufiBlazorDemo** and component XML doc
- **SbStack** — Flex row/column, gap, justify, align. - **SbStack** — Flex row/column, gap, justify, align.
- **SbGrid** — CSS grid; column counts, gap. - **SbGrid** — CSS grid; column counts, gap.
- **SbAppShell**, **SbSidebar** — App chrome; Wish Theme uses these. - **SbAppShell**, **SbSidebar** — App chrome; KomTheme uses these.
## Navigation ## Navigation
- **SbTabs** / **SbTab** — Tabbed content. - **SbTabs** / **SbTab** — Tabbed content.
- **SbBreadcrumb** / **SbBreadcrumbItem** — Breadcrumbs. - **SbBreadcrumb** / **SbBreadcrumbItem** — Breadcrumbs.
- **SbNavMenu** / **SbNavItem** — Hierarchical nav; used in Wish layouts. - **SbNavMenu** / **SbNavItem** — Hierarchical nav; used in Kom layouts.
## Overlays ## Overlays
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/installation.md
+2 -2
View File
@@ -59,10 +59,10 @@ Create a simple page with a few components such as `SbCard`, `SbButton`, and `Sb
If the host already uses Sufi Platform conventions: If the host already uses Sufi Platform conventions:
- SufiBlazor is usually part of the expected UI stack already - SufiBlazor is usually part of the expected UI stack already
- Wish Theme builds on top of SufiBlazor rather than replacing it - KomTheme builds on top of SufiBlazor rather than replacing it
- the same package, static asset, and theme-provider concepts still apply - the same package, static asset, and theme-provider concepts still apply
## Optional notes ## Optional notes
- If your app uses dialog, toast, or similar UI services, follow the host-specific registration guidance used by your application. - If your app uses dialog, toast, or similar UI services, follow the host-specific registration guidance used by your application.
- If Wish Theme is part of the host, it still depends on SufiBlazor as the base component system. - If KomTheme is part of the host, it still depends on SufiBlazor as the base component system.
src/SufiChain.SufiBlazor.Demo/wwwroot/docs/overview.md
+1 -1
View File
@@ -44,7 +44,7 @@ You can use SufiBlazor in:
When SufiBlazor is used inside Sufi Platform: When SufiBlazor is used inside Sufi Platform:
- it provides the base interactive component layer - it provides the base interactive component layer
- Wish Theme builds the host shell and layout on top of it - KomTheme builds the host shell and layout on top of it
- SufiAbp provides the platform abstractions, host wiring, and module composition rules around it - SufiAbp provides the platform abstractions, host wiring, and module composition rules around it
That relationship matters for platform developers, but the library remains usable outside that stack. That relationship matters for platform developers, but the library remains usable outside that stack.
src/SufiChain.SufiBlazor/wwwroot/demo.css
+1 -1
View File
@@ -118,7 +118,7 @@ html {
/* Focus styles - exclude native inputs that have their own focus ring (radio/checkbox) to avoid double outline or stray focus box. /* Focus styles - exclude native inputs that have their own focus ring (radio/checkbox) to avoid double outline or stray focus box.
Exclude text/number/textarea inputs – their wrapper uses :focus-within for the focus ring. Exclude text/number/textarea inputs – their wrapper uses :focus-within for the focus ring.
Exclude headings (h1-h6) – wish-theme removes their focus ring; these would override due to higher specificity. */ Exclude headings (h1-h6) – kom-theme removes their focus ring; these would override due to higher specificity. */
.demo-layout :focus-visible:not(.sb-radio__input):not(.sb-checkbox__input):not(.sb-number-field__input):not(.sb-text-field__input):not(.sb-textarea__input):not(h1):not(h2):not(h3):not(h4):not(h5):not(h6), .demo-layout :focus-visible:not(.sb-radio__input):not(.sb-checkbox__input):not(.sb-number-field__input):not(.sb-text-field__input):not(.sb-textarea__input):not(h1):not(h2):not(h3):not(h4):not(h5):not(h6),
.docs-home :focus-visible:not(.sb-radio__input):not(.sb-checkbox__input):not(.sb-number-field__input):not(.sb-text-field__input):not(.sb-textarea__input):not(h1):not(h2):not(h3):not(h4):not(h5):not(h6), .docs-home :focus-visible:not(.sb-radio__input):not(.sb-checkbox__input):not(.sb-number-field__input):not(.sb-text-field__input):not(.sb-textarea__input):not(h1):not(h2):not(h3):not(h4):not(h5):not(h6),
.demo-section :focus-visible:not(.sb-radio__input):not(.sb-checkbox__input):not(.sb-number-field__input):not(.sb-text-field__input):not(.sb-textarea__input):not(h1):not(h2):not(h3):not(h4):not(h5):not(h6) { .demo-section :focus-visible:not(.sb-radio__input):not(.sb-checkbox__input):not(.sb-number-field__input):not(.sb-text-field__input):not(.sb-textarea__input):not(h1):not(h2):not(h3):not(h4):not(h5):not(h6) {