@bettercms-ai/mcp 0.64.1 → 0.65.1

package/dist/skills/bettercms/SKILL.md

@@ -54,7 +54,9 @@ These hold on every task. The reference in brackets has the detail and the codes
    Its `authoringPreference` (components, fields, or null while owed) is asked once, can be
    re-answered, and is the user's answer, never yours.
 2. **Never create SEO fields** (§5b). Page and entry meta are native columns. [seo.md]
-3. **A page is a list of sections**, never loose top-level blocks. [components.md]
+3. **A page is a list of sections**, never loose top-level blocks, and never a nav, footer or
+   modal: chrome is the Layout. A call to action is one `button` field, never a text field
+   beside a link field. [components.md, content-modeling.md]
 4. **Nothing is live until it is published, and a page is not its content.** A draft form,
    component or entry renders nothing live. Read `warnings` on every write: `ENTRY_STILL_DRAFT`
    and `ENTRY_SEED_FAILED` mean content did not ship. [publishing.md]

package/dist/skills/bettercms/references/astro.md

@@ -42,6 +42,7 @@ build. Pass `apiUrl` and `workspace` as options, or let the snapshot supply them
 | `@bettercms-ai/astro/components/BcmsBlocks.astro` | Server render of a block tree. Pass `components` or instances render nothing |
 | `@bettercms-ai/astro/components/BcmsLiveBlocks.astro` | Same tree as a hydrated island that follows the editor's draft bridge |
 | `@bettercms-ai/astro/components/BcmsField.astro` | `path`, `kind` (`richtext`/`image`), `as`; emits `data-bcms-field` + `data-bcms-kind` |
+| `@bettercms-ai/astro/components/BcmsButton.astro` | A `button` field: `path`, `value`, `class`. One `<a>` with the label bound, the href in `data-bcms-props` and `data-variant` / `data-size` for your CSS; renders nothing without a label |
 | `@bettercms-ai/astro/components/BcmsForm.astro` | Renders a delivered form and submits it ([forms-and-interactions.md](forms-and-interactions.md)) |
 
 `BcmsLiveBlocks` rules:
@@ -52,6 +53,10 @@ build. Pass `apiUrl` and `workspace` as options, or let the snapshot supply them
 
 ## Bindings
 
