@wix/patterns 1.468.0 → 1.470.0

package/dist/docs/ImportButton.md

@@ -4,6 +4,10 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
+Some of that scaffolding is environment-scoped and is **not** needed to use this component: `@wix/ambassador-stores-catalog-v1-product/http`, `@wix/ambassador-stores-catalog-v1-product/types`, `@wix/patterns-cms`, `@wix/yoshi-flow-bm`. Those resolve only against a Wix build environment (a Yoshi flow's runtime, a generated service client, an internal sibling package) — substitute your own data source and http client rather than installing them.
+
 ## Design
 
 ### Description
@@ -88,7 +92,7 @@ import { ImportButton } from '@wix/patterns';
 
 A Wix Data (CMS) collection. `<ImportButton />` needs no config — it reads the import inputs live from the table’s schema source, and the CMS create/edit-field modal is loaded on demand.
 
-Example code: read `dist/docs/ImportButton/cms-import.tsx`
+Example code: read `dist/examples/ImportButton/cms-import.tsx`
 
 ---
 
@@ -96,7 +100,7 @@ Example code: read `dist/docs/ImportButton/cms-import.tsx`
 
 A non–Wix-Data destination (here the stores catalog) with no declared schema: pass a `config` naming the `destination` and listing the `fields` to map onto.
 
-Example code: read `dist/docs/ImportButton/platformized-import-fields-inline.tsx`
+Example code: read `dist/examples/ImportButton/platformized-import-fields-inline.tsx`
 
 ---
 
@@ -104,7 +108,7 @@ Example code: read `dist/docs/ImportButton/platformized-import-fields-inline.tsx
 
 A non–Wix-Data destination whose fields come from a source (`usePlatformizedSource`) instead of an inline list — like the CMS case, but you still name the `destination` in `config`.
 
-Example code: read `dist/docs/ImportButton/platformized-import-from-a-source.tsx`
+Example code: read `dist/examples/ImportButton/platformized-import-from-a-source.tsx`
 
 ---
 
@@ -112,7 +116,7 @@ Example code: read `dist/docs/ImportButton/platformized-import-from-a-source.tsx
 
 Mark fields with `required: true`. The import is blocked while any required field is still unmapped, with a footnote listing the missing ones. (Shown with a platformized `config`.)
 
-Example code: read `dist/docs/ImportButton/required-fields.tsx`
+Example code: read `dist/examples/ImportButton/required-fields.tsx`
 
 ---
 
@@ -120,7 +124,7 @@ Example code: read `dist/docs/ImportButton/required-fields.tsx`
 
 A CMS capability: when the collection’s schema permits adding fields, unmapped CSV columns default to creating a new field (with an "Edit field" affordance) instead of being skipped. `<ImportButton />` wires it from the schema automatically.
 
-Example code: read `dist/docs/ImportButton/create-new-field.tsx`
+Example code: read `dist/examples/ImportButton/create-new-field.tsx`
 
 ---
 
@@ -128,7 +132,7 @@ Example code: read `dist/docs/ImportButton/create-new-field.tsx`
 
 A CMS behavior: when a CSV column maps to the collection’s id field (`_id`), that row floats to the top and the modal offers an "update or skip" write policy for rows that collide on ID.
 
-Example code: read `dist/docs/ImportButton/update-or-skip-by-id.tsx`
+Example code: read `dist/examples/ImportButton/update-or-skip-by-id.tsx`
 
 ---
 
@@ -136,7 +140,7 @@ Example code: read `dist/docs/ImportButton/update-or-skip-by-id.tsx`
 
 Pass a `backup` to snapshot the collection before importing (undone on cancel) and a `jobApplicationErrorMap` to map a failed job’s application-error codes to messages. (Shown with a platformized `config`.)
 
-Example code: read `dist/docs/ImportButton/backup-error-handling.tsx`
+Example code: read `dist/examples/ImportButton/backup-error-handling.tsx`
 
 ## API
 

package/dist/docs/InMemoryBackend.md

@@ -2,6 +2,8 @@
 
 **Category:** Guides
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Overview

package/dist/docs/Indeterminate.md

@@ -4,17 +4,21 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
+Some of that scaffolding is environment-scoped and is **not** needed to use this component: `@wix/ambassador-contacts-v4-contact/http`, `@wix/ambassador-contacts-v4-contact/types`, `@wix/fe-essentials/react`. Those resolve only against a Wix build environment (a Yoshi flow's runtime, a generated service client, an internal sibling package) — substitute your own data source and http client rather than installing them.
+
 ## Design
 
 ### Examples
 
 ### Items indeterminate status
 
-Example code: read `dist/docs/Indeterminate/items-indeterminate-status.tsx`
+Example code: read `dist/examples/Indeterminate/items-indeterminate-status.tsx`
 
 ---
 
 ### All indeterminate
 
-Example code: read `dist/docs/Indeterminate/all-indeterminate.tsx`
+Example code: read `dist/examples/Indeterminate/all-indeterminate.tsx`
 

package/dist/docs/Internal Scroll.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Internal scroll
@@ -26,13 +28,13 @@ The "internalScroll" prop enables internal scrolling within the component itself
 
 ### Full Width Section
 
-Example code: read `dist/docs/Internal Scroll/full-width-section.tsx`
+Example code: read `dist/examples/Internal Scroll/full-width-section.tsx`
 
 ---
 
 ### Narrow Side Section
 
-Example code: read `dist/docs/Internal Scroll/narrow-side-section.tsx`
+Example code: read `dist/examples/Internal Scroll/narrow-side-section.tsx`
 
 ## BI
 

package/dist/docs/More Actions.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description
@@ -27,55 +29,55 @@ import { MoreActions } from '@wix/patterns';
 
 This example displays a menu at the collection page level by passing a `MoreActions` component to the `moreActions` prop of the [`CollectionPage.Header`](./?path=/story/base-components-pages-collection-page--collectionpage-header).
 
-Example code: read `dist/docs/More Actions/collection-page.tsx`
+Example code: read `dist/examples/More Actions/collection-page.tsx`
 
 ### Collection Page
 
 With secondary actions MoreActions component will be displayed with icon only.
 
-Example code: read `dist/docs/More Actions/collection-page-2.tsx`
+Example code: read `dist/examples/More Actions/collection-page-2.tsx`
 
 ### More actions with a divider
 
 Create groups of More Action buttons with a divider between each group. Each member of a group is defined in the same array. The groups arrays are included in the `items` array.
 
-Example code: read `dist/docs/More Actions/more-actions-with-a-divider.tsx`
+Example code: read `dist/examples/More Actions/more-actions-with-a-divider.tsx`
 
 ### More actions in the toolbar
 
 More Actions can be in the toolbar. Pass the `MoreActions` component to the `moreActions` prop of Table/Grid etc.
 
-Example code: read `dist/docs/More Actions/more-actions-in-the-toolbar.tsx`
+Example code: read `dist/examples/More Actions/more-actions-in-the-toolbar.tsx`
 
 ### Explore related apps
 
 Explore related apps with the `MoreActions` component. pass the explore apps modal props and we will take care of the rest.
 
-Example code: read `dist/docs/More Actions/explore-related-apps.tsx`
+Example code: read `dist/examples/More Actions/explore-related-apps.tsx`
 
 ### Integrate with Extension
 
 Use the `containerId` prop to extend the more actions items with items from [Slots and Plugins](./?path=/story/features-enrich-slots-and-plugins--slots-and-plugins). 
 
-Example code: read `dist/docs/More Actions/integrate-with-extension.tsx`
+Example code: read `dist/examples/More Actions/integrate-with-extension.tsx`
 
 ### Featured More Actions
 
 Features like Data Extension and Tags automatically add their actions to the More Actions menu.
 
-Example code: read `dist/docs/More Actions/featured-more-actions.tsx`
+Example code: read `dist/examples/More Actions/featured-more-actions.tsx`
 
 ### Featured More Actions - Opt Out
 
 Opt out of the Featured More Actions by passing `disableDefaultPageAction` to the relevant plugin props
 
-Example code: read `dist/docs/More Actions/featured-more-actions-opt-out.tsx`
+Example code: read `dist/examples/More Actions/featured-more-actions-opt-out.tsx`
 
 ### Featured More Actions - Custom Position
 
 Customize the position of the Featured More Actions by specifying them in the `items` prop.
 
-Example code: read `dist/docs/More Actions/featured-more-actions-custom-position.tsx`
+Example code: read `dist/examples/More Actions/featured-more-actions-custom-position.tsx`
 
 ## API
 

package/dist/docs/MultiAutoInlineCheckboxFilter.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Overview

package/dist/docs/MultiBulkActionToolbar.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description
@@ -28,37 +30,37 @@ import { MultiBulkActionToolbar } from '@wix/patterns';
 
 Basic bulk action.
 
-Example code: read `dist/docs/MultiBulkActionToolbar/bulk-action.tsx`
+Example code: read `dist/examples/MultiBulkActionToolbar/bulk-action.tsx`
 
 ### Popover menu
 
 A popoever menu for the primary action.
 
-Example code: read `dist/docs/MultiBulkActionToolbar/popover-menu.tsx`
+Example code: read `dist/examples/MultiBulkActionToolbar/popover-menu.tsx`
 
 ### Basic secondary action
 
 Popoever menu for primary and secondary actions.
 
-Example code: read `dist/docs/MultiBulkActionToolbar/basic-secondary-action.tsx`
+Example code: read `dist/examples/MultiBulkActionToolbar/basic-secondary-action.tsx`
 
 ### Primary & Secondary actions with a divider
 
 Create groups of `primaryActionItems -> subItems` & `secondaryActionItems` with a divider between each group. Each member of a group is defined in the same array. The groups arrays are included in the `items` array.
 
-Example code: read `dist/docs/MultiBulkActionToolbar/primary-secondary-actions-with-a-divider.tsx`
+Example code: read `dist/examples/MultiBulkActionToolbar/primary-secondary-actions-with-a-divider.tsx`
 
 ### Maximum selection
 
 `maxSelection` sets a limit on the number of items a visitor can select.
 
-Example code: read `dist/docs/MultiBulkActionToolbar/maximum-selection.tsx`
+Example code: read `dist/examples/MultiBulkActionToolbar/maximum-selection.tsx`
 
 ### Extend menu items
 
 You can extend existing menu items using [Slots and Plugins](./?path=/story/features-enrich-slots-and-plugins--slots-and-plugins) using your own `containerId`.
 
-Example code: read `dist/docs/MultiBulkActionToolbar/extend-menu-items.tsx`
+Example code: read `dist/examples/MultiBulkActionToolbar/extend-menu-items.tsx`
 
 ## API
 

package/dist/docs/MultiInlineCheckboxFilter.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Overview

package/dist/docs/MultiLevelSorting.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description
@@ -24,19 +26,19 @@ import { MultiLevelSorting } from '@wix/patterns';
 
 Apply sorting to multiple columns using the `<Table>` `multiLevelSorting` prop.
 
-Example code: read `dist/docs/MultiLevelSorting/basic-multi-level-sorting.tsx`
+Example code: read `dist/examples/MultiLevelSorting/basic-multi-level-sorting.tsx`
 
 ### Multi Level Sorting with defined sort directions
 
 Use the `defaultSortDirection` property in each columns object in the `columns` array to define the direction of the sort for that column.
 
-Example code: read `dist/docs/MultiLevelSorting/multi-level-sorting-with-defined-sort-directions.tsx`
+Example code: read `dist/examples/MultiLevelSorting/multi-level-sorting-with-defined-sort-directions.tsx`
 
 ### Multi Level Sorting with custom sort order
 
 Use the `sortMode` property in each columns object in the `columns` array to define the order of the sort options for that column.
 
-Example code: read `dist/docs/MultiLevelSorting/multi-level-sorting-with-custom-sort-order.tsx`
+Example code: read `dist/examples/MultiLevelSorting/multi-level-sorting-with-custom-sort-order.tsx`
 
 ## API
 

package/dist/docs/MultiSelectCheckboxFilter.md

@@ -4,6 +4,10 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
+Some of that scaffolding is environment-scoped and is **not** needed to use this component: `@wix/yoshi-flow-bm`. Those resolve only against a Wix build environment (a Yoshi flow's runtime, a generated service client, an internal sibling package) — substitute your own data source and http client rather than installing them.
+
 ## Design
 
 ### Overview

package/dist/docs/MultiSelectCollectionFilter.md

@@ -4,6 +4,10 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
+Some of that scaffolding is environment-scoped and is **not** needed to use this component: `@wix/yoshi-flow-bm`. Those resolve only against a Wix build environment (a Yoshi flow's runtime, a generated service client, an internal sibling package) — substitute your own data source and http client rather than installing them.
+
 ## Design
 
 ### Overview

package/dist/docs/NestedTable.md

@@ -4,6 +4,10 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
+Some of that scaffolding is environment-scoped and is **not** needed to use this component: `@wix/ambassador-contacts-v4-contact/http`, `@wix/ambassador-contacts-v4-contact/types`, `@wix/yoshi-flow-bm`. Those resolve only against a Wix build environment (a Yoshi flow's runtime, a generated service client, an internal sibling package) — substitute your own data source and http client rather than installing them.
+
 ## Design
 
 ```tsx
@@ -227,25 +231,25 @@ useNestedTable({
 
 All levels are of the same entity type / query endpoint
 
-Example code: read `dist/docs/NestedTable/single-entity.tsx`
+Example code: read `dist/examples/NestedTable/single-entity.tsx`
 
 ### Various Entities
 
 Each level is of a different entity type / query endpoint
 
-Example code: read `dist/docs/NestedTable/various-entities.tsx`
+Example code: read `dist/examples/NestedTable/various-entities.tsx`
 
 ### Flat Mode (Search)
 
 Table is in flat mode when search is active. Items are not grouped by level. Items shown with breadcrumbs when provided in the level config. `fetchData` will be called with `query.fields` that contains the value `breadcrumbs` to signal that the breadcrumbs should be fetched.
 
-Example code: read `dist/docs/NestedTable/flat-mode-search.tsx`
+Example code: read `dist/examples/NestedTable/flat-mode-search.tsx`
 
 ### Filters
 
 A client-side example of using filters on nested table (ignore the fetchData implementation that should be use a real API on a real project)
 
-Example code: read `dist/docs/NestedTable/filters.tsx`
+Example code: read `dist/examples/NestedTable/filters.tsx`
 
 ---
 
@@ -255,11 +259,11 @@ Example code: read `dist/docs/NestedTable/filters.tsx`
 
 Accessing node by id and all its descendants
 
-Example code: read `dist/docs/NestedTable/node-api-usage.tsx`
+Example code: read `dist/examples/NestedTable/node-api-usage.tsx`
 
 ### Drag and Drop
 
-Example code: read `dist/docs/NestedTable/drag-and-drop.tsx`
+Example code: read `dist/examples/NestedTable/drag-and-drop.tsx`
 
 ## API
 

package/dist/docs/NumberRangeFilter.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Overview

package/dist/docs/OperatorFilterPicker.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Overview

package/dist/docs/PageWrapper.md

@@ -2,6 +2,8 @@
 
 **Category:** Base Components/Pages/Custom/PageWrapper
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description

package/dist/docs/PatternsReactRoute.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description

package/dist/docs/PatternsReactRouter.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description

package/dist/docs/PickerContent.md

@@ -2,6 +2,8 @@
 
 **Category:** Base Components/Collections/Picker
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## API
 
 ### Overview

package/dist/docs/PickerModal.md

@@ -4,6 +4,10 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
+Some of that scaffolding is environment-scoped and is **not** needed to use this component: `@wix/ambassador-contacts-v4-contact/http`, `@wix/ambassador-contacts-v4-contact/types`, `@wix/fe-essentials/react`. Those resolve only against a Wix build environment (a Yoshi flow's runtime, a generated service client, an internal sibling package) — substitute your own data source and http client rather than installing them.
+
 ## Design
 
 ### Description
@@ -21,7 +25,7 @@ import { PickerModal } from '@wix/patterns';
 
 ### Multi Select
 
-Example code: read `dist/docs/PickerModal/multi-select.tsx`
+Example code: read `dist/examples/PickerModal/multi-select.tsx`
 
 ---
 
@@ -29,7 +33,7 @@ Example code: read `dist/docs/PickerModal/multi-select.tsx`
 
  Radio button selection, the user can select one item only
 
-Example code: read `dist/docs/PickerModal/single-selection.tsx`
+Example code: read `dist/examples/PickerModal/single-selection.tsx`
 
 ---
 
@@ -37,7 +41,7 @@ Example code: read `dist/docs/PickerModal/single-selection.tsx`
 
  When the user opens the modal some of the items are already selected
 
-Example code: read `dist/docs/PickerModal/pre-selected-item.tsx`
+Example code: read `dist/examples/PickerModal/pre-selected-item.tsx`
 
 ---
 
@@ -45,7 +49,7 @@ Example code: read `dist/docs/PickerModal/pre-selected-item.tsx`
 
 You can add a `SingleSelectFilter` to your Picker Modal to filter its contents. To have it you need to pass `SingleSelectFilter` to the `filterComponent` prop in `PickerContent` and define the filter behavior when creating a state (check out `usePickerContent` and `usePickerModal`) in the example.
 
-Example code: read `dist/docs/PickerModal/with-filter-dropdown.tsx`
+Example code: read `dist/examples/PickerModal/with-filter-dropdown.tsx`
 
 ---
 
@@ -53,7 +57,7 @@ Example code: read `dist/docs/PickerModal/with-filter-dropdown.tsx`
 
 You can override the search behavior using the `search` prop. Pass `false` to hide search, or a custom `<CollectionSearch />`
 
-Example code: read `dist/docs/PickerModal/search-override.tsx`
+Example code: read `dist/examples/PickerModal/search-override.tsx`
 
 ## API
 

package/dist/docs/PickerStandalone.md

@@ -4,6 +4,10 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
+Some of that scaffolding is environment-scoped and is **not** needed to use this component: `@wix/ambassador-contacts-v4-contact/http`, `@wix/ambassador-contacts-v4-contact/types`, `@wix/fe-essentials/react`. Those resolve only against a Wix build environment (a Yoshi flow's runtime, a generated service client, an internal sibling package) — substitute your own data source and http client rather than installing them.
+
 ## Import
 
 ```tsx
@@ -33,25 +37,25 @@ import { PickerStandalone } from '@wix/patterns';
 
 ### Basic
 
-Example code: read `dist/docs/PickerStandalone/basic.tsx`
+Example code: read `dist/examples/PickerStandalone/basic.tsx`
 
 ---
 
 ### Custom Empty State
 
-Example code: read `dist/docs/PickerStandalone/custom-empty-state.tsx`
+Example code: read `dist/examples/PickerStandalone/custom-empty-state.tsx`
 
 ---
 
 ### Custom Items
 
-Example code: read `dist/docs/PickerStandalone/custom-items.tsx`
+Example code: read `dist/examples/PickerStandalone/custom-items.tsx`
 
 ---
 
 ### CreateNew
 
-Example code: read `dist/docs/PickerStandalone/createnew.tsx`
+Example code: read `dist/examples/PickerStandalone/createnew.tsx`
 
 ## API
 

package/dist/docs/PrimaryActionButton.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description

package/dist/docs/PrimaryActions.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description

package/dist/docs/PrimaryPageButton.md

@@ -6,6 +6,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Description

package/dist/docs/RadioGroupFilter.md

@@ -4,6 +4,8 @@
 
 Paths written as `dist/…` below are relative to the `@wix/patterns` package root — the directory holding its `package.json`.
 
+Examples below are illustrative: each one demonstrates this page's API, and everything around it — data source, layout, http client — is only scaffolding to make that runnable.
+
 ## Design
 
 ### Overview