@contentful/experiences-design 0.7.10 → 0.8.0

package/CHANGELOG.md

@@ -1,3 +1,15 @@
+## 0.8.0 (2026-08-28)
+
+### 🧱 Updated Dependencies
+
+- Updated core to 0.8.0
+
+## 0.7.11 (2026-08-28)
+
+### 🧱 Updated Dependencies
+
+- Updated core to 0.7.11
+
 ## 0.7.10 (2026-08-27)
 
 ### 🧱 Updated Dependencies

package/README.md

@@ -16,6 +16,8 @@ Pure, framework-agnostic viewport math for resolving Contentful's `DesignPropVal
 
 ## `toCss` and the CSS-property whitelist
 
+`toCss` is a companion to the design-hook escape hatch, not part of the recommended styling path. Components should style from their auto-filled design props, where they read the keys they declared and there is nothing to filter — see [Styling components](../../README.md#styling-components). `toCss` earns its place when you're holding a whole resolved record from `useDesignValues()` / `getDesignValues()` / `injectDesignValues()` and need the CSS-shaped subset of it.
+
 The adapters' `toCss` helper keeps only keys whose normalized form is in `CSS_PROPERTIES` and **drops everything else** — that's how semantic design values (`variant`, `as`, `ratio`, …) stay out of a style object. The trade-off is that a genuine CSS property missing from the set is dropped silently.
 
 If you hit that:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentful/experiences-design",
-  "version": "0.7.10",
+  "version": "0.8.0",
   "description": "Viewport math and design-property resolution utilities for Contentful Experiences",
   "license": "MIT",
   "type": "module",
@@ -30,6 +30,6 @@
     "directory": "packages/design"
   },
   "dependencies": {
-    "@contentful/experiences-sdk-core": "0.7.10"
+    "@contentful/experiences-sdk-core": "0.8.0"
   }
 }