@bison-lab/payload-blocks 3.20.0 → 3.22.0

package/README.md

@@ -365,38 +365,41 @@ globals: [
 
 Then `payload generate:types`, `payload generate:importmap`, and
 `payload migrate:create`. Until the import map includes
-`@bison-lab/payload-blocks/admin#NavItemsField`, the items field renders
+`@bison-lab/payload-blocks/admin#NavItemsField` and
+`@bison-lab/payload-blocks/admin#AdminWorkspace`, those slots render
 as nothing, not the stock blocks UI.
 
-An editor sees a rail of bar items (Link vs Mega type cards from
-`@bison-lab/admin-ui`), destinations
-through `LINK_FIELD`, a two-up column builder, and a sticky
-`FloatingNavBlock` preview under the published theme. Advanced CSS
-column widths stay on the schema so existing rows do not migrate; the
-kit does not render them. The column widths, read as fractions, must add
-up to 100%: the rule is the array's own `validate`, so the editor sees
+An editor opening Header sees the admin workspace: title strip (Payload
+status / Save draft / Publish), a 300px item rail, and a canvas with a
+sticky kit preview of the bar (Theme Identity lockup when one exists). Destinations
+go through `LINK_FIELD`. The Header button is the rail slot that
+writes `header.cta` (off until the editor enables it; label and destination
+are required to save while it is on). Column widths, read as fractions, must add up to
+100%: the rule is the array's own `validate`, so the editor sees
 "The columns add up to 75%. They need to add up to 100%." as they build,
-and the global's publish refuses the same. Custom widths skip it. The
-mega trigger's landing page is now the same `type` / `page` / `href`
-picker as every other destination — a schema change, so sites run
-`payload migrate:create`.
+and the global's publish refuses the same. A panel is narrow, standard,
+or wide. The mega trigger's landing page is the same `type` / `page` /
+`href` picker as every other destination.
 
-In the site header, one call turns the rows into `FloatingNavBlock` items.
-The variants and icons here are the looks behind the values above:
+In the site header, one call turns the fetched Header global into
+`FloatingNavBlock` props. Looks come from chrome roles
+(`megaMenuVariantsFromLooks`), not a list on Header:
 
 ```tsx
 'use client'
-import { FloatingNavBlock } from '@bison-lab/ui'
-import { headerItemsFromBlocks } from '@bison-lab/payload-blocks/react'
+import { FloatingNavBlock, megaMenuVariantsFromLooks } from '@bison-lab/ui'
+import { headerFromNavigation } from '@bison-lab/payload-blocks/react'
 import { usePathname } from 'next/navigation'
 
-export function SiteHeader({ items }: { items: Navigation['items'] }) {
+export function SiteHeader({ doc }: { doc: Navigation }) {
   const pathname = usePathname()
   return (
     <FloatingNavBlock
-      breakpoint="lg" // the panel flattens below lg; the bar must switch there too
-      items={headerItemsFromBlocks(items, {
-        variants: { lumbar: { chip: '…', title: '…', icon: <Marker region="lumbar" /> }, si: { … } },
+      {...headerFromNavigation(doc, {
+        looks: megaMenuVariantsFromLooks(['lumbar', 'si'], {
+          lumbar: <Marker region="lumbar" />,
+          si: <Marker region="si" />,
+        }),
         icons: { help: <CircleHelp className="size-4" aria-hidden /> },
         isActive: (href) => pathname.startsWith(href),
         linkComponent: NextBlockLink,
@@ -407,6 +410,20 @@ export function SiteHeader({ items }: { items: Navigation['items'] }) {
 }
 ```
 
+`headerItemsFromBlocks` is still the items half. Public headers must
+call `headerFromNavigation` so hidden `bar` defaults reach the bar.
+
+## Navigation settings
+
+Bar behaviour stays on the Header schema (`bar.hideOnScroll`,
+`bar.viewport`, `bar.defaultMaxWidth`) and is hidden in the admin.
+The workspace canvas is the Header preview — do not leave a split
+live-preview iframe. The kit editor holds the edited mega row open
+through `openItem`. Featured looks stay on the chrome-role registry
+(BIS-85 / SPI-89) — Header has no `variants` array. The Spinal consume
+is SPI-99. After this schema change run `payload generate:importmap`,
+`payload generate:types`, and `payload migrate:create`.
+
 `MegaMenuBlockRenderer` renders one panel on its own, which is what a live
 preview of the row wants; it is not a page block and has no place in the
 registry. A row with no columns, or whose columns hold no complete links,

package/dist/admin.d.mts

@@ -1,6 +1,14 @@
 
-import { ArrayFieldClientComponent, BlocksFieldClientComponent, RowFieldClientComponent } from "payload";
+import * as react_jsx_runtime0 from "react/jsx-runtime";
+import { ArrayFieldClientComponent, BlocksFieldClientComponent, DocumentViewClientProps, RowFieldClientComponent } from "payload";
 
+//#region src/admin/admin-workspace.d.ts
+/**
+ * Wraps Payload's DefaultEditView so Header (and later kit editors)
+ * become the mockup workspace. Does not mount a second Form.
+ */
+declare function AdminWorkspace(props: DocumentViewClientProps): react_jsx_runtime0.JSX.Element;
+//#endregion
 //#region src/admin/link-field.d.ts
 declare const LinkField: RowFieldClientComponent;
 //#endregion
@@ -29,5 +37,5 @@ declare const MinRowsArrayField: ArrayFieldClientComponent;
 //#region src/admin/nav-items-field.d.ts
 declare const NavItemsField: BlocksFieldClientComponent;
 //#endregion
-export { LinkField, MinRowsArrayField, NavItemsField };
+export { AdminWorkspace, LinkField, MinRowsArrayField, NavItemsField };
 //# sourceMappingURL=admin.d.mts.map

package/dist/admin.d.mts.map

@@ -1 +1 @@
-{"version":3,"file":"admin.d.mts","names":[],"sources":["../src/admin/link-field.tsx","../src/admin/min-rows-array-field.tsx","../src/admin/nav-items-field.tsx"],"mappings":";;;;cAuEa,SAAA,EAAW,uBAAA;;;;;AAAxB;;;;;;;;AChDA;;;;;;;;ACqKA;cDrKa,iBAAA,EAAmB,yBAAA;;;cCqKnB,aAAA,EAAe,0BAAA"}
+{"version":3,"file":"admin.d.mts","names":[],"sources":["../src/admin/admin-workspace.tsx","../src/admin/link-field.tsx","../src/admin/min-rows-array-field.tsx","../src/admin/nav-items-field.tsx"],"mappings":";;;;;;;;AAWA;iBAAgB,cAAA,CAAe,KAAA,EAAO,uBAAA,GAAuB,kBAAA,CAAA,GAAA,CAAA,OAAA;;;cC4DhD,SAAA,EAAW,uBAAA;;;;;;AD5DxB;;;;;;;;;;;;;AC4DA;;;cChDa,iBAAA,EAAmB,yBAAA;;;cC6MnB,aAAA,EAAe,0BAAA"}