@c15t/react 2.0.0-rc.6 → 2.0.0-rc.8

package/dist-types/hooks/use-consent-manager.d.ts

@@ -2,7 +2,7 @@
  * @packageDocumentation
  * Hook for accessing and managing consent state.
  */
-import type { ConsentManagerInterface, ConsentStoreState } from '../../../core/dist-types/index.d.ts';
+import type { ConsentManagerInterface, ConsentStoreState } from 'c15t';
 /**
  * Hook for accessing and managing consent state.
  *

package/dist-types/hooks/use-headless-consent-ui.d.ts

@@ -1,4 +1,4 @@
-import { type PolicyUiAction, type PolicyUiActionDirection, type PolicyUiActionGroup, type PolicyUiProfile } from '../components/shared/libs/policy-actions';
+import { type PolicyUiAction, type PolicyUiActionDirection, type PolicyUiActionGroup, type PolicyUiProfile } from '@c15t/ui/utils';
 import { useConsentManager } from './use-consent-manager';
 export type HeadlessConsentSurface = 'banner' | 'dialog';
 export type HeadlessConsentSurfaceAction = PolicyUiAction;

package/dist-types/hooks/use-ssr-status.d.ts

@@ -20,8 +20,9 @@ export interface SSRStatus {
      *
      * - `'no_data'` — no `ssrData` prop was provided to the provider
      * - `'fetch_failed'` — `ssrData` was provided but the Promise resolved with no data
+     * - `'context_mismatch'` — `ssrData` did not match the current runtime request context
      */
-    ssrSkippedReason: 'no_data' | 'fetch_failed' | null;
+    ssrSkippedReason: 'no_data' | 'fetch_failed' | 'context_mismatch' | null;
 }
 /**
  * Returns information about SSR data usage.

package/dist-types/hooks/use-translations.d.ts

@@ -1,4 +1,4 @@
-import type { Translations } from '../../../core/dist-types/index.d.ts';
+import type { Translations } from 'c15t';
 /**
  * Hook for accessing translations in the current language.
  *

package/dist-types/index.d.ts

@@ -1,5 +1,5 @@
-export type { AllConsentNames, ConsentManagerInterface, ConsentStoreState, ConsentType, EuropePolicyMode, Overrides, PolicyPackPresets, Translations, } from '../../core/dist-types/index.d.ts';
-export { configureConsentManager, defaultTranslationConfig, detectBrowserLanguage, mergeTranslationConfigs, policyPackPresets, prepareTranslationConfig, } from '../../core/dist-types/index.d.ts';
+export type { AllConsentNames, ConsentManagerInterface, ConsentStoreState, ConsentType, EuropePolicyMode, Overrides, PolicyPackPresets, Translations, } from 'c15t';
+export { configureConsentManager, defaultTranslationConfig, detectBrowserLanguage, mergeTranslationConfigs, policyPackPresets, prepareTranslationConfig, } from 'c15t';
 export { ConsentBanner, type ConsentBannerProps, } from './components/consent-banner';
 export * from './components/consent-banner/components';
 export { ConsentDialog, type ConsentDialogProps, } from './components/consent-dialog';

package/dist-types/server/fetch-ssr-data.d.ts

@@ -1,4 +1,4 @@
-import type { SSRInitialData } from '../../../core/dist-types/index.d.ts';
+import type { SSRInitialData } from 'c15t';
 import type { FetchSSRDataOptions } from './types';
 /**
  * Fetches initial consent data on the server for SSR hydration.

package/dist-types/server/init-cache-key.d.ts

@@ -1,4 +1,4 @@
-import type { Overrides } from '../../../core/dist-types/index.d.ts';
+import type { Overrides } from 'c15t';
 /**
  * Creates a stable cache key for SSR init responses.
  *

package/dist-types/server/types.d.ts

@@ -1,4 +1,4 @@
-import type { Overrides, SSRInitialData } from '../../../core/dist-types/index.d.ts';
+import type { Overrides, SSRInitialData } from 'c15t';
 /**
  * Base options for SSR data fetching, shared across framework integrations.
  *

package/dist-types/types/consent-manager.d.ts

@@ -1,4 +1,4 @@
-import type { BaseConsentManagerOptions, UIOptions } from '../../../ui/dist-types/theme/index.d.ts';
+import type { BaseConsentManagerOptions, UIOptions } from '@c15t/ui/theme';
 import type { ReactNode } from 'react';
 /**
  * React-specific configuration options

package/dist-types/types/theme/style-keys.d.ts

@@ -1 +1 @@
-export type { AllThemeKeys } from '../../../../ui/dist-types/theme/index.d.ts';
+export type { AllThemeKeys } from '@c15t/ui/theme';

package/dist-types/types/theme/style-types.d.ts

@@ -1,7 +1,7 @@
-import type { ClassNameStyle as BaseClassNameStyle, Theme as BaseTheme } from '../../../../ui/dist-types/theme/index.d.ts';
+import type { ClassNameStyle as BaseClassNameStyle, Theme as BaseTheme } from '@c15t/ui/theme';
 import type { CSSProperties } from 'react';
 import type { AllThemeKeys } from './style-keys';
-export type { ColorTokens, ComponentSlots, CSSVariables, MotionTokens, RadiusTokens, ShadowTokens, SlotStyle, SpacingTokens, TypographyTokens, } from '../../../../ui/dist-types/theme/index.d.ts';
+export type { ColorTokens, ComponentSlots, CSSVariables, MotionTokens, RadiusTokens, ShadowTokens, SlotStyle, SpacingTokens, TypographyTokens, } from '@c15t/ui/theme';
 /**
  * Represents CSS properties with optional CSS variables.
  * @public

package/dist-types/utils/cn.d.ts

@@ -1,4 +1,4 @@
-import type { ClassValue } from '../../../ui/dist-types/utils/index.d.ts';
+import type { ClassValue } from '@c15t/ui/utils';
 export type { ClassValue };
 /**
  * Utilizes framework-agnostic `cn` from @c15t/ui.

package/dist-types/utils/theme-utils.d.ts

@@ -2,7 +2,7 @@
  * Utility functions for processing the v2 theme system.
  * Handles token-to-CSS variable conversion and dark mode overrides.
  */
