@alfadocs/ui-kit-debug 1.91.0 → 1.92.0

package/README.md

@@ -79,6 +79,30 @@ properties are available everywhere:
 import '@alfadocs/ui-kit/tokens';
 ```
 
+This full stylesheet includes all four third-party bridges. For an app that
+uses only part of the kit, choose core and add the bridges its components need:
+
+```ts
+import '@alfadocs/ui-kit/styles/core.css';
+import '@alfadocs/ui-kit/styles/ag-grid.css'; // DataTable
+```
+
+| Add after core                             | Components and patterns that need it                                                                                 |
+| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
+| `@alfadocs/ui-kit/styles/ag-grid.css`      | `DataTable`, `PatientTable`, `FileManager` (list view), Heatmap's "View as table", and the calendar pattern's sheets |
+| `@alfadocs/ui-kit/styles/redactor.css`     | `RichTextEditor` with the host's Redactor runtime, `NotesPanel`, `help-me-write-templates`                           |
+| `@alfadocs/ui-kit/styles/fullcalendar.css` | `Calendar`, `CalendarWorkspace` and the calendar patterns                                                            |
+| `@alfadocs/ui-kit/styles/apexcharts.css`   | `Chart`, `Sparkline`, and the anamnesis indicators, compare panel and evolution grid                                 |
+
+Anything else that renders one of these components needs the same bridge.
+
+Choose either `tokens` or core plus the required bridges. Core keeps all
+tokens, themes, base rules, component utilities and kit font declarations.
+Date pickers and booking components need no bridge. Vendor JavaScript and
+optional peer dependencies are still installed or supplied as before.
+Load core first so it establishes the CSS layer order. If copying built
+stylesheets, keep them beside the `fonts/` directory, as with `tokens.css`.
+
 Then apply a theme class on the root element:
 
 ```html