# KRB Wellbeing Framework v5 notes

Docs checked locally from `@webflow/designer-extension-typings` installed with the Webflow page-client probe.

## Rich text

`instance-props.d.ts` defines:

```ts
interface RichTextResolvedValue {
  innerText: string;
}
```

So component instance `richText` props via `setProps()` only support text, not HTML, and not inline images. That matches what happened:

- HTML shapes were rejected.
- `{ innerText, objectType: 'Object' }` was accepted and visible.
- The inline WP image cannot be imported through this `Content/Content` component prop.

Possible routes for the rich-text image later:

1. Manual paste into Webflow rich text.
2. Change the component to expose the diagram as a separate image prop/slot.
3. Test a lower-level WHTML/element insertion workflow outside component props, but that is different from setting a component richText prop and may require unlinking/changing the component structure.

## Page links

`instance-props.d.ts` defines:

```ts
interface PageLinkResolvedValue extends LinkResolvedValueBase {
  mode: 'page';
  to?: { pageId: string };
}
```

So the correct page-link value is:

```js
{ mode: 'page', to: { pageId: '...' } }
```

v4 used `{ mode: 'page', page }`, which explains why the Designer selected page link type but did not set a page target.

v5 updates only the three Next Pages link props using the docs-backed shape.