+A section root your own code renders spreads `sectionRootAttrs(block)` from `@bettercms-ai/astro`
+(`data-bcms-block`, `data-bcms-style` and the block's style), so the editor can move it and offer
+its spacing handles ([components.md](components.md) §5).
+
 `bind` and `bindProps` from `@bettercms-ai/astro/bindings` produce the same attributes as the Next
 helpers. Use them inside component instances so addresses resolve to the instance
 ([bindings.md](bindings.md) §3).

package/dist/skills/bettercms/references/componentize.md

@@ -41,8 +41,10 @@ Never let a component contain itself, directly or through a child.
    `NO_GROUP_ROOT` (keys are still the derive lane's own, such as `h1-welcome`: rename them into
    families first), `NOT_A_SECTION` (a lone scalar or page metadata; `detail: ENTRY_METADATA` is
    a template's frontmatter, `detail: DECLINED` a group the user declined) and `IMAGE_AS_TEXT`
-   (a text field holding an image path; it plans once the field is an image). Author the real
-   sections among those with `create_component` and `set_page_content` instead.
+   (a text field holding an image path; it plans once the field is an image). A nav, footer or
+   modal group is `NOT_A_SECTION` with `detail: LAYOUT_CHROME`: chrome is the Layout on every
+   site, never a page band. Author the real sections among those with `create_component` and
+   `set_page_content` instead.
 2. Show the user the sections, how many components it creates and which pages it rewrites.
    Confirm before writing. A group the user says is not a section: `componentize_sections
    { digest, sections: [groupKey], pageIds, decline: true }` (`decline: false` undoes it). The

package/dist/skills/bettercms/references/components.md

@@ -141,6 +141,30 @@ page that renders its own header or footer does not get the Layout's copy on top
 Rule: if an instance renders empty, check that definitions were passed before debugging the
 component.
 
+### When the site's own code renders the sections
+
+A code-built site ships only what its templates draw, whatever the page's `blockJson` says.
+
+- **Render the page's block list, never hard-coded bands.** A section added or moved in the
+  editor reaches the live site only when the template loops over the page's blocks in order and
+  each section root carries its block id as `data-bcms-block`. The codemod's `--componentize` pass
+  generates `src/lib/bcms-sections.ts` for the loop and adds those attributes. Until it ships, the
+  editor locks Add section and reordering on that route, and `submit_conversion_receipt` keeps
+  `complete: false` with one `SECTIONS_UNSTAMPED` row per route.
+- **No chrome placements on a page.** A nav, footer or modal placement the site's layout draws
+  renders nowhere, and the editor locks its outline row and skips it when it moves the sections
+  around it. Remove it.
+- **Spread `sectionRootAttrs(block)` on each root you write by hand** (`@bettercms-ai/astro`,
+  `@bettercms-ai/next`): it adds `data-bcms-block`, `data-bcms-style` and the block's style. The
+  editor offers section spacing and style handles only when every stamped root carries
+  `data-bcms-style`. A site converted before it existed shows none and `get_next_steps` lists
+  `upgrade-section-roots`. The fix is the codemod's `--upgrade-sections` mode, latest version, at
+  the repo root (`--dry-run` first); give each root it reports as skipped (`OWN_STYLE`, `SPREAD`,
+  `BLOCK_ID_ONLY`, …) its block style by hand, confirm with `--verify-styles`, push and release.
+- **A `button` field renders with `BcmsButton`** (`path`, `value`): one `<a>` carrying
+  `data-variant` and `data-size`, so the site's CSS decides what each look looks like and the
+  editor repaints it live.
+
 ## 6. Preview source
 
 - `set_component_source` records which file in the repo implements a component;

package/dist/skills/bettercms/references/content-modeling.md

@@ -83,6 +83,16 @@ sitemap), RSS (dated by `publishedAt`), `llms.txt` (one link per published item)
   URL for links that leave the site.
 - A repeater for small, same-shaped items (cards, FAQ rows, links, social accounts); a nested
   component or slot when an item has its own layout or variants.
+- **Model a call to action as a single `button` field.** It stores `{ label, href }` plus the
+  optional look keys `variant`, `size`, `arrow`, `icon` and `newTab`, and the site draws it with
+  `BcmsButton` ([astro.md](astro.md), [next.md](next.md)). Never a text
+  field beside a link field: the pair has nowhere to keep a look, and a new pair in the importer's
+  spelling (`hero-span-go` + `hero-a-go-href`) is refused with 400 `cta_pair` on `add_field`,
+  `create_page` and model writes. A page that already holds a pair (`primaryCtaText` +
+  `primaryCtaHref`) becomes one button with `update_field` `{ pageId, path: "primaryCtaText",
+  mergeHref: "primaryCtaHref" }`: each entry's DRAFT gets `{ label, href }` and keeps the old values,
+  so code still reading them keeps rendering; the live copy changes on publish. Inside a component
+  a CTA is a `button` block whose `props.text` and `props.href` two props target.
 - Never model SEO columns ([seo.md](seo.md)), Form questions (they live on the Form document) or
   Global Layout values as content fields.
 - Keep source ids, slugs, locale, status and previous URLs as migration metadata, stable across

package/dist/skills/bettercms/references/next.md

@@ -41,6 +41,8 @@ webhook. Use the project's webhook secret from the dashboard (the package docs n
 | `BcmsBlocks` | Render a block tree; pass `components` from `readComponents()` |
 | `readComponents()` | Component definitions from `bcms-content.json` |
 | `BcmsField` | `path`, `kind` (`richtext`/`image`), `as`; server-safe |
+| `BcmsButton` | A `button` field: `path`, `value`, `className`; one `<a>` with `data-variant` / `data-size` for your CSS; server-safe |
+| `sectionRootAttrs(block)` | Spread on a section root your own code renders: `data-bcms-block`, `data-bcms-style` and the block's style ([components.md](components.md) §5) |
 | `bind`, `bindProps` | Binding attributes; instance-aware inside components |
 | `BcmsForm` + `getForm(idOrName)` | Forms from the snapshot ([forms-and-interactions.md](forms-and-interactions.md)) |
 | `buildMetadata(page, siteDefaults, location?)` | Next `Metadata` from native SEO fields |

package/dist/skills/bettercms/references/portable-text.md

@@ -43,7 +43,8 @@ intended UX; confirm each control exists in the connected editor before promisin
 | FAQ question | text | plain | inside an accessible trigger; the component owns the level |
 | FAQ answer, modal body | narrowed richtext | paragraphs, lists, links, emphasis | focus and ARIA live outside the value |
 | Image | image | asset, alt text, caption | bind `src` and `alt` separately |
-| Link or button | grouped fields | label, link, style variant | no raw HTML, no `javascript:` URL |
+| Link | link | the destination | no raw HTML, no `javascript:` URL |
+| Button / call to action | one `button` field | label, link, style, size, arrow, icon, new tab | render with `BcmsButton`; never a text + link pair |
 
 "Disabled" controls mean the field's accept list removes irrelevant formatting; the field stays
 editable. Keep a source's unusual but valid hierarchy when changing it would alter meaning, and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bettercms-ai/mcp",
-  "version": "0.64.1",
+  "version": "0.65.1",
   "type": "module",
   "description": "BetterCMS MCP server — schema, content, forms + components authoring tools over the Management API, authed via OAuth device-code.",
   "bin": {