-import type { ThemeCSSVariables } from '../../../ui/dist-types/theme/index.d.ts';
+import type { ThemeCSSVariables } from '@c15t/ui/theme';
 import type { Theme } from '../types/theme/style-types';
 /**
  * Default design tokens for the v2 theme system.

package/dist-types/version.d.ts

@@ -1 +1 @@
-export declare const version = "2.0.0-rc.6";
+export declare const version = "2.0.0-rc.8";

package/docs/building-headless-components.md

@@ -2,15 +2,27 @@
 title: Building Headless Components
 description: Build policy-aware custom consent components in React using the headless hooks and policy-pack tooling.
 ---
-Building headless components is easier now because c15t exposes policy-aware primitives instead of forcing you to reconstruct banner rules by hand.
+Building custom consent UI is easier now because c15t exposes multiple layers of policy-aware primitives instead of forcing you to reconstruct banner rules by hand.
 
-The headless stack is:
+The layering is:
+
+* stock component props for the shortest path
+* `ConsentBanner.PolicyActions` and `ConsentWidget.PolicyActions` for custom structure with policy-aware actions
+* `useHeadlessConsentUI()` for fully manual action rendering and non-standard controls
+
+> ⚠️ **Warning:**
+> Headless is the last step in the customization ladder. Use this guide only when pre-built components, tokens, slots, compound components, and noStyle are no longer sufficient.
+
+The headless stack underneath that is:
 
 * `useHeadlessConsentUI()` for policy-aware banner/dialog actions, ordering, layout, and primary actions hints
+* `@c15t/ui/utils` for the pure policy-action helpers that framework packages build on
 * `useConsentManager()` for runtime state, categories, selected consent state, and policy metadata
 * `useTranslations()` for the resolved copy
 * `offlinePolicy.policyPacks` for offline previews that behave like backend policy resolution
 
+The split is intentional: `@c15t/ui` owns pure policy-action resolution, while the framework hooks own visibility, consent mutations, and reactive state.
+
 > ℹ️ **Info:**
 > This guide is about building your own components while still respecting resolved policy-pack behavior. For the general headless overview, see Headless Mode.
 
@@ -30,6 +42,11 @@ The main win is that your custom UI can stay aligned with policy packs without d
 
 That means your component mostly focuses on markup and design-system concerns instead of re-implementing policy interpretation.
 
+For most compound-component layouts, start with `ConsentBanner.PolicyActions` or `ConsentWidget.PolicyActions`. They render stock c15t buttons and translations by default, and `renderAction` is only needed when you want to override the action mapping. Reach for manual `actionGroups` mapping when you need action rendering that no longer fits the stock button compounds.
+
+> ℹ️ **Info:**
+> For custom layouts built from c15t compound components, prefer ConsentBanner.PolicyActions and ConsentWidget.PolicyActions. The examples below intentionally use manual actionGroups mapping to show the fully headless escape hatch.
+
 ## Provider Setup for Local Policy Testing
 
 ```tsx
@@ -165,25 +182,29 @@ export function CustomConsentDialog() {
         ))}
       </div>
 
-      <div className="mt-4 flex gap-2">
-        {dialog.orderedActions.map((action) => (
-          <button
-            key={action}
-            type="button"
-            onClick={() => {
-              if (action === 'customize') {
-                void saveCustomPreferences();
-                return;
-              }
-              void performDialogAction(action);
-            }}
-          >
-            {action === 'accept'
-              ? translations.common.acceptAll
-              : action === 'reject'
-                ? translations.common.rejectAll
-                : translations.common.save}
-          </button>
+      <div className="mt-4 space-y-2">
+        {dialog.actionGroups.map((group, index) => (
+          <div key={`${group.join('-')}-${index}`} className="flex gap-2">
+            {group.map((action) => (
+              <button
+                key={action}
+                type="button"
+                onClick={() => {
+                  if (action === 'customize') {
+                    void saveCustomPreferences();
+                    return;
+                  }
+                  void performDialogAction(action);
+                }}
+              >
+                {action === 'accept'
+                  ? translations.common.acceptAll
+                  : action === 'reject'
+                    ? translations.common.rejectAll
+                    : translations.common.save}
+              </button>
+            ))}
+          </div>
         ))}
       </div>
     </section>
@@ -196,7 +217,7 @@ export function CustomConsentDialog() {
 When you build custom banner or dialog components, make sure they use:
 
 * `activeUI` or `banner.isVisible` / `dialog.isVisible` for visibility
-* `allowedActions`, `orderedActions`, or `actionGroups` instead of hard-coding buttons
+* `allowedActions`, `actionGroups`, and `primaryActions` instead of hard-coding buttons
 * `primaryActions` for visual emphasis
 * `consentCategories` when deciding which category toggles to render
 * `policyDecision` when you want to debug why a specific UI state was chosen

package/docs/callbacks.md

@@ -2,7 +2,12 @@
 title: Callbacks
 description: React to consent lifecycle events - initialization, consent changes, errors, and revocation reloads.
 ---
-Callbacks let you run custom code at key points in the consent lifecycle. Define them in the provider's `callbacks` option, or register them dynamically via `useConsentManager()`.
+Callbacks let you run custom code at key points in the consent lifecycle. Define them in the provider or runtime `callbacks` option, or register them dynamically after initialization.
+
+For analytics SDKs and other change-only integrations, prefer `subscribeToConsentChanges()` or `onConsentChanged`. Use `onConsentSet` when you want the broader lifecycle signal, including initialization, automatic defaults, and replay-aware registration.
+
+> ℹ️ **Info:**
+> subscribeToConsentChanges() is the recommended API for analytics SDKs and consent-mode integrations. It only emits future saves that actually changed persisted preferences.
 
 ## Configuration
 
@@ -23,8 +28,10 @@ export function ConsentManager({ children }: { children: ReactNode }) {
             console.log('Language:', translations.language);
           },
           onConsentSet: ({ preferences }) => {
-            // Fire analytics event
-            analytics.track('consent_updated', { preferences });
+            console.log('Consent lifecycle event:', preferences);
+          },
+          onConsentChanged: ({ allowedCategories, deniedCategories }) => {
+            analytics.syncConsent({ allowedCategories, deniedCategories });
           },
           onError: ({ error }) => {
             errorReporter.captureMessage(error);
@@ -42,6 +49,18 @@ export function ConsentManager({ children }: { children: ReactNode }) {
 }
 ```
 
+## Choose the Right Surface
+
+|Surface|Replays when registered late?|Fires on init / hydration / auto-grants?|Best for|
+|--|--|--|--|
+|`onBannerFetched`|Yes, via `setCallback('onBannerFetched', ...)` after init|Yes|Logging resolved policy, location, and translations|
+|`onConsentSet`|Yes, via `setCallback('onConsentSet', ...)`|Yes|Broad lifecycle hooks, debugging, and integrations that want the latest full state regardless of how it was reached|
+|`onConsentChanged`|No|No|Declarative change-only integrations|
+|`subscribeToConsentChanges()`|No|No|Canonical change-only subscriptions after mount|
+
+> ℹ️ **Info:**
+> Script.onConsentChange is a script-scoped lifecycle hook. It is not the global consent change API for analytics SDKs or other app-wide integrations.
+
 ## Available Callbacks
 
 ### `onBannerFetched`
@@ -58,14 +77,34 @@ onBannerFetched: ({ jurisdiction, location, translations }) => {
 
 ### `onConsentSet`
 
-Called whenever consent preferences are saved - whether by user action (`saveConsents()`), automatic defaults, or on initialization when no jurisdiction is detected.
+Called whenever c15t broadly settles consent state: store initialization, automatic defaults during init, explicit saves, and replay via `setCallback('onConsentSet', ...)`.
 
 ```tsx
 onConsentSet: ({ preferences }) => {
   // preferences: { necessary: true, measurement: true, marketing: false, ... }
-  if (preferences.measurement) {
-    loadAnalytics();
-  }
+  console.log('Latest consent state:', preferences);
+}
+```
+
+### `onConsentChanged`
+
+Called only after an explicit `saveConsents()` or `setConsent()` that actually changes the saved consent state. It never fires on store creation, hydration, automatic grants, unchanged saves, or `setCallback('onConsentChanged', ...)`.
+
+```tsx
+onConsentChanged: ({
+  preferences,
+  previousPreferences,
+  allowedCategories,
+  deniedCategories,
+  previousAllowedCategories,
+  previousDeniedCategories,
+}) => {
+  analytics.syncConsent({
+    allowedCategories,
+    deniedCategories,
+    previousAllowedCategories,
+    previousDeniedCategories,
+  });
 }
 ```
 
@@ -91,7 +130,28 @@ onBeforeConsentRevocationReload: ({ preferences }) => {
 }
 ```
 
-## Dynamic Registration
+## Change-Only Subscriptions
+
+Use `subscribeToConsentChanges()` when you want a stable listener for real preference changes after mount:
+
+```tsx
+import { useEffect } from 'react';
+import { useConsentManager } from '@c15t/react';
+
+function ConsentAnalytics() {
+  const { subscribeToConsentChanges } = useConsentManager();
+
+  useEffect(() => {
+    return subscribeToConsentChanges(({ allowedCategories, deniedCategories }) => {
+      analytics.syncConsent({ allowedCategories, deniedCategories });
+    });
+  }, [subscribeToConsentChanges]);
+
+  return null;
+}
+```
+
+## Runtime Callback Registration
 
 Register or update callbacks at runtime using `setCallback()`:
 
@@ -103,11 +163,16 @@ function ConsentAnalytics() {
   const { setCallback } = useConsentManager();
 
   useEffect(() => {
+    setCallback('onBannerFetched', ({ jurisdiction, location }) => {
+      console.log('Resolved init data:', { jurisdiction, location });
+    });
+
     setCallback('onConsentSet', ({ preferences }) => {
-      analytics.track('consent_changed', preferences);
+      console.log('Broad consent lifecycle event:', preferences);
     });
 
     return () => {
+      setCallback('onBannerFetched', undefined);
       setCallback('onConsentSet', undefined);
     };
   }, [setCallback]);
@@ -115,3 +180,5 @@ function ConsentAnalytics() {
   return null;
 }
 ```
+
+`setCallback('onConsentSet', ...)` immediately replays the current consent state. For change-only logic, prefer `subscribeToConsentChanges()` or `onConsentChanged`.

package/docs/components/consent-banner.md

@@ -1,6 +1,6 @@
 ---
 title: ConsentBanner
-description: A pre-built consent banner that appears when user consent is needed. Supports custom layout, button arrangement, and full compound component composition.
+description: A pre-built consent banner that appears when user consent is needed. Supports policy-aware layout, theming, and advanced composition when markup must change.
 ---
 `ConsentBanner` is a ready-to-use consent banner that appears automatically in **opt-in jurisdictions** (like GDPR) where explicit consent is required before tracking. In opt-out jurisdictions (like CCPA), the banner won't appear — users get an opt-out mechanism instead. It includes reject, accept, and customize buttons with configurable layout.
 
@@ -18,20 +18,6 @@ export function ConsentManager() {
 }
 ```
 
-## Customizing Content
-
-Override the default title, description, and button labels:
-
-```tsx
-<ConsentBanner
-  title="We value your privacy"
-  description="We use cookies to enhance your browsing experience and analyze site traffic."
-  acceptButtonText="Accept all"
-  rejectButtonText="Reject all"
-  customizeButtonText="Manage preferences"
-/>
-```
-
 ## Button Layout
 
 The `layout` prop controls button arrangement. Each item is either a button ID or an array of button IDs (which groups them together):
@@ -86,6 +72,37 @@ Use the provider `theme` prop to control how stock consent actions look:
 
 Policy packs control grouping, ordering, and direction. The theme controls button appearance.
 
+## Styling First
+
+> ℹ️ **Info:**
+> For pure theming, stay inside the pre-built banner. Start with layout props, theme.consentActions, design tokens, and theme.slots before reaching for compound components. See Styling Overview.
+
+The stock banner maps common visual changes to the theme system:
+
+* Card background -> `theme.colors.surface`
+* Footer background -> `theme.colors.surfaceHover`
+* Card, footer, and title tweaks -> `theme.slots.consentBannerCard`, `consentBannerFooter`, and `consentBannerTitle`
+
+```tsx
+<ConsentManagerProvider
+  options={{
+    theme: {
+      colors: {
+        surface: '#fffdf8',
+        surfaceHover: '#f6f3ee',
+      },
+      slots: {
+        consentBannerCard: 'rounded-[28px] shadow-xl',
+        consentBannerFooter: 'border-t border-black/10 px-6',
+        consentBannerTitle: 'tracking-tight',
+      },
+    },
+  }}
+>
+  <ConsentBanner />
+</ConsentManagerProvider>
+```
+
 ### Primary Button
 
 Highlight specific button(s) as the primary action:
@@ -116,9 +133,40 @@ Control which legal links appear in the banner description:
 > ℹ️ **Info:**
 > Legal link URLs are configured in the ConsentManagerProvider options via the legalLinks prop, not on the banner itself.
 
-## Compound Components
+## Customizing Copy
 
-Build fully custom banner layouts using sub-components:
+Prefer provider `i18n` when you want to rename the stock banner content:
+
+```tsx
+<ConsentManagerProvider
+  options={{
+    i18n: {
+      locale: 'en',
+      messages: {
+        en: {
+          cookieBanner: {
+            title: 'We value your privacy',
+            description: 'We use cookies to improve the site and measure performance.',
+          },
+          common: {
+            acceptAll: 'Accept all',
+            rejectAll: 'Reject all',
+            customize: 'Manage preferences',
+          },
+        },
+      },
+    },
+  }}
+>
+  <ConsentBanner />
+</ConsentManagerProvider>
+```
+
+Direct text props such as `title`, `description`, and `acceptButtonText` are still supported for one-off overrides, but `i18n` is the preferred path for copy changes.
+
+## Advanced: Compound Components
+
+Use compound components only when the stock banner structure is no longer enough and you need to rearrange existing c15t primitives while keeping policy-driven action grouping and emphasis:
 
 ```tsx
 <ConsentBanner.Root>
@@ -128,13 +176,7 @@ Build fully custom banner layouts using sub-components:
       <ConsentBanner.Title />
       <ConsentBanner.Description />
     </ConsentBanner.Header>
-    <ConsentBanner.Footer>
-      <ConsentBanner.FooterSubGroup>
-        <ConsentBanner.RejectButton />
-        <ConsentBanner.AcceptButton />
-      </ConsentBanner.FooterSubGroup>
-      <ConsentBanner.CustomizeButton />
-    </ConsentBanner.Footer>
+    <ConsentBanner.PolicyActions />
   </ConsentBanner.Card>
 </ConsentBanner.Root>
 ```
@@ -144,6 +186,7 @@ Build fully custom banner layouts using sub-components:
 * `ConsentBanner.Header` — Contains title and description
 * `ConsentBanner.Title` — Heading, defaults to translation `consentBanner.title`
 * `ConsentBanner.Description` — Description text, supports `legalLinks` prop
+* `ConsentBanner.PolicyActions` — Renders policy-aware grouped actions inside the banner footer
 * `ConsentBanner.Footer` — Action buttons container
 * `ConsentBanner.FooterSubGroup` — Groups related buttons together
 * `ConsentBanner.RejectButton` — Rejects all consent
@@ -151,6 +194,86 @@ Build fully custom banner layouts using sub-components:
 * `ConsentBanner.AcceptButton` — Accepts all consent
 * `ConsentBanner.Overlay` — Optional backdrop overlay
 
+For a fixed layout that intentionally ignores policy grouping, render the footer manually:
+
+```tsx
+<ConsentBanner.Root>
+  <ConsentBanner.Card>
+    <ConsentBanner.Header>
+      <ConsentBanner.Title />
+      <ConsentBanner.Description />
+    </ConsentBanner.Header>
+    <ConsentBanner.Footer>
+      <ConsentBanner.FooterSubGroup>
+        <ConsentBanner.RejectButton />
+        <ConsentBanner.AcceptButton />
+      </ConsentBanner.FooterSubGroup>
+      <ConsentBanner.CustomizeButton />
+    </ConsentBanner.Footer>
+  </ConsentBanner.Card>
+</ConsentBanner.Root>
+```
+
+## Using `renderAction` with c15t Defaults
+
+`ConsentBanner.PolicyActions` renders stock c15t buttons and translations by default.
+
+```tsx
+<ConsentBanner.PolicyActions />
+```
+
+`renderAction` is optional. When you want custom mapping but still want the built-in c15t button behavior and copy, return the stock button compounds:
+
+```tsx
+<ConsentBanner.PolicyActions
+renderAction={(action, props) => {
+  const { key, ...buttonProps } = props
+
+  switch (action) {
+    case 'accept':
+        return <ConsentBanner.AcceptButton key={key} {...buttonProps} />
+    case 'reject':
+        return <ConsentBanner.RejectButton key={key} {...buttonProps} />
+    case 'customize':
+        return <ConsentBanner.CustomizeButton key={key} {...buttonProps} />
+  }
+}}
+/>
+```
+
+Use `useTranslations()` only when you are replacing the button markup entirely:
+
+```tsx
+import { ConsentBanner, useTranslations } from '@c15t/react';
+
+export function CustomBannerActions() {
+  const { common } = useTranslations();
+
+  return (
+    <ConsentBanner.PolicyActions
+      renderAction={(action, props) => (
+        <button
+          key={props.key}
+          type="button"
+          className={props.isPrimary ? 'btn-primary' : 'btn-secondary'}
+          style={props.style}
+        >
+          {action === 'accept'
+            ? common.acceptAll
+            : action === 'reject'
+              ? common.rejectAll
+              : common.customize}
+        </button>
+      )}
+    />
+  );
+}
+```
+
+For maximum control, use `useHeadlessConsentUI()` and render `banner.actionGroups` manually.
+
+If you only need styling changes, stay with tokens and slots instead of rebuilding the banner layout.
+
 ## Props
 
 ### ConsentBannerProps
@@ -167,6 +290,7 @@ Build fully custom banner layouts using sub-components:
 |trapFocus|boolean \|undefined|When true, the consent banner will trap focus|true|Optional|
 |disableAnimation|boolean \|undefined|When true, disables the entrance/exit animations|false|Optional|
 |legalLinks|(keyof LegalLinksTranslations)\[] \|null \|undefined|Controls which legal links to display. Options: \`undefined\` (default): Shows all available legal links; \`null\`: Explicitly hides all legal links; Array of keys: Shows only the specified legal links|-|Optional|
+|hideBranding|boolean \|undefined|When true, hides the branding tag on the banner.|false|Optional|
 |layout|ConsentBannerLayout \|undefined|Defines the layout of buttons in the footer. Allows reordering and grouping of buttons.|-|Optional|
 |direction|PolicyUiActionDirection \|undefined|Defines how footer button groups flow.|-|Optional|
 |primaryButton|ConsentBannerButton \|undefined|Specifies which button(s) should be highlighted as the primary action.|-|Optional|

package/docs/components/consent-dialog.md

@@ -81,9 +81,36 @@ Hide the c15t branding in the dialog footer:
 <ConsentDialog hideBranding />
 ```
 
-## Compound Components
+## Styling First
 
-Build fully custom dialog layouts using sub-components:
+> ℹ️ **Info:**
+> If you are only changing visuals, stay with the stock dialog and use the theme system first. Start with tokens and slots such as consentDialogCard, consentDialogHeader, and consentDialogFooter. See Styling Overview.
+
+```tsx
+<ConsentManagerProvider
+  options={{
+    theme: {
+      colors: {
+        surface: '#fffdf8',
+        surfaceHover: '#f6f3ee',
+      },
+      slots: {
+        consentDialogCard: 'rounded-[32px] shadow-xl',
+        consentDialogHeader: 'gap-3',
+        consentDialogFooter: 'border-t border-black/10 px-6',
+      },
+    },
+  }}
+>
+  <ConsentDialog />
+</ConsentManagerProvider>
+```
+
+Dialog copy should be changed through `ConsentManagerProvider.options.i18n`, not by rebuilding the dialog structure.
+
+## Advanced: Compound Components
+
+Use compound components only when you need custom dialog markup while still keeping c15t primitives and policy-aware footer actions:
 
 ```tsx
 <ConsentDialog.Root>
@@ -94,7 +121,12 @@ Build fully custom dialog layouts using sub-components:
       <ConsentDialog.HeaderDescription />
     </ConsentDialog.Header>
     <ConsentDialog.Content>
-      <ConsentWidget />
+      <ConsentWidget.Root>
+        <ConsentWidget.Accordion type="single">
+          <ConsentWidget.AccordionItems />
+        </ConsentWidget.Accordion>
+        <ConsentWidget.PolicyActions />
+      </ConsentWidget.Root>
     </ConsentDialog.Content>
     <ConsentDialog.Footer />
   </ConsentDialog.Card>
@@ -109,6 +141,7 @@ Build fully custom dialog layouts using sub-components:
 * `ConsentDialog.Content` — Main content area (typically contains `ConsentWidget`)
 * `ConsentDialog.Footer` — Footer with optional branding (`hideBranding` prop)
 * `ConsentDialog.Overlay` — Backdrop overlay
+* `ConsentWidget.PolicyActions` — Renders policy-aware grouped dialog actions
 
 For a quick pre-composed layout, use the shorthand card:
 
@@ -118,6 +151,12 @@ For a quick pre-composed layout, use the shorthand card:
 </ConsentDialog.Root>
 ```
 
+`ConsentWidget.PolicyActions` uses stock c15t widget buttons and translations by default. Pass `renderAction` only when you need to customize the action mapping, and return stock widget button compounds if you want to preserve built-in behavior and copy.
+
+For fully manual control over dialog action rendering, use `useHeadlessConsentUI()` and map `dialog.actionGroups` yourself.
+
+If the stock dialog structure still works, prefer tokens, slots, and provider configuration instead.
+
 ## Props
 
 ### ConsentDialogProps