@delmaredigital/payload-puck 0.4.0 → 0.6.1

package/README.md

@@ -8,6 +8,7 @@ A PayloadCMS plugin for integrating [Puck](https://puckeditor.com) visual page b
 
 - [Installation](#installation)
 - [Quick Start](#quick-start)
+  - [Adding to Existing Projects](#adding-to-existing-projects)
 - [Styling Setup](#styling-setup)
 - [Core Concepts](#core-concepts)
 - [Components](#components)
@@ -17,6 +18,7 @@ A PayloadCMS plugin for integrating [Puck](https://puckeditor.com) visual page b
 - [Layouts](#layouts)
 - [Page-Tree Integration](#page-tree-integration)
 - [Hybrid Integration](#hybrid-integration)
+- [AI Integration](#ai-integration)
 - [Advanced Configuration](#advanced-configuration)
 - [License](#license)
 
@@ -28,17 +30,19 @@ A PayloadCMS plugin for integrating [Puck](https://puckeditor.com) visual page b
 
 | Dependency | Version | Purpose |
 |------------|---------|---------|
-| `@measured/puck` | >= 0.20.0 | Visual editor core |
-| `payload` | >= 3.0.0 | CMS backend |
-| `@payloadcms/next` | >= 3.0.0 | Payload Next.js integration |
-| `next` | >= 14.0.0 | React framework |
-| `react` | >= 18.0.0 | UI library |
+| `@puckeditor/core` | >= 0.21.0 | Visual editor core |
+| `payload` | >= 3.69.0 | CMS backend |
+| `@payloadcms/next` | >= 3.69.0 | Payload Next.js integration |
+| `next` | >= 15.4.8 | React framework |
+| `react` | >= 19.2.1 | UI library |
 | `@tailwindcss/typography` | >= 0.5.0 | RichText component styling |
 
+> **Note:** Puck 0.21+ moved from `@measured/puck` to `@puckeditor/core`. This plugin requires the new package scope.
+
 ### Install
 
 ```bash
-pnpm add @delmaredigital/payload-puck @measured/puck
+pnpm add @delmaredigital/payload-puck @puckeditor/core
 ```
 
 ---
@@ -50,7 +54,7 @@ The plugin integrates directly into Payload's admin UI with minimal configuratio
 ### Step 1: Add the Plugin
 
 ```typescript
-// payload.config.ts
+// src/payload.config.ts
 import { buildConfig } from 'payload'
 import { createPuckPlugin } from '@delmaredigital/payload-puck/plugin'
 
@@ -96,6 +100,34 @@ export default function RootLayout({ children }: { children: React.ReactNode })
 
 > **Note:** For custom editor UIs (outside Payload admin), you can also pass the config directly to `PuckEditor` instead of using the context provider.
 
+**Alternative: Payload Admin Provider (vanilla starter pattern)**
+
+If you're using the vanilla Payload starter structure, you can register the provider via the admin config instead:
+
+```typescript
+// src/payload.config.ts
+export default buildConfig({
+  admin: {
+    components: {
+      providers: ['@/components/admin/PuckProvider'],
+    },
+  },
+  // ...
+})
+```
+
+```typescript
+// src/components/admin/PuckProvider.tsx
+'use client'
+
+import { PuckConfigProvider } from '@delmaredigital/payload-puck/client'
+import { editorConfig } from '@delmaredigital/payload-puck/config/editor'
+
+export default function PuckProvider({ children }: { children: React.ReactNode }) {
+  return <PuckConfigProvider config={editorConfig}>{children}</PuckConfigProvider>
+}
+```
+
 ### Step 3: Create a Frontend Route
 
 The plugin can't auto-create frontend routes (Next.js App Router is file-based), but here's copy-paste ready code:
@@ -112,16 +144,23 @@ import { notFound } from 'next/navigation'
 import type { Metadata } from 'next'
 
 // Fetch page by slug (or homepage if no slug)
+// Only returns published pages - unpublished pages will 404
 async function getPage(slug?: string[]) {
   const payload = await getPayload({ config })
   const slugPath = slug?.join('/') || ''
 
   // Try to find by slug, or find homepage
+  // Filter for published pages only (_status: 'published')
   const { docs } = await payload.find({
     collection: 'pages',
-    where: slugPath
-      ? { slug: { equals: slugPath } }
-      : { isHomepage: { equals: true } },
+    where: {
+      and: [
+        { _status: { equals: 'published' } },
+        slugPath
+          ? { slug: { equals: slugPath } }
+          : { isHomepage: { equals: true } },
+      ],
+    },
     limit: 1,
   })
 
@@ -171,6 +210,74 @@ export default async function Page({
 - The editor runs inside Payload's admin UI with full navigation
 - API endpoints are handled automatically via Payload's endpoint system
 
+### Adding to Existing Projects
+
+> **⚠️ Important:** If you're adding Puck to a project with existing frontend routes, you must update those routes to render Puck content.
+
+When adding Puck to an existing Payload project:
+
+1. ✅ Add the plugin to `payload.config.ts`
+2. ✅ Add `PuckConfigProvider` to your admin layout
+3. ⚠️ **Update your frontend page templates** to render `puckData`
+
+Without step 3, Puck pages will render blank because your existing routes only look for legacy block fields like `layout` or `hero`.
+
+**Option A: Hybrid Rendering (recommended for migration)**
+
+Use `HybridPageRenderer` to support both legacy blocks and Puck pages:
+
+```typescript
+import { HybridPageRenderer } from '@delmaredigital/payload-puck/render'
+import { baseConfig } from '@delmaredigital/payload-puck/config'
+import { LegacyBlockRenderer } from '@/components/LegacyBlockRenderer'
+
+export default async function Page({ params }) {
+  const page = await getPage(params.slug)
+
+  return (
+    <HybridPageRenderer
+      page={page}
+      config={baseConfig}
+      legacyRenderer={(blocks) => <LegacyBlockRenderer blocks={blocks} />}
+    />
+  )
+}
+```
+
+**Option B: Manual Detection**
+
+Add conditional logic to check `editorVersion`:
+
+```typescript
+// Check if page was created with Puck
+const isPuckPage = page.editorVersion === 'puck' && page.puckData?.content?.length > 0
+
+if (isPuckPage) {
+  return <PageRenderer config={baseConfig} data={page.puckData} />
+}
+
+// Fall back to legacy rendering
+return <LegacyBlockRenderer blocks={page.layout} />
+```
+
+**Option C: Custom Components**
+
+If you have custom Puck components (not just the built-in ones), create a client wrapper:
+
+```typescript
+// components/PuckPageRenderer.tsx
+'use client'
+
+import { Render } from '@puckeditor/core'
+import { myCustomConfig } from '@/puck/config'
+
+export function PuckPageRenderer({ data }) {
+  return <Render config={myCustomConfig} data={data} />
+}
+```
+
+Then use this wrapper in your page template instead of `PageRenderer`.
+
 ---
 
 ## Styling Setup
@@ -285,6 +392,11 @@ The editor uses Payload's native draft system. The plugin automatically enables
 }
 ```
 
+The editor header provides:
+- **Save** - Saves as draft without publishing
+- **Publish** - Publishes the page (sets `_status: 'published'`)
+- **Unpublish** - Reverts a published page to draft status (appears only when published)
+
 ---
 
 ## Components
@@ -306,7 +418,7 @@ The editor uses Payload's native draft system. The plugin automatically enables
 |-----------|-------------|
 | **Heading** | H1-H6 headings with size and alignment |
 | **Text** | Paragraph text with styling options |
-| **RichText** | TipTap-powered WYSIWYG editor |
+| **RichText** | Puck's native richtext editor with enhancements: font sizes, text colors with opacity, highlights, superscript/subscript, and inline editing on canvas |
 
 ### Media & Interactive
 
@@ -316,7 +428,20 @@ The editor uses Payload's native draft system. The plugin automatically enables
 | **Button** | Styled button/link with variants |
 | **Card** | Content card with optional image |
 | **Divider** | Horizontal rule with styles |
-| **Accordion** | Expandable content sections |
+| **Accordion** | Expandable content sections (first item opens by default) |
+
+### Semantic HTML Elements
+
+Layout components (Section, Flex, Container, Grid) support semantic HTML output for better SEO and accessibility:
+
+| Component | Available Elements |
+|-----------|-------------------|
+| **Section** | `section`, `article`, `aside`, `nav`, `header`, `footer`, `main`, `div` |
+| **Flex** | `div`, `nav`, `ul`, `ol`, `aside`, `section` |
+| **Container** | `div`, `article`, `aside`, `section` |
+| **Grid** | `div`, `ul`, `ol` |
+
+Select the appropriate HTML element in the component's sidebar to output semantic markup.
 
 ### Responsive Controls
 
@@ -324,6 +449,7 @@ Layout components support per-breakpoint customization:
 - **Dimensions** - Width, max-width, height constraints
 - **Padding/Margin** - Spacing per breakpoint
 - **Visibility** - Show/hide at specific breakpoints
+- **Viewport Preview** - Mobile, Tablet, Desktop, and Full Width options
 
 ---
 
@@ -336,13 +462,15 @@ All fields are imported from `@delmaredigital/payload-puck/fields`.
 | Field | Description |
 |-------|-------------|
 | **MediaField** | Payload media library integration |
-| **TiptapField** | Rich text editor with formatting |
+| **RichTextField** | Puck's native richtext with enhancements (colors, font sizes, highlights) |
 | **ColorPickerField** | Color picker with opacity and presets |
 | **BackgroundField** | Solid colors, gradients, images |
 | **PaddingField / MarginField** | Visual spacing editors |
 | **BorderField** | Border width, style, color, radius |
 | **DimensionsField** | Width/height with constraints |
-| **AlignmentField** | Text alignment options |
+| **AlignmentField** | Text alignment (left, center, right) |
+| **ContentAlignmentField** | Visual 3x3 grid selector for positioning (d-pad style) |
+| **SizeField** | Preset sizes (sm, default, lg) with custom mode |
 | **AnimationField** | Entrance animations |
 | **ResponsiveVisibilityField** | Show/hide per breakpoint |
 | **FolderPickerField** | Hierarchical folder selection (page-tree) |
@@ -375,9 +503,46 @@ import {
   dimensionsValueToCSS,
   animationValueToCSS,
   visibilityValueToCSS,
+  alignmentToFlexCSS,
+  alignmentToGridCSS,
+  sizeValueToCSS,
+  getSizeClasses,
 } from '@delmaredigital/payload-puck/fields'
 ```
 
+### ContentAlignmentField Example
+
+The ContentAlignmentField provides a visual 3x3 grid selector for content positioning:
+
+```typescript
+import {
+  createContentAlignmentField,
+  alignmentToFlexCSS,
+  alignmentToGridCSS,
+} from '@delmaredigital/payload-puck/fields'
+
+const BannerConfig = {
+  fields: {
+    contentPosition: createContentAlignmentField({ label: 'Content Position' }),
+  },
+  render: ({ contentPosition }) => (
+    <div style={{
+      display: 'flex',
+      minHeight: '400px',
+      ...alignmentToFlexCSS(contentPosition), // Converts to justify-content + align-items
+    }}>
+      <div>Positioned content</div>
+    </div>
+  ),
+}
+```
+
+Helper functions:
+- `alignmentToFlexCSS()` - For Flexbox containers (`justify-content` + `align-items`)
+- `alignmentToGridCSS()` - For Grid containers (`justify-content` + `align-content`)
+- `alignmentToPlaceSelfCSS()` - For individual grid items (`place-self`)
+- `alignmentToTailwind()` - Returns Tailwind classes (`justify-* items-*`)
+
 ---
 
 ## Building Custom Components
@@ -417,7 +582,7 @@ export const puckConfig: Config = {
 Build custom components with pre-built fields:
 
 ```typescript
-import type { ComponentConfig } from '@measured/puck'
+import type { ComponentConfig } from '@puckeditor/core'
 import {
   createMediaField,
   createBackgroundField,
@@ -539,8 +704,11 @@ This is the recommended pattern for Payload apps. The provider wraps only the ad
 | `createBorderField()` | Border styling |
 | `createDimensionsField()` | Width/height constraints |
 | `createAnimationField()` | Entrance animations |
-| `createAlignmentField()` | Text alignment |
-| `createTiptapField()` | Inline rich text editor |
+| `createAlignmentField()` | Text alignment (left, center, right) |
+| `createContentAlignmentField()` | Visual 3x3 grid positioning selector |
+| `createSizeField()` | Size presets with custom mode |
+| `createRichTextField()` | Puck's native richtext with colors, font sizes, highlights |
+| `createResponsiveVisibilityField()` | Show/hide per breakpoint |
 
 ### CSS Helper Functions
 
@@ -554,12 +722,17 @@ import {
   borderValueToCSS,
   dimensionsValueToCSS,
   colorValueToCSS,
+  alignmentToFlexCSS,
+  alignmentToGridCSS,
+  sizeValueToCSS,
 } from '@delmaredigital/payload-puck/fields'
 
 const style = {
   background: backgroundValueToCSS(props.background),
   padding: paddingValueToCSS(props.padding),
   ...dimensionsValueToCSS(props.dimensions),
+  ...alignmentToFlexCSS(props.contentAlignment),
+  ...sizeValueToCSS(props.size),
 }
 ```
 
@@ -772,6 +945,196 @@ import { LegacyBlockRenderer } from '@/components/LegacyBlockRenderer'
 
 ---
 
+## AI Integration
+
+> **Early Preview:** While Puck's AI features are powerful, this plugin's implementation is still in early stages and under active development. Expect changes as we refine the integration.
+
+The plugin integrates with [Puck AI](https://puckeditor.com/docs/integrating-puck/ai) to enable AI-assisted page generation. Users can describe what they want in natural language, and the AI builds complete page layouts using your components.
+
+### Requirements
+
+- `PUCK_API_KEY` environment variable (from [Puck Cloud](https://puckeditor.com))
+- AI features require `@puckeditor/plugin-ai` and `@puckeditor/cloud-client` (bundled with the plugin)
+
+### Quick Start
+
+Enable AI in your plugin configuration:
+
+```typescript
+createPuckPlugin({
+  pagesCollection: 'pages',
+  ai: {
+    enabled: true,
+    context: 'We are Acme Corp, a B2B SaaS company. Use professional language.',
+  },
+})
+```
+
+This automatically:
+- Registers the AI chat endpoint at `/api/puck/ai`
+- Adds the AI chat plugin to the editor
+- Applies comprehensive component instructions for better generation quality
+
+### Dynamic Business Context
+
+Instead of hardcoding context in your config, you can manage it through Payload admin:
+
+```typescript
+createPuckPlugin({
+  ai: {
+    enabled: true,
+    contextCollection: true,  // Creates puck-ai-context collection
+  },
+})
+```
+
+This creates a `puck-ai-context` collection where you can add entries for:
+- **Brand Guidelines** - Colors, fonts, brand voice
+- **Tone of Voice** - How to communicate
+- **Product Information** - What you sell/offer
+- **Industry Context** - Your market and audience
+- **Technical Requirements** - Specific constraints
+- **Page Patterns** - Common layout structures
+
+Context entries can be enabled/disabled and ordered. The AI receives all enabled entries sorted by order.
+
+### Context Editor Plugin
+
+When `contextCollection: true`, a "Context" panel appears in the Puck plugin rail. Users can view, create, edit, and toggle context entries directly in the editor without visiting Payload admin.
+
+### Prompt Management
+
+Store reusable prompts in Payload:
+
+```typescript
+createPuckPlugin({
+  ai: {
+    enabled: true,
+    promptsCollection: true,  // Creates puck-ai-prompts collection
+    examplePrompts: [
+      { label: 'Landing page', prompt: 'Create a landing page for...' },
+    ],
+  },
+})
+```
+
+Prompts from the collection appear in the AI chat interface. A "Prompts" panel in the plugin rail allows in-editor prompt management.
+
+### Custom Tools
+
+Enable the AI to query your data:
+
+```typescript
+import { z } from 'zod'
+
+createPuckPlugin({
+  ai: {
+    enabled: true,
+    tools: {
+      getProducts: {
+        description: 'Get products from the database',
+        inputSchema: z.object({ category: z.string() }),
+        execute: async ({ category }, { payload }) => {
+          return await payload.find({
+            collection: 'products',
+            where: { category: { equals: category } },
+          })
+        },
+      },
+    },
+  },
+})
+```
+
+Tools receive a context object with the Payload instance and authenticated user.
+
+### AI Configuration Options
+
+| Option | Default | Description |
+|--------|---------|-------------|
+| `enabled` | `false` | Enable AI features |
+| `context` | `undefined` | Static system context for the AI |
+| `contextCollection` | `false` | Create `puck-ai-context` collection for dynamic context |
+| `promptsCollection` | `false` | Create `puck-ai-prompts` collection for reusable prompts |
+| `examplePrompts` | `[]` | Static example prompts for the chat interface |
+| `tools` | `undefined` | Custom tools for AI to query your system |
+| `componentInstructions` | `undefined` | Override default component AI instructions |
+
+### Component Instructions
+
+The plugin includes comprehensive instructions for all built-in components, teaching the AI:
+- Correct field names and values
+- Component composition patterns
+- Page structure best practices (Hero → Features → CTA flow)
+- Semantic HTML usage
+
+To customize or extend:
+
+```typescript
+createPuckPlugin({
+  ai: {
+    enabled: true,
+    componentInstructions: {
+      Heading: {
+        ai: { instructions: 'Use our brand voice: professional but approachable' },
+        fields: {
+          text: { ai: { instructions: 'Keep under 8 words' } },
+        },
+      },
+    },
+  },
+})
+```
+
+### Standalone API Routes
+
+For custom implementations outside the plugin:
+
+```typescript
+// app/api/puck/[...all]/route.ts
+import { createPuckAiApiRoutes } from '@delmaredigital/payload-puck/ai'
+import config from '@payload-config'
+
+export const POST = createPuckAiApiRoutes({
+  payloadConfig: config,
+  auth: {
+    authenticate: async (request) => {
+      // Your auth implementation
+      return { user: { id: '...' } }
+    },
+  },
+  ai: {
+    context: 'Your business context...',
+  },
+})
+```
+
+### AI Exports
+
+```typescript
+import {
+  // Plugins
+  createAiPlugin,
+  createPromptEditorPlugin,
+  createContextEditorPlugin,
+
+  // Hooks
+  useAiPrompts,
+  useAiContext,
+
+  // Config utilities
+  injectAiConfig,
+  comprehensiveComponentAiConfig,
+  pagePatternSystemContext,
+
+  // API routes
+  createPuckAiApiRoutes,
+  createAiGenerate,
+} from '@delmaredigital/payload-puck/ai'
+```
+
+---
+
 ## Advanced Configuration
 
 ### Plugin Options
@@ -785,6 +1148,8 @@ import { LegacyBlockRenderer } from '@/components/LegacyBlockRenderer'
 | `adminViewPath` | `'/puck-editor'` | Path for the editor (full path: `/admin/puck-editor/:collection/:id`) |
 | `pageTreeIntegration` | auto-detect | Integration with `@delmaredigital/payload-page-tree` |
 | `layouts` | `undefined` | Layout definitions for page templates |
+| `editorStylesheet` | `undefined` | Path to CSS file for editor iframe styling (e.g., `'src/app/globals.css'`) |
+| `editorStylesheetUrls` | `[]` | Additional stylesheet URLs for the editor (e.g., Google Fonts) |
 
 ```typescript
 createPuckPlugin({
@@ -812,6 +1177,52 @@ createPuckPlugin({
 })
 ```
 
+### Editor Stylesheet (Iframe Styling)
+
+The Puck editor renders page content in an iframe. By default, this iframe doesn't have access to your frontend's CSS (Tailwind utilities, CSS variables, fonts). The `editorStylesheet` option solves this by compiling and serving your CSS.
+
+**How it works:**
+1. You specify your CSS file path in the plugin config
+2. The plugin creates an endpoint at `/api/puck/styles`
+3. On first request, the CSS is compiled with PostCSS/Tailwind and cached
+4. The iframe loads this compiled CSS
+
+```typescript
+createPuckPlugin({
+  pagesCollection: 'pages',
+  // Your frontend's main CSS file
+  editorStylesheet: 'src/app/(frontend)/globals.css',
+  // External stylesheets (Google Fonts, etc.)
+  editorStylesheetUrls: [
+    'https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap'
+  ],
+})
+```
+
+Then update your `PuckConfigProvider` to use the compiled stylesheet:
+
+```typescript
+<PuckConfigProvider
+  config={editorConfig}
+  layouts={siteLayouts}
+  editorStylesheets={[
+    '/api/puck/styles',  // Plugin-created endpoint
+    'https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap'
+  ]}
+>
+  {children}
+</PuckConfigProvider>
+```
+
+**Requirements:**
+- `postcss` must be installed in your project
+- For Tailwind v4: `@tailwindcss/postcss`
+- For Tailwind v3: `tailwindcss`
+
+The CSS is compiled at runtime (cached after first request) using your project's PostCSS/Tailwind installation.
+
+---
+
 ### Custom API Routes (Advanced)
 
 The built-in endpoints handle most use cases. Only disable them if you need custom authentication or middleware.
@@ -845,6 +1256,7 @@ See the JSDoc in `@delmaredigital/payload-puck/api` for usage examples.
 | `@delmaredigital/payload-puck/theme` | `ThemeProvider`, theme utilities |
 | `@delmaredigital/payload-puck/layouts` | Layout definitions, `LayoutWrapper` |
 | `@delmaredigital/payload-puck/api` | API route factories (for custom implementations) |
+| `@delmaredigital/payload-puck/ai` | AI plugins, hooks, config utilities, API routes |
 | `@delmaredigital/payload-puck/admin/client` | `EditWithPuckButton`, `EditWithPuckCell` |
 
 ---

package/dist/admin/PuckEditorView.d.ts

@@ -1,4 +1,4 @@
-import type { Config as PuckConfig, Data, Plugin as PuckPlugin } from '@measured/puck';
+import type { Config as PuckConfig, Data, Plugin as PuckPlugin } from '@puckeditor/core';
 /**
  * Props for the PuckEditorView component
  */

package/dist/admin/PuckEditorView.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"PuckEditorView.d.ts","sourceRoot":"","sources":["../../src/admin/PuckEditorView.tsx"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,MAAM,IAAI,UAAU,EAAE,IAAI,EAAE,MAAM,IAAI,UAAU,EAAE,MAAM,gBAAgB,CAAA;AAEtF;;GAEG;AACH,MAAM,WAAW,mBAAmB;IAClC;;OAEG;IACH,MAAM,EAAE,UAAU,CAAA;IAClB;;;OAGG;IACH,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB;;;OAGG;IACH,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB;;;OAGG;IACH,OAAO,CAAC,EAAE,MAAM,CAAA;IAChB;;OAEG;IACH,UAAU,CAAC,EAAE,MAAM,GAAG,CAAC,CAAC,IAAI,EAAE,MAAM,KAAK,MAAM,CAAC,CAAA;IAChD;;OAEG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE;QAAE,UAAU,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,OAAO,CAAA;KAAE,CAAC,CAAA;IACtE;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,CAAA;IAClB;;;;OAIG;IACH,OAAO,CAAC,EAAE,UAAU,EAAE,GAAG,KAAK,CAAA;IAC9B;;OAEG;IACH,aAAa,CAAC,EAAE,CAAC,IAAI,EAAE,IAAI,KAAK,IAAI,CAAA;IACpC;;OAEG;IACH,WAAW,CAAC,EAAE,CAAC,KAAK,EAAE,KAAK,KAAK,IAAI,CAAA;CACrC;AAUD;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,wBAAgB,cAAc,CAAC,EAC7B,MAAM,EACN,cAAwB,EACxB,WAAyB,EACzB,OAAO,EACP,UAAU,EACV,YAAY,EACZ,SAAwB,EACxB,OAAO,EACP,aAAa,EACb,WAAW,GACZ,EAAE,mBAAmB,2CAkKrB;AAED,eAAe,cAAc,CAAA"}
+{"version":3,"file":"PuckEditorView.d.ts","sourceRoot":"","sources":["../../src/admin/PuckEditorView.tsx"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,MAAM,IAAI,UAAU,EAAE,IAAI,EAAE,MAAM,IAAI,UAAU,EAAE,MAAM,kBAAkB,CAAA;AAExF;;GAEG;AACH,MAAM,WAAW,mBAAmB;IAClC;;OAEG;IACH,MAAM,EAAE,UAAU,CAAA;IAClB;;;OAGG;IACH,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB;;;OAGG;IACH,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB;;;OAGG;IACH,OAAO,CAAC,EAAE,MAAM,CAAA;IAChB;;OAEG;IACH,UAAU,CAAC,EAAE,MAAM,GAAG,CAAC,CAAC,IAAI,EAAE,MAAM,KAAK,MAAM,CAAC,CAAA;IAChD;;OAEG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE;QAAE,UAAU,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,OAAO,CAAA;KAAE,CAAC,CAAA;IACtE;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,CAAA;IAClB;;;;OAIG;IACH,OAAO,CAAC,EAAE,UAAU,EAAE,GAAG,KAAK,CAAA;IAC9B;;OAEG;IACH,aAAa,CAAC,EAAE,CAAC,IAAI,EAAE,IAAI,KAAK,IAAI,CAAA;IACpC;;OAEG;IACH,WAAW,CAAC,EAAE,CAAC,KAAK,EAAE,KAAK,KAAK,IAAI,CAAA;CACrC;AAUD;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,wBAAgB,cAAc,CAAC,EAC7B,MAAM,EACN,cAAwB,EACxB,WAAyB,EACzB,OAAO,EACP,UAAU,EACV,YAAY,EACZ,SAAwB,EACxB,OAAO,EACP,aAAa,EACb,WAAW,GACZ,EAAE,mBAAmB,2CAkKrB;AAED,eAAe,cAAc,CAAA"}

package/dist/ai/collections/AiContext.d.ts

@@ -0,0 +1,16 @@
+import type { CollectionConfig } from 'payload';
+/**
+ * AI Context Collection
+ *
+ * Stores business context entries for the AI chat interface.
+ * These context entries are concatenated and sent to the AI system prompt
+ * to help it understand your brand, tone, and requirements.
+ *
+ * @example Creating context entries in Payload admin:
+ * - "Brand Guidelines" - Colors, fonts, brand voice
+ * - "Tone of Voice" - How to communicate
+ * - "Product Information" - What you sell/offer
+ * - "Industry Context" - Your market and audience
+ */
+export declare const AiContextCollection: CollectionConfig;
+//# sourceMappingURL=AiContext.d.ts.map

package/dist/ai/collections/AiContext.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"AiContext.d.ts","sourceRoot":"","sources":["../../../src/ai/collections/AiContext.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,SAAS,CAAA;AAE/C;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,mBAAmB,EAAE,gBA0EjC,CAAA"}