@c15t/nextjs 2.2.0 → 3.0.0-alpha.0

package/docs/shared/react/components/consent-banner.md

@@ -1,242 +0,0 @@
----
-title: Consent Banner
-description: Reference page for consent banner.
-group: reference
----
-`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.
-
-## 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):
-
-```tsx
-{/* Default: reject and accept grouped, customize separate */}
-<ConsentBanner layout={[['reject', 'accept'], 'customize']} />
-
-{/* All buttons in one group */}
-<ConsentBanner layout={[['reject', 'customize', 'accept']]} />
-
-{/* Accept first, then reject and customize grouped */}
-<ConsentBanner layout={['accept', ['reject', 'customize']]} />
-```
-
-To stack groups vertically, pair the same grouped layout with `direction="column"`:
-
-```tsx
-<ConsentBanner
-  layout={['customize', ['reject', 'accept']]}
-  direction="column"
-/>
-```
-
-## Policy-Driven UI Profile
-
-When using backend runtime policies, `policy.ui.uiProfile` can control banner action presentation:
-
-* `compact` — default desktop sizing
-* `balanced` — auto-fills compact and grouped layouts with moderate emphasis
-* `strict` — always fills action controls for explicit, high-clarity layouts
-
-## Theme-Level Button Styling
-
-Use the provider `theme` prop to control how stock consent actions look:
-
-```tsx
-<ConsentManagerProvider
-  options={{
-    theme: {
-      consentActions: {
-        default: { mode: 'stroke' },
-        accept: { variant: 'primary', mode: 'stroke' },
-        customize: { variant: 'neutral', mode: 'ghost' },
-      },
-    },
-  }}
->
-  <ConsentBanner />
-</ConsentManagerProvider>
-```
-
-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:
-
-```tsx
-{/* Single primary */}
-<ConsentBanner primaryButton="accept" />
-
-{/* Multiple primaries */}
-<ConsentBanner primaryButton={['accept', 'customize']} />
-```
-
-## Legal Links
-
-Control which legal links appear in the banner description:
-
-```tsx
-{/* Show all configured links (default) */}
-<ConsentBanner legalLinks={undefined} />
-
-{/* Show no links */}
-<ConsentBanner legalLinks={null} />
-
-{/* Show specific links */}
-<ConsentBanner legalLinks={['privacyPolicy', 'cookiePolicy']} />
-```
-
-> ℹ️ **Info:**
-> Legal link URLs are configured in the ConsentManagerProvider options via the legalLinks prop, not on the banner itself.
-
-## Customizing Copy
-
-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>
-  <ConsentBanner.Overlay />
-  <ConsentBanner.Card>
-    <ConsentBanner.Header>
-      <ConsentBanner.Title />
-      <ConsentBanner.Description />
-    </ConsentBanner.Header>
-    <ConsentBanner.PolicyActions />
-  </ConsentBanner.Card>
-</ConsentBanner.Root>
-```
-
-* `ConsentBanner.Root` — Outermost container, provides theme context
-* `ConsentBanner.Card` — Main content card with optional focus trapping
-* `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
-* `ConsentBanner.CustomizeButton` — Opens the consent dialog
-* `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} />
-  }
-}}
-/>
-```
-
-`renderAction` is still meant for stock button compounds. If you want completely custom button elements and click handling, use `useHeadlessConsentUI()` and render `banner.actionGroups` manually instead of `ConsentBanner.PolicyActions`.
-
-If you only need styling changes, stay with tokens and slots instead of rebuilding the banner layout.
-
-## Props
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ConsentBannerProps\`|
-|Source Path|\`./packages/react/src/components/consent-banner/consent-banner.tsx\`|
-
-\*ExtractedTypeTable: Could not extract "ConsentBannerProps" from "./packages/react/src/components/consent-banner/consent-banner.tsx" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*

package/docs/shared/react/components/consent-dialog-link.md

@@ -1,45 +0,0 @@
----
-title: Consent Dialog Link
-description: Reference page for consent dialog link.
-group: reference
----
-`ConsentDialogLink` is an inline trigger for opening the consent dialog from places like site footers, legal pages, or account settings. It is unstyled by default, so it inherits your app's typography and link/button styles.
-
-## Footer Link (unstyled by default)
-
-```tsx
-<footer>
-  <ConsentDialogLink>
-    Your privacy settings
-  </ConsentDialogLink>
-</footer>
-```
-
-## Render as an Anchor
-
-Use `asChild` to keep semantic anchor markup while still opening the dialog:
-
-```tsx
-<ConsentDialogLink asChild>
-  <a href="#privacy-settings">Manage Preferences</a>
-</ConsentDialogLink>
-```
-
-## Optional Styling Control
-
-The component defaults to `noStyle={true}`. Set it to `false` if you want c15t button styles:
-
-```tsx
-<ConsentDialogLink noStyle={false}>
-  Privacy Settings
-</ConsentDialogLink>
-```
-
-## Props
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ConsentDialogLinkProps\`|
-|Source Path|\`./packages/react/src/components/consent-preferences-link/consent-preferences-link.tsx\`|
-
-\*ExtractedTypeTable: Could not extract "ConsentDialogLinkProps" from "./packages/react/src/components/consent-preferences-link/consent-preferences-link.tsx" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*

package/docs/shared/react/components/consent-dialog-trigger.md

@@ -1,185 +0,0 @@
----
-title: Consent Dialog Trigger
-description: Reference page for consent dialog trigger.
-group: reference
----
-`ConsentDialogTrigger` is a floating button that opens the consent dialog when clicked. Users can drag it to any corner of the screen, and the position persists across sessions. Use it to give users a persistent way to manage their privacy settings.
-
-## Icon Options
-
-```tsx
-{/* Built-in icons */}
-<ConsentDialogTrigger icon="branding" />    {/* c15t logo (default) */}
-<ConsentDialogTrigger icon="fingerprint" /> {/* Privacy icon */}
-<ConsentDialogTrigger icon="settings" />    {/* Gear icon */}
-
-{/* Custom icon */}
-<ConsentDialogTrigger icon={<MyCustomIcon />} />
-```
-
-## Configurable Toolbar
-
-Use the separate `ConsentDialogTriggerToolbar` when you want to place app-owned controls beside the privacy trigger. It always renders exactly one built-in action that opens consent preferences, so `actions` only contains controls your app owns.
-
-```tsx
-<ConsentDialogTriggerToolbar
-  ariaLabel="Site controls"
-  actions={[
-    {
-      id: 'theme',
-      label: isDark ? 'Switch to light theme' : 'Switch to dark theme',
-      icon: isDark ? <SunIcon /> : <MoonIcon />,
-      pressed: isDark,
-      onSelect: toggleColorScheme,
-    },
-    {
-      id: 'support',
-      label: 'Open support chat',
-      icon: <ChatIcon />,
-      onSelect: openSupportChat,
-    },
-  ]}
-  preferences={{
-    icon: 'fingerprint',
-    label: 'Manage privacy settings',
-  }}
-/>
-```
-
-Each custom action requires a stable `id`, accessible `label`, `icon`, and `onSelect` callback. Use `pressed` for toggle actions and `disabled` for unavailable actions. Your app remains responsible for state, integrations, and changing the icon or label. The preferences action automatically moves to the edge nearest the toolbar's snapped corner while custom actions keep their configured order.
-
-Toolbars are horizontal by default. Set `orientation="vertical"` to stack the actions and enable Up/Down arrow-key navigation:
-
-```tsx
-<ConsentDialogTriggerToolbar
-  orientation="vertical"
-  actions={toolbarActions}
-/>
-```
-
-### Toolbar Styling
-
-The toolbar follows the standard styling precedence: internal CSS module styles, provider theme slots, then direct component overrides. Use `className` and `style` on the toolbar, or on an individual action, and use `noStyle` for a fully custom implementation.
-
-```tsx
-<ConsentManagerProvider
-  options={{
-    theme: {
-      slots: {
-        consentDialogTriggerToolbar: 'my-toolbar',
-        consentDialogTriggerToolbarItem: 'my-toolbar-item',
-        consentDialogTriggerToolbarIcon: 'my-toolbar-icon',
-      },
-    },
-  }}
->
-  <ConsentDialogTriggerToolbar
-    className="fixed-toolbar"
-    style={{ '--cdtt-offset': '24px' }}
-    actions={[
-      {
-        id: 'support',
-        label: 'Open support chat',
-        icon: <ChatIcon />,
-        onSelect: openSupportChat,
-        className: 'support-action',
-      },
-    ]}
-  />
-</ConsentManagerProvider>
-```
-
-Available toolbar theme slots are `consentDialogTriggerToolbar`, `consentDialogTriggerToolbarItem`, and `consentDialogTriggerToolbarIcon`.
-
-With `noStyle`, use `data-corner`, `data-dragging`, and `data-snapping` on the toolbar to style its current position and interaction state.
-
-## Visibility
-
-Control when the trigger is visible:
-
-```tsx
-{/* Always visible (default) */}
-<ConsentDialogTrigger showWhen="always" />
-
-{/* Only after user has made a consent choice */}
-<ConsentDialogTrigger showWhen="after-consent" />
-
-{/* Hidden (control visibility programmatically) */}
-<ConsentDialogTrigger showWhen="never" />
-```
-
-## Position
-
-Set the default corner and control persistence:
-
-```tsx
-<ConsentDialogTrigger
-  defaultPosition="bottom-left"
-  persistPosition={true} // Remembers user's drag position
-  onPositionChange={(position) => console.log('Moved to:', position)}
-/>
-```
-
-## Size
-
-```tsx
-<ConsentDialogTrigger size="sm" /> {/* Small */}
-<ConsentDialogTrigger size="md" /> {/* Medium (default) */}
-<ConsentDialogTrigger size="lg" /> {/* Large */}
-```
-
-## Compound Components
-
-Build fully custom trigger layouts using sub-components:
-
-```tsx
-<ConsentDialogTrigger.Root defaultPosition="bottom-right">
-  <ConsentDialogTrigger.Button size="md">
-    <ConsentDialogTrigger.Icon icon="settings" />
-    <ConsentDialogTrigger.Text>Privacy</ConsentDialogTrigger.Text>
-  </ConsentDialogTrigger.Button>
-</ConsentDialogTrigger.Root>
-```
-
-* `ConsentDialogTrigger.Root` — Portal wrapper with drag handling and position persistence
-* `ConsentDialogTrigger.Button` — Draggable button element with size variants
-* `ConsentDialogTrigger.Icon` — Icon display (branding, fingerprint, settings, or custom)
-* `ConsentDialogTrigger.Text` — Optional text label
-
-## Props
-
-### ConsentDialogTrigger
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ConsentDialogTriggerProps\`|
-|Source Path|\`./packages/react/src/components/consent-dialog-trigger/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "ConsentDialogTriggerProps" from "./packages/react/src/components/consent-dialog-trigger/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-### ConsentDialogTriggerToolbar
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ConsentDialogTriggerToolbarProps\`|
-|Source Path|\`./packages/react/src/components/consent-dialog-trigger/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "ConsentDialogTriggerToolbarProps" from "./packages/react/src/components/consent-dialog-trigger/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-### Toolbar Actions
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ConsentDialogTriggerToolbarAction\`|
-|Source Path|\`./packages/react/src/components/consent-dialog-trigger/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "ConsentDialogTriggerToolbarAction" from "./packages/react/src/components/consent-dialog-trigger/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-### Preferences Action
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ConsentDialogTriggerToolbarPreferences\`|
-|Source Path|\`./packages/react/src/components/consent-dialog-trigger/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "ConsentDialogTriggerToolbarPreferences" from "./packages/react/src/components/consent-dialog-trigger/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*

package/docs/shared/react/components/consent-dialog.md

@@ -1,119 +0,0 @@
----
-title: Consent Dialog
-description: Reference page for consent dialog.
-group: reference
----
-`ConsentDialog` is a modal that shows toggles for each consent category. In **opt-in jurisdictions**, it typically opens when users click "Customize" on `ConsentBanner`. It can also be controlled programmatically for use on settings pages regardless of jurisdiction.
-
-## Floating Trigger
-
-Add a floating button that lets users re-open the dialog after dismissing the banner:
-
-```tsx
-{/* Default trigger */}
-<ConsentDialog showTrigger />
-
-{/* Custom trigger */}
-<ConsentDialog
-  showTrigger={{
-    icon: 'settings',
-    defaultPosition: 'bottom-left',
-    showWhen: 'after-consent',
-    size: 'sm',
-  }}
-/>
-```
-
-## Branding
-
-Hide the c15t branding tag:
-
-```tsx
-<ConsentDialog hideBranding />
-```
-
-## Styling First
-
-> ℹ️ **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, consentWidgetFooter, and consentDialogTag. See Styling Overview.
-
-```tsx
-<ConsentManagerProvider
-  options={{
-    theme: {
-      colors: {
-        surface: '#fffdf8',
-        surfaceHover: '#f6f3ee',
-      },
-      slots: {
-        consentDialogCard: 'rounded-[32px] shadow-xl',
-        consentDialogHeader: 'gap-3',
-        consentWidgetFooter: 'gap-3 pt-6',
-        consentDialogTag: 'shadow-none',
-      },
-    },
-  }}
->
-  <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>
-  <ConsentDialog.Overlay />
-  <ConsentDialog.Card>
-    <ConsentDialog.Header>
-      <ConsentDialog.HeaderTitle />
-      <ConsentDialog.HeaderDescription />
-    </ConsentDialog.Header>
-    <ConsentDialog.Content>
-      <ConsentWidget.Root>
-        <ConsentWidget.Accordion type="single">
-          <ConsentWidget.AccordionItems />
-        </ConsentWidget.Accordion>
-        <ConsentWidget.PolicyActions />
-      </ConsentWidget.Root>
-    </ConsentDialog.Content>
-    <ConsentDialog.Footer />
-  </ConsentDialog.Card>
-</ConsentDialog.Root>
-```
-
-* `ConsentDialog.Root` — Portal container with focus trap, scroll lock, and animation
-* `ConsentDialog.Card` — Main dialog card
-* `ConsentDialog.Header` — Contains title and description
-* `ConsentDialog.HeaderTitle` — Dialog title
-* `ConsentDialog.HeaderDescription` — Description with optional `legalLinks`
-* `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:
-
-```tsx
-<ConsentDialog.Root>
-  <ConsentDialog.ConsentCustomizationCard />
-</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
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ConsentDialogProps\`|
-|Source Path|\`./packages/react/src/components/consent-dialog/consent-dialog.tsx\`|
-
-\*ExtractedTypeTable: Could not extract "ConsentDialogProps" from "./packages/react/src/components/consent-dialog/consent-dialog.tsx" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*