@actuate-media/sections-react 0.2.12 → 0.2.14

package/CHANGELOG.md

@@ -0,0 +1,210 @@
+# @actuate-media/sections-react
+
+## 0.2.14
+
+### Patch Changes
+
+- Updated dependencies [0c3a6eb]
+  - @actuate-media/cms-core@0.61.0
+
+## 0.2.13
+
+### Patch Changes
+
+- 854152d: Developer experience improvements from external-consumer feedback:
+  - Every published package now ships its `CHANGELOG.md` in the npm tarball, and packages that were missing a `README.md` (cli, cms-admin, cms-core, import, platform-vercel, all plugins, sections-react) now have one — so release notes and usage docs are visible on npmjs.com and in `node_modules`.
+  - New client-safe form validation entry point: `@actuate-media/cms-core/forms/client` exports `validateFormFieldClient()`, `validateFormValuesClient()`, visibility/conditional helpers, and the exact `FORM_EMAIL_RE` / `FORM_PHONE_RE` regexes the server enforces — zero Node dependencies, so public-site forms can mirror server rules without reimplementing them. The server validator now imports the same primitives, so client and server can never drift.
+
+- Updated dependencies [854152d]
+- Updated dependencies [bf5f857]
+  - @actuate-media/cms-core@0.60.0
+
+## 0.2.12
+
+### Patch Changes
+
+- Updated dependencies [15b3f45]
+  - @actuate-media/cms-core@0.59.1
+
+## 0.2.11
+
+### Patch Changes
+
+- Updated dependencies [f962e2d]
+- Updated dependencies [73a117a]
+  - @actuate-media/cms-core@0.59.0
+
+## 0.2.10
+
+### Patch Changes
+
+- Updated dependencies [363bb3e]
+  - @actuate-media/cms-core@0.58.0
+
+## 0.2.9
+
+### Patch Changes
+
+- Updated dependencies [a5f8bc0]
+  - @actuate-media/cms-core@0.57.1
+
+## 0.2.8
+
+### Patch Changes
+
+- Updated dependencies [8e73cf5]
+  - @actuate-media/cms-core@0.57.0
+
+## 0.2.7
+
+### Patch Changes
+
+- Updated dependencies [99565a1]
+  - @actuate-media/cms-core@0.56.0
+
+## 0.2.6
+
+### Patch Changes
+
+- Updated dependencies [74662c0]
+  - @actuate-media/cms-core@0.55.0
+
+## 0.2.5
+
+### Patch Changes
+
+- Updated dependencies [29f32ba]
+  - @actuate-media/cms-core@0.54.0
+
+## 0.2.4
+
+### Patch Changes
+
+- Updated dependencies [aa4bd1a]
+  - @actuate-media/cms-core@0.53.0
+
+## 0.2.3
+
+### Patch Changes
+
+- Updated dependencies [01eef99]
+  - @actuate-media/cms-core@0.52.0
+
+## 0.2.2
+
+### Patch Changes
+
+- Updated dependencies [aeee3a4]
+  - @actuate-media/cms-core@0.51.2
+
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [f88a406]
+  - @actuate-media/cms-core@0.51.1
+
+## 0.2.0
+
+### Minor Changes
+
+- 204da7a: WS-E (E3): media resolution + responsive images in the public render path.
+  - **sections-react:** new pluggable `renderImage` `RenderOptions` hook (with
+    exported `RenderImage`/`RenderImageProps` types and a `defaultRenderImage`).
+    The default emits a lazy, `decoding="async"` `<img>` and forwards intrinsic
+    `width`/`height` when known; a Next.js consumer can pass a `next/image`-backed
+    renderer for responsive `srcset` + optimization. The `feature`, `gallery`, and
+    post-header images now route through it (`<PostHeader>` gains an optional
+    `options` prop). The package stays React-only — no `next` dependency.
+  - **cms-core:** the `/resolve` endpoint now enriches section images with
+    intrinsic `width`/`height` and library `altText`, matched from `actuate_media`
+    by stored URL (`storageKey`/`publicUrl`). Additive and best-effort — the
+    stored document is never mutated and a lookup failure never breaks resolve.
+    `feature` sections gain `imageWidth`/`imageHeight` (+ backfilled `imageAlt`);
+    `gallery` rows gain `width`/`height` (+ backfilled `alt`).
+  - **create-actuate-cms:** the generated catch-all page renders CMS images via a
+    `next/image`-backed `renderImage` (falling back to a fluid `<img>` when the
+    CMS doesn't know dimensions), and `next.config` now allow-lists the storage
+    host under `images.remotePatterns` so optimization works out of the box.
+
+- 2f18c56: WS-E (E2): public form rendering — a built site can now render and submit a CMS form end to end.
+  - **sections-react:** new `<ActuateForm>` Client Component fetches the public form
+    schema (`GET /api/cms/public/forms/:slug`), renders the fields (text/email/
+    url/tel/number/date, textarea, select, checkbox, radio), and submits to the
+    schema's `submitPath`. Spam protection is wired automatically: a hidden
+    honeypot (keyed from `spam.honeypotFieldKey`), an `elapsedMs` "time to submit"
+    timer, and an optional consumer-supplied `captchaToken`. Pre-fetch a schema via
+    the `form` prop to skip the round-trip (SSR/streaming). Adds a `baseUrl`
+    `RenderOptions` field (defaults to same-origin). Exposes pure, tested helpers
+    (`coercePublicForm`, `buildSubmitBody`, `fieldControl`, `firstMissingRequired`).
+  - **cms-core:** new canonical `form` section type. Set `content.formSlug` (plus
+    optional heading/intro) on any page or post and the matching renderer embeds
+    the form. The registry-drift guard now covers it (renderer ↔ type).
+  - **cms-admin:** the form Embed panel now shows the real public endpoints
+    (`/api/cms/public/forms/:slug` + `/submit`) and a copy-paste `<ActuateForm>`
+    snippet, replacing the previously-advertised `/api/forms/*`, iframe, and
+    `embed.js` routes that were never implemented. Adds a `mail` section icon.
+
+- e2e0bd7: WS-E (E4): public navigation endpoint + navigation rendering in the scaffold.
+  - **cms-core:** new unauthenticated `GET /api/cms/public/navigations/:slug` that
+    returns a clean `{ name, slug, location, items }` tree. Like globals it is site
+    chrome — not status-gated — and safe when the navigation plugin isn't installed
+    (no match → 404). A shared, pure `coercePublicNavItems` helper sanitizes the
+    open `data.items` JSON: drops unlabeled nodes, strips internal `id`s, caps
+    recursion depth, and only passes through `_blank`/`_self` targets. Both
+    `createSiteClient` and `createServerSiteClient` gain `getNavigation(slug)`
+    returning `PublicNavigation | null`, and `PublicNavigation` / `PublicNavItem`
+    are now exported types.
+  - **sections-react:** new presentational `<SiteNav>` — an accessible `<nav>`
+    landmark whose submenus use native `<details>`/`<summary>` disclosure
+    (keyboard-operable, no client JS). New-tab links get
+    `rel="noopener noreferrer"`; an empty menu renders nothing. Exports `SiteNav`
+    plus `SiteNavProps`/`SiteNavItem`.
+  - **create-actuate-cms:** `lib/cms.ts` re-exports `getNavigation`, and the
+    generated site layout fetches the `main` menu and renders a header with the
+    site name + `<SiteNav>`, degrading gracefully to just the name when no menu
+    exists yet.
+
+### Patch Changes
+
+- Updated dependencies [a413616]
+- Updated dependencies [204da7a]
+- Updated dependencies [2f18c56]
+- Updated dependencies [e2e0bd7]
+  - @actuate-media/cms-core@0.51.0
+
+## 0.1.2
+
+### Patch Changes
+
+- Updated dependencies [d7a144c]
+  - @actuate-media/cms-core@0.50.0
+
+## 0.1.1
+
+### Patch Changes
+
+- Updated dependencies [9ba332c]
+  - @actuate-media/cms-core@0.49.0
+
+## 0.1.0
+
+### Minor Changes
+
+- 989bd09: New package: a public React renderer for Actuate's canonical page-content
+  contract (ADR 0001 — `data.sections: PageSection[]`).
+  - `<Sections sections={...} ctx={...} />` renders all 10 built-in section types
+    (hero, text, feature, stats, cta, article-body, quote, author-bio,
+    related-posts, gallery) with zero hand-written mapper. SSR-first (safe in
+    React Server Components).
+  - `<PostHeader config={...} ctx={...} />` renders a post header from its
+    template config + the post's own fields.
+  - Consumer-controlled renderer registry: override any section type per-render
+    via the `renderers` prop, or app-wide via `registerSectionRenderer()`.
+    Resolution precedence: prop > global registry > built-in default > skip.
+  - Rich-text fields go through an injectable `options.sanitizeHtml` hook
+    (default identity; Actuate sanitizes on write, pass a sanitizer for
+    defense-in-depth or third-party HTML).
+  - A registry-drift guard test keeps the renderer map in lockstep with the
+    cms-core section registry, so no section type can ship without a renderer
+    (and vice-versa).

package/README.md

@@ -0,0 +1,36 @@
+# @actuate-media/sections-react
+
+Public React renderer for [Actuate CMS](https://github.com/actuate-media/actuatecms)
+page sections — the canonical `PageSection[]` contract — with a
+consumer-controlled renderer registry.
+
+```bash
+npm install @actuate-media/sections-react
+```
+
+## Usage
+
+```tsx
+import { SectionList, registerSectionRenderer } from '@actuate-media/sections-react'
+
+// Register renderers for your custom section types (built-ins are included)
+registerSectionRenderer('my-hero', ({ section, ctx, options }) => (
+  <MyHero {...(section.content as MyHeroContent)} />
+))
+
+// Render a resolved page
+<SectionList sections={page.sections} ctx={{ siteUrl }} />
+```
+
+The same custom types can be made editable in the admin via
+`defineSectionTypes()` + `sections.types` in `actuate.config.ts`, and rendered
+in the editor canvas via `AdminRoot`'s `sectionRenderers` prop.
+
+## Release notes
+
+See [CHANGELOG.md](./CHANGELOG.md) (shipped with the package) or the
+[GitHub releases](https://github.com/actuate-media/actuatecms/releases).
+
+## License
+
+MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@actuate-media/sections-react",
-  "version": "0.2.12",
+  "version": "0.2.14",
   "description": "Public React renderer for Actuate CMS page sections — the canonical PageSection[] contract — with a consumer-controlled renderer registry.",
   "repository": {
     "type": "git",
@@ -22,10 +22,11 @@
     }
   },
   "files": [
-    "dist"
+    "dist",
+    "CHANGELOG.md"
   ],
   "dependencies": {
-    "@actuate-media/cms-core": "0.59.1"
+    "@actuate-media/cms-core": "0.61.0"
   },
   "peerDependencies": {
     "react": ">=18.0.0"