@mario_hahn/jumpy-ui 0.6.1 → 0.7.0

package/README.md

@@ -1,5 +1,35 @@
 # @mario_hahn/jumpy-ui
 
+## Theme overrides
+
+Use semantic colors for brand-wide changes and action overrides for individual
+states. For example, `createJumpyThemeFromPreset('jumpy-dark', { color: {
+surfacePrimary: '#234567' } })` also updates the primary action's default surface
+CSS variable. Explicit `actions.primary.regular` state values take precedence.
+Generated semantic color dependencies propagate color fields to their CSS aliases.
+
+Individual CSS tokens can be set on the provider, including for its portals:
+
+```tsx
+<JumpyThemeProvider theme={theme} tokens={{
+  '--jumpy-actions-primary-regular-default-surface': '#234567',
+}}>
+  <App />
+</JumpyThemeProvider>
+```
+
+Provider variables are emitted in zero-specificity `:where([data-jumpy-scope])`
+stylesheet rules. Application rules such as `[data-jumpy-theme] { ... }` can override
+them without `!important`. Nested providers have independent scopes; portaled content
+reuses its originating provider's scope. A `:root`-only value is inherited and cannot
+override a variable declared directly on a theme scope; target `[data-jumpy-theme]`
+or use the provider's `tokens` prop instead. Token props change CSS variables, not
+the values returned by `useJumpyTheme()`.
+
+The Jumpy presets use brand orange `#FF5C00`, hover/pressed `#E05200`, with white
+primary text/icons. This is roughly 3:1 contrast, not 4.5:1; semibold alone does
+not qualify small button labels for WCAG's large-text exception.
+
 Jumpy Components als ein gemeinsames UI-Paket.
 
 ## Rule
@@ -12,7 +42,7 @@ Jumpy Components als ein gemeinsames UI-Paket.
 Starting with 0.5.0, Jumpy UI uses the public npmjs registry. No package token is required to install:
 
 ```bash
-npm install @mario_hahn/jumpy-ui@^0.6.0
+npm install @mario_hahn/jumpy-ui@^0.7.0
 ```
 
 The public npm package uses the `@mario_hahn` scope. Older GitHub Packages releases