@wix/patterns 1.477.0 → 1.479.0

package/dist/docs/EntityPage.Header.md

@@ -78,7 +78,7 @@ function Basic() {
 
 ### More Actions
 
-This example displays a header with more actions CTA. To learn how to create a more actions menu, see [`MoreActions`](./?path=/story/features-actions-more-actions--more-actions).
+This example displays a header with more actions CTA. To learn how to create a more actions menu, see [`MoreActions`](<More Actions.md>).
 
 ```tsx
 import React from 'react';
@@ -236,7 +236,7 @@ function Badges() {
 
 ### Overview
 
-The header component for an [`EntityPage`](./?path=/story/base-components-pages-entity-page--entitypage). Renders the page title, optional subtitle, breadcrumbs, badges, and a more-actions menu. Place it as a direct child of `<EntityPage>`.
+The header component for an [`EntityPage`](EntityPage.md). Renders the page title, optional subtitle, breadcrumbs, badges, and a more-actions menu. Place it as a direct child of `<EntityPage>`.
 
 ```tsx
 import { EntityPage } from '@wix/patterns';

package/dist/docs/EntityPage.MainContent.md

@@ -8,7 +8,7 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 ### Overview
 
-A slot component for the main content area of an [`EntityPage`](./?path=/story/base-components-pages-entity-page--entitypage). Place it inside `<EntityPage.Content>`. This is where you render the primary form fields and cards.
+A slot component for the main content area of an [`EntityPage`](EntityPage.md). Place it inside `<EntityPage.Content>`. This is where you render the primary form fields and cards.
 
 ```tsx
 import { EntityPage } from '@wix/patterns';
@@ -16,7 +16,7 @@ import { EntityPage } from '@wix/patterns';
 
 ### Usage
 
-This component acts as a container for [EntityPage.Card](./?path=/story/base-components-pages-entity-page--entitypage-card) child components and is displayed on the left side of the Page layout. For examples of how this component is used, please refer to the [EntityPage](./?path=/story/base-components-pages-entity-page--entitypage&tab=Examples) examples.
+This component acts as a container for [EntityPage.Card](EntityPage.Card.md) child components and is displayed on the left side of the Page layout. For examples of how this component is used, please refer to the [EntityPage](EntityPage.md) examples.
 
 ### Props
 

package/dist/docs/EntityPage.Slots.md

@@ -62,7 +62,7 @@ function Basic() {
 
 ### Overview
 
-A slot container for rendering TPA plugin widgets inside an [`EntityPage`](./?path=/story/base-components-pages-entity-page--entitypage). Pass a `containerId` from your Dev Center app to render third-party plugins in the entity page layout. Learn more about [Slots and Plugins](./?path=/story/features-enrich-slots-and-plugins--slots-and-plugins).
+A slot container for rendering TPA plugin widgets inside an [`EntityPage`](EntityPage.md). Pass a `containerId` from your Dev Center app to render third-party plugins in the entity page layout. Learn more about [Slots and Plugins](./?path=/story/features-enrich-slots-and-plugins--slots-and-plugins).
 
 ```tsx
 import { EntityPage } from '@wix/patterns';

package/dist/docs/EntityPage.md

@@ -16,13 +16,13 @@ Here's a breakdown of its main purposes:
 
 1. **Appearance of the Entity Page**: The `EntityPage` component handles the overall layout and structure of the entity page. It defines how the page is organized, including title and subtitle, more actions dropdown, CTAs, content basic layout and widgets. Also, it is responsible for rendering loading skeletons, error state, displaying notifications and other.
 
-2. **Handling Fetch**: The `EntityPage` component typically integrates with a fetch mechanism (e.g., an API call) to retrieve data related to the entity being displayed on the page. This integration is done through the `fetch` function passed as a prop to the [`useEntityPage`](./?path=/story/base-components-pages-entity-page-hooks-useentitypage--useentitypage) hook, allowing the component to retrieve the necessary data for rendering. You can use the [`useEntity`](./?path=/story/base-components-pages-entity-page-hooks-useentity--useentity)  to access a fetched entity.
+2. **Handling Fetch**: The `EntityPage` component typically integrates with a fetch mechanism (e.g., an API call) to retrieve data related to the entity being displayed on the page. This integration is done through the `fetch` function passed as a prop to the [`useEntityPage`](useEntityPage.md) hook, allowing the component to retrieve the necessary data for rendering. You can use the [`useEntity`](useEntity.md)  to access a fetched entity.
 
-3. **Handling Save and Validation Logic**: The [useForm](https://react-hook-form.com/docs/useform)  hook from [react-hook-form](https://react-hook-form.com/) is used to create a form object, and the `onSave` function passed as a prop to the [`useEntityPage`](./?path=/story/components-page-entitypage-hooks-useentitypage--useentitypage) hook, is triggered when the user initiates a save action.
+3. **Handling Save and Validation Logic**: The [useForm](https://react-hook-form.com/docs/useform)  hook from [react-hook-form](https://react-hook-form.com/) is used to create a form object, and the `onSave` function passed as a prop to the [`useEntityPage`](useEntityPage.md) hook, is triggered when the user initiates a save action.
 
-4. **Easy integration with open platform capabilities**: Create a container in Dev Center, and Wix Patterns will automatically fetch and display the relevant plugins. Pass your `componentId` to the `componentId` prop of `EntityPage.Slots` to add widgets to an entity page, or to the `componentId` prop of [`MoreActions`](./?path=/story/features-actions-more-actions--moreactions) to extend the "More Actions" menu with extra items.
+4. **Easy integration with open platform capabilities**: Create a container in Dev Center, and Wix Patterns will automatically fetch and display the relevant plugins. Pass your `componentId` to the `componentId` prop of `EntityPage.Slots` to add widgets to an entity page, or to the `componentId` prop of [`MoreActions`](<More Actions.md>) to extend the "More Actions" menu with extra items.
 
-In summary, the ``EntityPage`` component and the associated [`useEntityPage`](./?path=/story/base-components-pages-entity-page-hooks-useentitypage--useentitypage) hook together provide a streamlined approach to rendering, fetching, saving, and validating data for a specific entity within an application.
+In summary, the ``EntityPage`` component and the associated [`useEntityPage`](useEntityPage.md) hook together provide a streamlined approach to rendering, fetching, saving, and validating data for a specific entity within an application.
 
 
 ---
@@ -31,15 +31,15 @@ In summary, the ``EntityPage`` component and the associated [`useEntityPage`](./
 
 This comprehensive demo demonstrates all the key functionalities supported by `EntityPage`:
 
-- Page designed with 2 sections: the main content using the [EntityPage.MainContent](./?path=/story/base-components-pages-entity-page--entitypage-maincontent) component and the additional content using the [EntityPage.AdditionalContent](./?path=/story/base-components-pages-entity-page--entitypage-additionalcontent) component.
+- Page designed with 2 sections: the main content using the [EntityPage.MainContent](EntityPage.MainContent.md) component and the additional content using the [EntityPage.AdditionalContent](EntityPage.AdditionalContent.md) component.
 
-- [MoreActions](./?path=/story/base-components-pages-entity-page--entitypage-header#More_Actions), offering a more actions menu with inline actions and additional actions that are extended using `containerId`, alongside [EntityPage.Slots](./?path=/story/base-components-pages-entity-page--entitypage-slots) which enable the broadening of your UI with a variety of Cards.
+- [MoreActions](EntityPage.Header.md), offering a more actions menu with inline actions and additional actions that are extended using `containerId`, alongside [EntityPage.Slots](EntityPage.Slots.md) which enable the broadening of your UI with a variety of Cards.
 
-- Integration with current widgets such as [CustomFieldsWidget](./?path=/story/base-components-pages-entity-page--entitypage-customfieldswidget) and [TagsWidget](./?path=/story/base-components-pages-entity-page--entitypage-tagswidget), linked to the page's state, enables their use in conjunction with the page's isDirty state.
+- Integration with current widgets such as [CustomFieldsWidget](CustomFieldsWidget.md) and [TagsWidget](TagsWidget.md), linked to the page's state, enables their use in conjunction with the page's isDirty state.
 
 - A save and validation process that ensures required fields are filled.
 
-Explore the [Examples](./?path=/story/components-page-entitypage--entitypage&tab=Examples) section for a clearer understanding of the various states of the entity state, and examine each sub-component to see their available states and examples.
+Explore the [Examples](EntityPage.md) section for a clearer understanding of the various states of the entity state, and examine each sub-component to see their available states and examples.
 
 
 Example code: read `dist/examples/EntityPage/demo.tsx`

package/dist/docs/EntityPageState.md

@@ -10,7 +10,7 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 ### Overview
 
-`EntityPageState` is the state object that drives an [`EntityPage`](./?path=/story/base-components-pages-entity-page--entitypage). It is created by the [`useEntityPage`](./?path=/story/base-components-pages-entity-page-hooks-useentitypage--useentitypage) hook and manages:
+`EntityPageState` is the state object that drives an [`EntityPage`](EntityPage.md). It is created by the [`useEntityPage`](useEntityPage.md) hook and manages:
 
 - **Entity fetching** — loads the entity from the server via `fetch`
 - **Form state** — integrates with `react-hook-form` for editing
@@ -18,7 +18,7 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 - **Dirty-form protection** — warns on `beforeunload` when the form has unsaved changes
 - **Navigation** — supports both Patterns Router (`parentPath`) and legacy BM navigation (`parentPageId`)
 
-Pass the returned state to `<EntityPage state={state}>` and use [`useEntity`](./?path=/story/base-components-pages-entity-page-hooks-useentity--useentity) to read the entity reactively.
+Pass the returned state to `<EntityPage state={state}>` and use [`useEntity`](useEntity.md) to read the entity reactively.
 
 ```tsx
 import { useEntityPage } from '@wix/patterns';

package/dist/docs/Explore Apps.md

@@ -174,7 +174,7 @@ function ExploreApps() {
 
 | Prop | Type | Required | Default | Description |
 |------|------|----------|---------|-------------|
-| `items` | `MoreActionsPropItem[] \| MoreActionsPropItem[][]` | No | - | Actions items that appear in the `MoreActions` popover menu. \ Actions can be grouped by using an array of arrays. \ Each sub-array represents a different group within the popover, \ and a divider will be rendered after each sub-array to separate the groups. \| [MoreActionsItem](./?path=/story/common-types--moreactionsitem)[][] |
+| `items` | `MoreActionsPropItem[] \| MoreActionsPropItem[][]` | No | - | Actions items that appear in the `MoreActions` popover menu. \ Actions can be grouped by using an array of arrays. \ Each sub-array represents a different group within the popover, \ and a divider will be rendered after each sub-array to separate the groups. \| [MoreActionsItem](MoreActionsItem.md)[][] |
 | `containerId` | `string` | No | - | An id of the container defined in the installed on a site application that contains TPA's actions. |
 | `containerProps` | `Record<string, any>` | No | - | Additional properties passed to the `onClick` of the container's extensions menu items. |
 | `biAdditionalInfo` | `string` | No | - | Additional info for cairoPageCtaClicked BI event. |

package/dist/docs/ExportTo.md

@@ -209,13 +209,13 @@ Event   |   Description   |
 
 ### Usage
 
-`getExportButton` API is exposed from the `<Table />` [testkit](./?path=/story/components-collection--table&activeTab=Testkit)
+`getExportButton` API is exposed from the `<Table />` [testkit](Table.md)
 
 ### Export `HttpClient` Mocks
 
 #### BM Flow
 
-When using `Flow BM` testkit, use the [wixPatternsTestProviderPropsOverrides](./?path=/story/testing-component-tests--component-tests#TableTestDriver.ts) Wix Patterns helper for injecting all relevant mocks.
+When using `Flow BM` testkit, use the [wixPatternsTestProviderPropsOverrides](<Component Tests.md>) Wix Patterns helper for injecting all relevant mocks.
 
 #### Manually
 

package/dist/docs/Filter Overview.md

@@ -10,11 +10,11 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 ### Overview
 
-To better understand the use and configuration of filters in Wix Patterns and especially in [Tabs Filter](./?path=/story/features-filter-components--tabsfilter), [Toolbar Filters](./?path=/story/features-filter-components--toolbarfilters) and [Views](./?path=/story/features-display-views--views) it is important to know the difference between the [Filter Components](./?path=/story/features-filter-components) and the `Filter` object including all the built-in factories Wix Patterns provides.
+To better understand the use and configuration of filters in Wix Patterns and especially in [Tabs Filter](TabsFilter.md), [Toolbar Filters](ToolbarFilters.md) and [Views](Views.md) it is important to know the difference between the Filter Components and the `Filter` object including all the built-in factories Wix Patterns provides.
 
 The filter components as the name suggests are just wrappers over [@wix/design-system](https://www.docs.wixdesignsystem.com/?path=/story/getting-started--about) components to handle the filter object, whereas the filter object is a data structure that stores the current state of the filter that being used.
 
-Looking to add filters to Data Extensions? [Learn more](./?path=/story/features-enrich-data-extension--data-extension#Filters_&_Sorting).
+Looking to add filters to Data Extensions? [Learn more](<Data Extension Overview.md>).
 
 
 ### Filter Factories
@@ -23,32 +23,32 @@ There are several different factories that can be divided into two main categori
 
 Common:
 
-- [stringsArrayFilter](./?path=/story/features-filter-factories--stringsarrayfilter) - plain strings selection
-- [idNameArrayFilter](./?path=/story/features-filter-factories--idnamearrayfilter) - object selection
-- [stringFilter](./?path=/story/features-filter-factories--stringfilter) - single string selection
-- [dateRangeFilter](./?path=/story/features-filter-factories--daterangefilter) - specifically for [DateRangeFilter](./?path=/story/common-filters--daterangefilter) component
+- [stringsArrayFilter](stringsArrayFilter.md) - plain strings selection
+- [idNameArrayFilter](idNameArrayFilter.md) - object selection
+- [stringFilter](stringFilter.md) - single string selection
+- [dateRangeFilter](dateRangeFilter.Factories.md) - specifically for [DateRangeFilter](DateRangeFilter.Components.md) component
 
 Uncommon:
 
-- [arrayFilter](./?path=/story/features-filter-factories--arrayfilter)
+- [arrayFilter](arrayFilter.md)
 - idArrayFilter
 - rangeFilter
 - idNameArrayFilterNum
-- [customFilter](./?path=/story/features-filter-factories--customfilter)
+- [customFilter](customFilter.md)
 
 
 ### Filter Components
 
 Wix Patterns offers a variety of plug & play components for filters, including auto-complete date ranges and more. Here are all the filter components that Wix Patterns provides out-of-the-box:
 
-- [MultiInlineCheckboxFilter](./?path=/story/features-filter-components--multiinlinecheckboxfilter)
-- [MultiSelectCheckboxFilter](./?path=/story/features-filter-components--multiselectcheckboxfilter)
-- [MultiSelectCollectionFilter](./?path=/story/features-filter-components--multiselectcollectionfilter)
-- [SingleSelectFilter](./?path=/story/features-filter-components--singleselectfilter)
-- [AutoCompleteFilter](./?path=/story/features-filter-components--autocompletefilter)
-- [DateRangeFilter](./?path=/story/features-filter-components--daterangefilter)
-- [MultiAutoInlineCheckboxFilter](./?path=/story/features-filter-components--multiautoinlinecheckboxfilter)
-- [RadioGroupFilter](./?path=/story/features-filter-components--radiogroupfilter)
+- [MultiInlineCheckboxFilter](MultiInlineCheckboxFilter.md)
+- [MultiSelectCheckboxFilter](MultiSelectCheckboxFilter.md)
+- [MultiSelectCollectionFilter](MultiSelectCollectionFilter.md)
+- [SingleSelectFilter](SingleSelectFilter.md)
+- [AutoCompleteFilter](AutoCompleteFilter.md)
+- [DateRangeFilter](DateRangeFilter.Components.md)
+- [MultiAutoInlineCheckboxFilter](MultiAutoInlineCheckboxFilter.md)
+- [RadioGroupFilter](RadioGroupFilter.md)
 
 The choice of which component to use depends on the desired user experience. Most of the components can be connected with a variety of filters, so the choice is ultimately up to you.
 
@@ -83,7 +83,7 @@ Here is the JIRA ticket with the details:
 >
 > Thanks a lot  Joe, Product Manager@Contacts
 
-In this example, we will only be discussing filters. If you need information on creating an initial Wix Patterns table, please refer to the [Table](./?path=/story/base-components-collections-table-table--table) documentation. You have one final opportunity to get some coffee before we begin implementing the ticket ;) Ready? good! Let's go step by step and analyze what Joe asked us to do and which component and filter types will be the most suitable for the job.
+In this example, we will only be discussing filters. If you need information on creating an initial Wix Patterns table, please refer to the [Table](Table.md) documentation. You have one final opportunity to get some coffee before we begin implementing the ticket ;) Ready? good! Let's go step by step and analyze what Joe asked us to do and which component and filter types will be the most suitable for the job.
 
 ##### Contact Level
 
@@ -113,7 +113,7 @@ const levelsCollection = useStaticListFilterCollection(filter, [
 
 ![image](https://user-images.githubusercontent.com/32840800/209715656-7737593c-b98f-4bc8-a9bb-4325f04ee603.png)
 
-This is the most basic example for using [stringsArrayFilter](./?path=/story/features-filter-factories--stringsarrayfilter) and [MultiSelectCheckboxFilter](./?path=/story/features-filter-components--multiselectcheckboxfilter)
+This is the most basic example for using [stringsArrayFilter](stringsArrayFilter.md) and [MultiSelectCheckboxFilter](MultiSelectCheckboxFilter.md)
 
 ```tsx
 const [filter] = React.useState(() => stringsArrayFilter());
@@ -139,7 +139,7 @@ const collection = useFilterCollection(filter, {
 ```
 ##### Last Seen
 
-One option for filtering a date range is to use the [DateRangeFilter](./?path=/story/features-filter-components--daterangefilter) component with [dateRangeFilter](./?path=/story/features-filter-factories--daterangefilter) provided by Wix Patterns. This duo can simplify the process of creating options for filtering a date range. However, it is also possible to create the options manually using a more basic filter like [idNameArrayFilter](./?path=/story/features-filter-factories--idnamearrayfilter) if you really want to.
+One option for filtering a date range is to use the [DateRangeFilter](DateRangeFilter.Components.md) component with [dateRangeFilter](dateRangeFilter.Factories.md) provided by Wix Patterns. This duo can simplify the process of creating options for filtering a date range. However, it is also possible to create the options manually using a more basic filter like [idNameArrayFilter](idNameArrayFilter.md) if you really want to.
 
 ```js
 const [filter] = React.useState(() => dateRangeFilter());
@@ -151,7 +151,7 @@ const [filter] = React.useState(() => dateRangeFilter());
 
 ##### Subscription Status
 
-The subscription status is a simple enum in server but while showing the possible options for the user we cannot use the values as-is, certainly for other languages. To handle this we will use [idNameArrayFilter](./?path=/story/features-filter-factories--idnamearrayfilter), the most common filter factory we have.
+The subscription status is a simple enum in server but while showing the possible options for the user we cannot use the values as-is, certainly for other languages. To handle this we will use [idNameArrayFilter](idNameArrayFilter.md), the most common filter factory we have.
 
 ```js
 import React from 'react';
@@ -177,7 +177,7 @@ const subscriptionStatusCollection = useStaticListFilterCollection(filter, [
 
 At first, this example may appear straightforward but how does the dropdown menu determine the value of each option? In addition, if the contact has a boolean indication for subscription status rather than an enum, assigning the `id` to a boolean value could potentially be problematic (`[{id: true, name: 'Subscribed'}, {id: false, name: 'Unsubscribed'}]`).
 
-The [idNameArrayFilter](./?path=/story/features-filter-factories--idnamearrayfilter) filter expects `id` and `name` while `name` is basically the value of the filter. That is why we are able to see the options values without having to explicitly implement them. We could achieve the same result by using the `renderItem` property:
+The [idNameArrayFilter](idNameArrayFilter.md) filter expects `id` and `name` while `name` is basically the value of the filter. That is why we are able to see the options values without having to explicitly implement them. We could achieve the same result by using the `renderItem` property:
 
 ```js
 import React from 'react';
@@ -235,7 +235,7 @@ const fetchData = (query: OffsetQuery<ContactsFilters>) => {
 
 ##### Search
 
-The search parameter is not technically part of the filters panel, but it can be initialized using [stringFilter](./?path=/story/features-filter-factories--stringfilter). This filter is usually opt-in by default, but if you want to pass an initial value for the search input, you can do so by passing your own filter to it.
+The search parameter is not technically part of the filters panel, but it can be initialized using [stringFilter](stringFilter.md). This filter is usually opt-in by default, but if you want to pass an initial value for the search input, you can do so by passing your own filter to it.
 
 ```js
 const collection = useCollection<Contact, ContactsFilters>({
@@ -245,7 +245,7 @@ const collection = useCollection<Contact, ContactsFilters>({
 })
 ```
 
-Using the knowledge we gained from going through the necessary filters, let's apply it to the [Tabs Filter]() feature to create a Wix Patterns [`Table`](./?path=/story/base-components-collections-table-table--table) that includes a filters button featuring all of the previously mentioned filters.
+Using the knowledge we gained from going through the necessary filters, let's apply it to the [Tabs Filter]() feature to create a Wix Patterns [`Table`](Table.md) that includes a filters button featuring all of the previously mentioned filters.
 
 
 

package/dist/docs/FilterProps.md

@@ -8,7 +8,7 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 ### Overview
 
-The base filter component interface used by all filter types in Wix Patterns. Each filter defines how it renders in the toolbar, its value type, and how it maps to query parameters. See specific filter implementations like [`SingleSelectFilter`](./?path=/story/features-filter-components--singleselectfilter), [`MultiSelectCheckboxFilter`](./?path=/story/features-filter-components--multiselectcheckboxfilter), and [`DateRangeFilter`](./?path=/story/features-filter-components--daterangefilter).
+The base filter component interface used by all filter types in Wix Patterns. Each filter defines how it renders in the toolbar, its value type, and how it maps to query parameters. See specific filter implementations like [`SingleSelectFilter`](SingleSelectFilter.md), [`MultiSelectCheckboxFilter`](MultiSelectCheckboxFilter.md), and [`DateRangeFilter`](DateRangeFilter.Components.md).
 
 ### Props
 

package/dist/docs/FormPageState.md

@@ -6,7 +6,7 @@
 
 ### Overview
 
-`FormPageState` manages form state for page components (`EntityPage`, `SettingsPage`). It wraps a `react-hook-form` `UseFormReturn` instance and adds initialization/submission task tracking and optional widgets form state. You typically do not create this directly — it is managed internally by [`EntityPageState`](./?path=/story/base-components-pages-entity-page-state--entitypagestate) or [`SettingsPageState`](./?path=/story/base-components-pages-settings-page-state--settingspagestate).
+`FormPageState` manages form state for page components (`EntityPage`, `SettingsPage`). It wraps a `react-hook-form` `UseFormReturn` instance and adds initialization/submission task tracking and optional widgets form state. You typically do not create this directly — it is managed internally by [`EntityPageState`](EntityPageState.md) or [`SettingsPageState`](SettingsPageState.md).
 
 ### Props
 

package/dist/docs/Grid Sections.md

@@ -8,13 +8,13 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 ### Description
 
-Group [`Grid`](./?path=/story/base-components-collections-grid-grid--grid) data into sections.
+Group [`Grid`](Grid.md) data into sections.
 
 #### Usage
 
-1. Create a [`Grid`](./?path=/story/base-components-collections-grid-grid--grid) collection component.
-1. In the `fetchData` function of the [`useGridCollection()`](./?path=/story/base-components-collections-grid-usegridcollection--usegridcollection) hook, return data grouped by the desired field for creating sections. You can use `sort` for this, or simply return the data grouped by the field in a flat array. Patterns detects this field and sections the grid data by its values.
-1. Define the `sections` prop on the `Grid`. The prop must be a [`GridSectionsProp`](./?path=/story/common-types--gridsectionsprop) object, where the `renderSection` callback returns a [`Section`](./?path=/story/common-types--collectionsection) object with `id`, `title`, and optional `primaryAction` properties.
+1. Create a [`Grid`](Grid.md) collection component.
+1. In the `fetchData` function of the [`useGridCollection()`](useGridCollection.md) hook, return data grouped by the desired field for creating sections. You can use `sort` for this, or simply return the data grouped by the field in a flat array. Patterns detects this field and sections the grid data by its values.
+1. Define the `sections` prop on the `Grid`. The prop must be a [`GridSectionsProp`](GridSectionsProp.md) object, where the `renderSection` callback returns a [`Section`](CollectionSection.md) object with `id`, `title`, and optional `primaryAction` properties.
 
 
 ```tsx

package/dist/docs/Grid.md

@@ -14,9 +14,9 @@ The `Grid` component displays cards in rows and columns as an alternative to tab
 
 #### Usage
 
-1. Wrap your code in a `WixDesignSystemProvider` followed by a [`WixPatternsProvider`](./?path=/story/base-components-providers--wixpatternsprovider).
-1. Wrap `Grid` in a [`CollectionPage`](./?path=/story/base-components-pages-collection-page--collectionpage).
-1. Create a [`GridState`](./?path=/story/base-components-collections-grid-gridstate--gridstate) using [`useGridCollection()`](./?path=/story/base-components-collections-grid-usegridcollection--usegridcollection).
+1. Wrap your code in a `WixDesignSystemProvider` followed by a [`WixPatternsProvider`](WixPatternsProvider.md).
+1. Wrap `Grid` in a [`CollectionPage`](CollectionPage.md).
+1. Create a [`GridState`](GridState.md) using [`useGridCollection()`](useGridCollection.md).
 1. Pass the `GridState` to the `state` prop.
 
 
@@ -71,7 +71,7 @@ Example code: read `dist/examples/Grid/use-the-preset-prop.tsx`
 
 ### Grid sections
 
-This example fetches sorted collection data by `jobTitle` and then groups the grid into sections based on `jobTitle`.         For more information, see [Grid Sections](./?path=/story/features-display-grid-sections--grid-sections).
+This example fetches sorted collection data by `jobTitle` and then groups the grid into sections based on `jobTitle`.         For more information, see [Grid Sections](<Grid Sections.md>).
 
 Example code: read `dist/examples/Grid/grid-sections.tsx`
 

package/dist/docs/GridDragAndDrop.md

@@ -8,13 +8,13 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 ### Description
 
-Enables [drag and drop](./?path=/story/features-sort-drag-and-drop--overview) functionality on a [`Grid`](./?path=/story/base-components-collections-grid-grid--grid) component.
+Enables [drag and drop](./?path=/story/features-sort-drag-and-drop--overview) functionality on a [`Grid`](Grid.md) component.
 
 #### Usage
 
-1. Define a [`Grid`](./?path=/story/base-components-collections-grid-grid--grid) component.
+1. Define a [`Grid`](Grid.md) component.
 1. Import and pass the `GridDragAndDrop` component to the `dragAndDrop` prop on the `Grid`.
-1. Define the relevant drag and drop props on the [`Grid`](./?path=/story/base-components-collections-grid-grid--grid&tab=API):
+1. Define the relevant drag and drop props on the [`Grid`](Grid.md):
 
       * `dragAndDropSubmit`
       * `dragAndDropCancel` (optional)

package/dist/docs/GridFolders.md

@@ -12,7 +12,7 @@ Some of that scaffolding is environment-scoped and is **not** needed to use this
 
 ### Description
 
-The `GridFolders` component presents folders and their respective content in a visually organized grid view, where each part is neatly divided into its own dedicated section. The [`useGridFolders()`](./?path=/story/base-components-collections-gridfolders-usegridfolders--usegridfolders) hook manages the state and behavior of the grid component based on the provided collections.
+The `GridFolders` component presents folders and their respective content in a visually organized grid view, where each part is neatly divided into its own dedicated section. The [`useGridFolders()`](useGridFolders.md) hook manages the state and behavior of the grid component based on the provided collections.
 
 
 ```tsx

package/dist/docs/GridFoldersSection.md

@@ -10,7 +10,7 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 `GridFoldersSection` renders a section within a `GridFolders` layout — either the folders section or the items section. Each section can include an optional `header` (e.g. a section title) and accepts `children` for the grid content.
 
-This component is typically used in conjunction with [`GridFolders`](./?path=/story/base-components-collections-gridfolders--gridfolders) and [`useGridCollection`](./?path=/story/common-hooks--usegridcollection).
+This component is typically used in conjunction with [`GridFolders`](GridFolders.md) and [`useGridCollection`](useGridCollection.md).
 
 ```tsx
 import { GridFolders } from '@wix/patterns';

package/dist/docs/GridFoldersState.md

@@ -8,11 +8,11 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 ### Overview
 
-`GridFoldersState` manages the state for a [`GridFolders`](./?path=/story/base-components-collections-gridfolders--gridfolders) component, which displays both folders and items in a grid layout. It holds separate `CollectionState` instances for folders and items, plus a shared toolbar. Created by [`useGridCollection`](./?path=/story/common-hooks--usegridcollection) with a folders configuration.
+`GridFoldersState` manages the state for a [`GridFolders`](GridFolders.md) component, which displays both folders and items in a grid layout. It holds separate `CollectionState` instances for folders and items, plus a shared toolbar. Created by [`useGridCollection`](useGridCollection.md) with a folders configuration.
 
 ### Description
 
-`GridFoldersState` is the return value of the [`useGridFoldersCollection()`](./?path=/story/base-components-collections-gridfolders-usegridfolders--usegridfolders) hook.
+`GridFoldersState` is the return value of the [`useGridFoldersCollection()`](useGridFolders.md) hook.
 
 ### Props
 

package/dist/docs/GridSectionsProp.md

@@ -6,11 +6,11 @@
 
 ### Overview
 
-Configuration object for the `sections` prop on [`Grid`](./?path=/story/base-components-collections-grid--grid). Enables grouping grid items into sections with headers. Provide a `GridSections` component, a `groupBy` function that extracts the grouping key from each item, and an optional `renderSection` callback for custom section headers.
+Configuration object for the `sections` prop on [`Grid`](Grid.md). Enables grouping grid items into sections with headers. Provide a `GridSections` component, a `groupBy` function that extracts the grouping key from each item, and an optional `renderSection` callback for custom section headers.
 
 ### Description
 
-Pass to the `sections` prop of a `Grid` component to create [Grid Sections](./?path=/story/features-display-grid-sections--grid-sections).
+Pass to the `sections` prop of a `Grid` component to create [Grid Sections](<Grid Sections.md>).
 
 ### Props
 
@@ -18,5 +18,5 @@ Pass to the `sections` prop of a `Grid` component to create [Grid Sections](./?p
 |------|------|----------|---------|-------------|
 | `GridSections` | `(<T, F extends FiltersMap>(props: GridSectionsContentProps<T, F>) => Element) & { displayName: string; }` | Yes | - | A `GridSections` component. Import and pass the component without parameters. |
 | `groupBy` | `GroupBy<T>` | Yes | - | A function that extracts the grouping key from an item. Items with the same key will be grouped into the same section. |
-| `renderSection` | `RenderSection<T>` | No | - | A callback function to render the grid sections. The function receives the section ID and items in the section, and should return the `title`, and optional `primaryAction`, `badge`, or `summary` for each section. For more information, see the [section](./?path=/story/common-types--collectionsection) type. |
+| `renderSection` | `RenderSection<T>` | No | - | A callback function to render the grid sections. The function receives the section ID and items in the section, and should return the `title`, and optional `primaryAction`, `badge`, or `summary` for each section. For more information, see the [section](CollectionSection.md) type. |
 

package/dist/docs/GridState.md

@@ -8,11 +8,11 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 ### Overview
 
-`GridState` manages the state for a [`Grid`](./?path=/story/base-components-collections-grid--grid) component. It wraps a `CollectionState` for data, a `ToolbarCollectionState` for the toolbar, and tracks grid-specific UI state like size presets and sections. Created by [`useGridCollection`](./?path=/story/common-hooks--usegridcollection).
+`GridState` manages the state for a [`Grid`](Grid.md) component. It wraps a `CollectionState` for data, a `ToolbarCollectionState` for the toolbar, and tracks grid-specific UI state like size presets and sections. Created by [`useGridCollection`](useGridCollection.md).
 
 ### Description
 
-`GridState` is the return value of the [`useGridCollection()`](./?path=/story/base-components-collections-grid-usegridcollection--usegridcollection) hook.
+`GridState` is the return value of the [`useGridCollection()`](useGridCollection.md) hook.
 
 ### Props
 

package/dist/docs/ImportButton.md

@@ -6,7 +6,7 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 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.
+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/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
 

package/dist/docs/InMemoryBackend.md

@@ -74,9 +74,9 @@ export function createBackend() {
 |------|------|----------|---------|-------------|
 | `createOne` | `(index: number) => T` | Yes | - | A callback function for each item creation |
 | `itemKey` | `(item: T) => string` | Yes | - | A callback function that accepts an item and returns a unique ID of it. typically `item.id`. |
-| `predicate` | `((query: BackendQuery<FiltersMap>) => (item: T) => boolean)` | No | - | A function that accepts a subset of [ComputedQuery](./?path=/story/common-types--computedquery) sent by the client and returns another function that accepts an item and should return a boolean that indicates whether the item passes the query filtering or not. |
-| `orderBy` | `((query: BackendQuery<FiltersMap>) => Order<T>[])` | No | - | A function that accepts a subset of [ComputedQuery](./?path=/story/common-types--computedquery) sent by the client and returns another function that accepts an item and should returns a list of rules to order the items by |
-| `projection` | `((query: BackendQuery<FiltersMap>) => (item: T) => T)` | No | - | A function that accepts a subset of [ComputedQuery](./?path=/story/common-types--computedquery) sent by the client and returns a list of fields to project from the item |
+| `predicate` | `((query: BackendQuery<FiltersMap>) => (item: T) => boolean)` | No | - | A function that accepts a subset of [ComputedQuery](ComputedQuery.md) sent by the client and returns another function that accepts an item and should return a boolean that indicates whether the item passes the query filtering or not. |
+| `orderBy` | `((query: BackendQuery<FiltersMap>) => Order<T>[])` | No | - | A function that accepts a subset of [ComputedQuery](ComputedQuery.md) sent by the client and returns another function that accepts an item and should returns a list of rules to order the items by |
+| `projection` | `((query: BackendQuery<FiltersMap>) => (item: T) => T)` | No | - | A function that accepts a subset of [ComputedQuery](ComputedQuery.md) sent by the client and returns a list of fields to project from the item |
 | `delay` | `{ min: number; max: number; }` | No | `{ min: 0, max: 5 }` | Simulates API latency |
 | `total` | `number` | Yes | - | Total number of items to store in the backend |
 | `enableTotal` | `boolean` | No | - | Enable total for the backend. Defaults to "true" |

package/dist/docs/More Actions.md

@@ -14,11 +14,11 @@ Displays a menu of more actions on a page component.
 
 #### Usage
 
-1. Define a [`CollectionPage`](./?path=/story/base-components-pages-collection-page--collectionpage) or [`EntityPage`](./?path=/story/base-components-pages-entity-page--entitypage) component.
+1. Define a [`CollectionPage`](CollectionPage.md) or [`EntityPage`](EntityPage.md) component.
 1. Pass this `MoreActions` component to the `moreActions` prop on the page header component.
-1. Within the component, define an array of [`MoreActionsItem`](./?path=/story/common-types--moreactionsitem) objects to display.
+1. Within the component, define an array of [`MoreActionsItem`](MoreActionsItem.md) objects to display.
 
-> **Note:** Make sure that your page is nested under a [`WixPatternsProvider`](./?path=/story/base-components-providers--wixpatternsprovider).
+> **Note:** Make sure that your page is nested under a [`WixPatternsProvider`](WixPatternsProvider.md).
 
 
 ```tsx
@@ -27,7 +27,7 @@ import { MoreActions } from '@wix/patterns';
 
 ### Collection Page
 
-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).
+This example displays a menu at the collection page level by passing a `MoreActions` component to the `moreActions` prop of the [`CollectionPage.Header`](CollectionPage.Header.md).
 
 Example code: read `dist/examples/More Actions/collection-page.tsx`
 
@@ -85,7 +85,7 @@ Example code: read `dist/examples/More Actions/featured-more-actions-custom-posi
 
 | Prop | Type | Required | Default | Description |
 |------|------|----------|---------|-------------|
-| `items` | `MoreActionsPropItem[] \| MoreActionsPropItem[][]` | No | - | Actions items that appear in the `MoreActions` popover menu. \ Actions can be grouped by using an array of arrays. \ Each sub-array represents a different group within the popover, \ and a divider will be rendered after each sub-array to separate the groups. \| [MoreActionsItem](./?path=/story/common-types--moreactionsitem)[][] |
+| `items` | `MoreActionsPropItem[] \| MoreActionsPropItem[][]` | No | - | Actions items that appear in the `MoreActions` popover menu. \ Actions can be grouped by using an array of arrays. \ Each sub-array represents a different group within the popover, \ and a divider will be rendered after each sub-array to separate the groups. \| [MoreActionsItem](MoreActionsItem.md)[][] |
 | `containerId` | `string` | No | - | An id of the container defined in the installed on a site application that contains TPA's actions. |
 | `containerProps` | `Record<string, any>` | No | - | Additional properties passed to the `onClick` of the container's extensions menu items. |
 | `biAdditionalInfo` | `string` | No | - | Additional info for cairoPageCtaClicked BI event. |

package/dist/docs/MoreActionsItem.md

@@ -8,11 +8,11 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 ### Overview
 
-Defines an action item in the [`MoreActions`](./?path=/story/features-actions-moreactions--more-actions) dropdown menu. Each item has a `text` label, an `onClick` handler, and optional properties like `prefixIcon`, `skin` (`dark` or `destructive`), `disabled`, `subtitle`, and `dataHook`.
+Defines an action item in the [`MoreActions`](<More Actions.md>) dropdown menu. Each item has a `text` label, an `onClick` handler, and optional properties like `prefixIcon`, `skin` (`dark` or `destructive`), `disabled`, `subtitle`, and `dataHook`.
 
 ### Description
 
-Represents an item within the [More Actions](./?path=/story/features-actions-more-actions--more-actions) menu, defining its appearance and behavior.
+Represents an item within the [More Actions](<More Actions.md>) menu, defining its appearance and behavior.
 
 ### Props
 

package/dist/docs/MultiAutoInlineCheckboxFilter.md

@@ -10,7 +10,7 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 ### Overview
 
-`MultiAutoInlineCheckboxFilter` is based on [MultiInlineCheckboxFilter](./?path=/story/features-filter-components--multiinlinecheckboxfilter) and [MultiSelectCheckboxFilter](./?path=/story/features-filter-components--multiselectcheckboxfilter).
+`MultiAutoInlineCheckboxFilter` is based on [MultiInlineCheckboxFilter](MultiInlineCheckboxFilter.md) and [MultiSelectCheckboxFilter](MultiSelectCheckboxFilter.md).
 
 `MultiAutoInlineCheckboxFilter` automatically toggles between `MultiInlineCheckboxFilter` and `MultiSelectCheckboxFilter` based on the following cases:
   - In case the filter is located in the toolbar, it will be rendered as `MultiSelectCheckboxFilter`.

package/dist/docs/MultiBulkActionToolbar.md

@@ -131,6 +131,6 @@ Event   |   Description   |
 
 ### Usage
 
-All `<MultiBulkActionToolbar />` testkit APIs are exposed directly from the `<Table />` [testkit](./?path=/story/base-components-collections-table-table--table&activeTab=Testkit)
+All `<MultiBulkActionToolbar />` testkit APIs are exposed directly from the `<Table />` [testkit](Table.md)
 
 

package/dist/docs/MultiLevelSorting.md

@@ -12,9 +12,9 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 Allows visitors to apply sorting to multiple columns (in hierarchical order).
 
-See also [Sortable Columns](./?path=/story/features-sort-sortable-columns-sortable-columns--sortable-columns).
+See also [Sortable Columns](<Sortable Columns.md>).
 
-`<MultiLevelSorting>` must be passed to a [`<Table>`](./?path=/story/base-components-collections-table-table--table) `multiLevelSorting` prop. Note that only `<Table>` and `<TableGridSwitch>` support sorting.
+`<MultiLevelSorting>` must be passed to a [`<Table>`](Table.md) `multiLevelSorting` prop. Note that only `<Table>` and `<TableGridSwitch>` support sorting.
 
 Make sure to mark each column that you want to be sortable with `sortable: true`.
 
@@ -50,7 +50,7 @@ Read `dist/dts-bundle/types/MultiLevelSorting.d.ts` for `MultiLevelSorting`'s pr
 
 ### Usage
 
-All `<MultiLevelSorting />` testkit APIs are exposed using the `getMultiLevelSortingPanel` method of `<Table />` [testkit](./?path=/story/base-components-collections-table-table--table&activeTab=Testkit)
+All `<MultiLevelSorting />` testkit APIs are exposed using the `getMultiLevelSortingPanel` method of `<Table />` [testkit](Table.md)
 
 
 ## BI

package/dist/docs/MultiSelectCheckboxFilter.md

@@ -14,8 +14,8 @@ Some of that scaffolding is environment-scoped and is **not** needed to use this
 
 Use `MultiSelectCheckboxFilter` for rendering a list of items in a dropdown, with checkboxes.
 
-- Use [useFilterCollection](./?path=/story/features-filter-hooks--usefiltercollection) hook to create the collection state object for fetching the list items.
-- Use [useStaticListFilterCollection](./?path=/story/features-filter-hooks--usestaticlistfiltercollection) hook to create the collection state object for a static list of items.
+- Use [useFilterCollection](useFilterCollection.md) hook to create the collection state object for fetching the list items.
+- Use [useStaticListFilterCollection](useStaticListFilterCollection.md) hook to create the collection state object for a static list of items.
 
 
 ```tsx

package/dist/docs/MultiSelectCollectionFilter.md

@@ -16,7 +16,7 @@ Some of that scaffolding is environment-scoped and is **not** needed to use this
 
 Use `MultiSelectCollectionFilter` for rendering a filter that shows a list of items (fetched from a server) with tags.
 
-Use [`useFilterCollection`](./?path=/story/features-filter-hooks--usefiltercollection) to create the collection state object for fetching the list items.
+Use [`useFilterCollection`](useFilterCollection.md) to create the collection state object for fetching the list items.
 
 
 ```tsx