create-kywi-app 0.7.1 → 0.9.0

package/assets/agent-patterns.md

@@ -443,7 +443,15 @@ interchangeable.
   pin) and A/B experiments. Since 0.6.3 it also renders in the layout editor as
   a badged block with an **arm switcher**, each arm editable with the ordinary
   section/column/module tools, so server-resolution no longer costs the owner
-  their editing surface.
+  their editing surface. Since kywi-cms#119, the owner doesn't need an agent to
+  hand-author this shape at all: the section chrome — in the admin layout
+  editor and in the in-place front-of-site overlay alike — offers
+  **Personalize this section** / **A/B test** actions that wrap an ordinary
+  section into a section-level variant container on the spot, seeding the
+  default arm from the section's current content and opening straight into its
+  config (audience/experiment picker included). An agent only needs to reach
+  for `update_layout` when scripting bulk changes or building a container the
+  UI can't reach.
 - **Module-level** — the `variantContainer` *module*, placed in a column; its
   arms are HTML strings (`defaultContent`, `variants: [{audienceId, label,
   content}]`). Every arm ships in the HTML (default visible, the rest

package/lib/templates.mjs

@@ -1559,6 +1559,7 @@ export default async function PublicPage({ params, searchParams }: Params & Sear
         initialLayout={layout ?? { regions: { main: [] } }}
         adminHref={\`/admin/content/\${contentType}/\${contentId}\`}
         moduleComponents={moduleComponents}
+        hostModules={config.modules ?? []}
       >
         {content}
       </KywiFrontEdit>
@@ -1607,6 +1608,7 @@ import {
   BUILT_IN_MODULE_COMPONENTS,
   type LayoutDocument,
   type ModuleComponentMap,
+  type ModuleConfig,
 } from '@kywi-software/core/layout'
 import type { SaveAction } from '@kywi-software/core/admin'
 
@@ -1638,6 +1640,10 @@ export interface KywiFrontEditProps {
   adminHref: string
   /** Custom (defineModule) renderers, shared with the public layout + admin (#48). */
   moduleComponents?: ModuleComponentMap
+  /** Custom (defineModule) module CONFIGS from kywi.config.ts — gives the overlay
+   *  editor each custom module's prop definitions, so the props rail and inline
+   *  text editing work for them exactly as in the admin editor (kywi-cms#118). */
+  hostModules?: ModuleConfig[]
   children: React.ReactNode
 }
 
@@ -1662,6 +1668,7 @@ export function KywiFrontEdit({
   initialLayout,
   adminHref,
   moduleComponents = {},
+  hostModules = [],
   children,
 }: KywiFrontEditProps) {
   const edit = useKywiEditMode({ canEdit, canPublish })
@@ -1675,10 +1682,14 @@ export function KywiFrontEdit({
     if (editRequested) startEdit()
   }, [editRequested, startEdit])
 
-  // Registries + renderers for the editor: built from core (no module list is
-  // re-declared here) and merged with this app's custom module renderers from
-  // lib/modules — the SAME source the admin app and public renderer use (#48).
-  const moduleRegistry = React.useMemo(() => createModuleRegistry([]), [])
+  // Registries + renderers for the editor: the module registry carries each
+  // module's prop definitions (built-ins + this app's kywi.config.ts modules —
+  // without the host list, custom modules render but are uneditable, kywi-cms#118),
+  // merged with the custom renderers from lib/modules (#48).
+  const moduleRegistry = React.useMemo(
+    () => createModuleRegistry(hostModules ?? []),
+    [hostModules],
+  )
   const themeRegistry = React.useMemo(() => createThemeRegistry(), [])
   const editorComponents = React.useMemo(
     () => ({ ...BUILT_IN_MODULE_COMPONENTS, ...moduleComponents }),
@@ -2215,10 +2226,10 @@ leaving the editor keeps \`?kywi-edit=1\` in the URL in sync, so reloading (or
 sharing the link) lands back in the same mode. It all lives in
 \`app/(site)/kywi-front-edit.tsx\`; the editor bundle (and the admin stylesheet) is
 lazy-loaded, so pages your visitors see never carry its weight — an anonymous
-or read-only visitor gets no toolbar and no extra client JS. Note: custom
-\`defineModule\` types still RENDER on the canvas, but they don't appear in the
-front-of-site editor's insert palette (it uses the built-in module set) — add
-them from the admin's Layout tab instead.
+or read-only visitor gets no toolbar and no extra client JS. Custom
+\`defineModule\` types from \`kywi.config.ts\` also appear in the front-of-site
+editor's insert palette and are fully editable in place — the props rail and
+inline text editing work exactly as they do in the admin's Layout tab.
 
 ## Personalization, A/B testing & self-ID
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-kywi-app",
-  "version": "0.7.1",
+  "version": "0.9.0",
   "description": "Scaffold a new Kywi CMS project — npx create-kywi-app my-site",
   "type": "module",
   "homepage": "https://github.com/Kywi-Software/kywi-cms#readme",