@wix/patterns 1.477.0 → 1.479.0

package/dist/docs/Sortable Columns.md

@@ -12,13 +12,13 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 The sortable columns feature allows users to sort a table by clicking on a column header, sorting the table based on the values in that column.
 
-> **Note:** To allow visitors to sort by multiple columns, you need to enable [Multi Level Sorting](./?path=/story/features-sort-sortable-columns-multilevelsorting--multilevelsorting).
+> **Note:** To allow visitors to sort by multiple columns, you need to enable [Multi Level Sorting](MultiLevelSorting.md).
 
 #### Usage
 
-1. Define a [`Table`](./?path=/story/base-components-collections-table-table--table) collection component.
+1. Define a [`Table`](Table.md) collection component.
 
-1. Define the table columns by passing [`TableColumn`](./?path=/story/common-types--tablecolumn) objects to the `columns` prop on the `Table`, specifiying the following properties:
+1. Define the table columns by passing [`TableColumn`](TableColumn.md) objects to the `columns` prop on the `Table`, specifiying the following properties:
 
     * `id`: A unique identifier for the column. **Required** to enable sortable columns.
     * `sortable`: Set to `true` to make the column sortable. **Required** to enable sortable columns.
@@ -27,7 +27,7 @@ The sortable columns feature allows users to sort a table by clicking on a colum
 
 #### Backend integration
 
-The [`query`](./?path=/story/common-types--computedquery) argument passed to [`fetchData`](./?path=/story/common-hooks--usecollection) includes a `sort` option. For tables, only one column can be sorted at a time, so the array will either be empty or contain a single sort object. Given your server supports sorting, convert the `sort` array to the appropriate parameter format for your server.
+The [`query`](ComputedQuery.md) argument passed to [`fetchData`](useCollection.md) includes a `sort` option. For tables, only one column can be sorted at a time, so the array will either be empty or contain a single sort object. Given your server supports sorting, convert the `sort` array to the appropriate parameter format for your server.
 
 
 ### Basic sortable column

package/dist/docs/SummaryBar.md

@@ -83,6 +83,6 @@ Event   |   Description   |
 
 ### Usage
 
-`getSummaryBar` API is exposed from the `<Table />` [testkit](./?path=/story/components-collection--table&tab=Testkit)
+`getSummaryBar` API is exposed from the `<Table />` [testkit](Table.md)
 
 

package/dist/docs/Table Sections.md

@@ -10,13 +10,13 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 ### Description
 
-Group [`Table`](./?path=/story/base-components-collections-table-table--table) data into sections.
+Group [`Table`](Table.md) data into sections.
 
 #### Usage
 
-1. Create a [`Table`](./?path=/story/base-components-collections-table-table--table) collection component.
-1. In the `fetchData` function of the [`useTableCollection()`](./?path=/story/base-components-collections-table-usetablecollection--usetablecollection) 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 table data by its values.
-1. Define the `sections` prop on the `Table`. The prop must be a [`TableSectionsProp`](./?path=/story/common-types--tablesectionsprop) object, where the `renderSection` callback returns a [`Section`](./?path=/story/common-types--collectionsection) object with `id`, `title`, and optional `primaryAction` properties.
+1. Create a [`Table`](Table.md) collection component.
+1. In the `fetchData` function of the [`useTableCollection()`](useTableCollection.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 table data by its values.
+1. Define the `sections` prop on the `Table`. The prop must be a [`TableSectionsProp`](TableSectionsProp.md) object, where the `renderSection` callback returns a [`Section`](CollectionSection.md) object with `id`, `title`, and optional `primaryAction` properties.
 
 ```tsx
 import { TableSections } from '@wix/patterns';

package/dist/docs/Table.md

@@ -22,9 +22,9 @@ The `Table` component displays data in rows and columns, allowing you to organiz
 
 #### Usage
 
-1. Wrap your code in a `WixDesignSystemProvider` followed by a [`WixPatternsProvider`](./?path=/story/base-components-providers--wixpatternsprovider).
-1. Wrap `Table` in a [`CollectionPage`](./?path=/story/base-components-pages-collection-page--collectionpage).
-1. Create a [`TableState`](./?path=/story/base-components-collections-table-tablestate--tablestate) using [`useTableCollection()`](./?path=/story/base-components-collections-table-usetablecollection--usetablecollection).
+1. Wrap your code in a `WixDesignSystemProvider` followed by a [`WixPatternsProvider`](WixPatternsProvider.md).
+1. Wrap `Table` in a [`CollectionPage`](CollectionPage.md).
+1. Create a [`TableState`](TableState.md) using [`useTableCollection()`](useTableCollection.md).
 1. Pass the `TableState` to the `state` prop.
 
 ```tsx
@@ -95,7 +95,7 @@ Example code: read `dist/examples/Table/fetch-total-async.tsx`
 
 ### Using Ambassador
 
-If you have a crud package from ambassador you can use our [useAmbassadorCollection](./?path=/story/common-hooks--useambassadorcollection) hook instead using the default [useCollection](./?path=/story/common-hooks--usecollection).
+If you have a crud package from ambassador you can use our [useAmbassadorCollection](useAmbassadorCollection.md) hook instead using the default [useCollection](useCollection.md).
 
 Example code: read `dist/examples/Table/using-ambassador.tsx`
 

package/dist/docs/TableColumn.md

@@ -8,13 +8,13 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 ### Overview
 
-Defines a column in a [`Table`](./?path=/story/base-components-collections-table--table) component. Extends the Wix Design System table column with Patterns-specific features: `sortable` / `defaultSortOrder`, `searchable`, `hideable` (for [`CustomColumns`](./?path=/story/features-display--customcolumns)), and `mobile` layout configuration.
+Defines a column in a [`Table`](Table.md) component. Extends the Wix Design System table column with Patterns-specific features: `sortable` / `defaultSortOrder`, `searchable`, `hideable` (for [`CustomColumns`](CustomColumns.md)), and `mobile` layout configuration.
 
 ### Description
 
-A column of a [`Table`](./?path=/story/base-components-collections-table-table--table) collection component.
+A column of a [`Table`](Table.md) collection component.
 
-> **Note:** `TableColumn` properties affect the behavior of features such as [Custom Columns](./?path=/story/features-display-custom-columns--overview) and [Sortable Columns](./?path=/story/features-sort-sortable-columns-sortable-columns--sortable-columns).
+> **Note:** `TableColumn` properties affect the behavior of features such as [Custom Columns](./?path=/story/features-display-custom-columns--overview) and [Sortable Columns](<Sortable Columns.md>).
 
 
 ### Props

package/dist/docs/TableDragAndDrop.md

@@ -12,13 +12,13 @@ Some of that scaffolding is environment-scoped and is **not** needed to use this
 
 ### Description
 
-Enables [drag and drop](./?path=/story/features-sort-drag-and-drop--overview) functionality on a [`Table`](./?path=/story/base-components-collections-table-table--table) component.
+Enables [drag and drop](./?path=/story/features-sort-drag-and-drop--overview) functionality on a [`Table`](Table.md) component.
 
 #### Usage
 
-1. Define a [`Table`](./?path=/story/base-components-collections-table-table--table) component.
+1. Define a [`Table`](Table.md) component.
 1. Import and pass the `TableDragAndDrop` component to the `dragAndDrop` prop on the `Table`.
-1. Define the relevant drag and drop props on the [`Table`](./?path=/story/base-components-collections-table-table--table&tab=API):
+1. Define the relevant drag and drop props on the [`Table`](Table.md):
 
       * `dragAndDropSubmit`
       * `dragAndDropCancel` (optional)

package/dist/docs/TableFolders.md

@@ -39,7 +39,7 @@ Example code: read `dist/examples/TableFolders/table-folders.tsx`
 
 ### With Tags
 
-This example shows a `TableFolders` component with tags. Note that you can only assign tags to table items and not to folders. [See Tags docs](./?path=/story/features-enrich-tags--tags-overview).
+This example shows a `TableFolders` component with tags. Note that you can only assign tags to table items and not to folders. [See Tags docs](<Tags Overview.md>).
 
 Example code: read `dist/examples/TableFolders/with-tags.tsx`
 

package/dist/docs/TableFoldersState.md

@@ -8,11 +8,11 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 ### Overview
 
-`TableFoldersState` manages the state for a [`TableFolders`](./?path=/story/base-components-collections-tablefolders--tablefolders) component, which displays folders and items in a table layout. Holds separate `CollectionState` instances for folders and items, plus a shared `TableState` and toolbar. Created by [`useTableCollection`](./?path=/story/base-components-collections-table-usetablecollection--usetablecollection) with a folders configuration.
+`TableFoldersState` manages the state for a [`TableFolders`](TableFolders.md) component, which displays folders and items in a table layout. Holds separate `CollectionState` instances for folders and items, plus a shared `TableState` and toolbar. Created by [`useTableCollection`](useTableCollection.md) with a folders configuration.
 
 ### Description
 
-`TableFoldersState` is the return value of the [`useTableFolders()`](./?path=/story/base-components-collections-tablefolders-usetablefolders--usetablefolders) hook.
+`TableFoldersState` is the return value of the [`useTableFolders()`](useTableFolders.md) hook.
 
 ### Props
 

package/dist/docs/TableGridSwitch.md

@@ -14,9 +14,9 @@ The `TableGridSwitch` component provides a pair of icons in the toolbar for togg
 
 #### Usage
 
-1. Wrap your code in a `WixDesignSystemProvider` followed by a [`WixPatternsProvider`](./?path=/story/base-components-providers--wixpatternsprovider).
-1. Wrap `TableGridSwitch` in a [`CollectionPage`](./?path=/story/base-components-pages-collection-page--collectionpage).
-1. Create a [`TableGridSwitchState`](./?path=/story/base-components-collections-tablegridswitch-tablegridswitchstate--tablegridswitchstate) using [`useTableGridSwitchCollection()`](./?path=/story/base-components-collections-tablegridswitch-usetablegridswitchcollection--usetablegridswitchcollection).
+1. Wrap your code in a `WixDesignSystemProvider` followed by a [`WixPatternsProvider`](WixPatternsProvider.md).
+1. Wrap `TableGridSwitch` in a [`CollectionPage`](CollectionPage.md).
+1. Create a [`TableGridSwitchState`](TableGridSwitchState.md) using [`useTableGridSwitchCollection()`](useTableGridSwitchCollection.md).
 1. Pass the `TableGridSwitchState` to the `state` prop.
 
 ```tsx
@@ -31,7 +31,7 @@ Example code: read `dist/examples/TableGridSwitch/basic-table-grid-switch.tsx`
 
 ### Custom columns
 
-A basic table and grid switch with [custom columns](./?path=/story/features-display--customcolumns). Note that custom columns are only available in the Table view.
+A basic table and grid switch with [custom columns](CustomColumns.md). Note that custom columns are only available in the Table view.
 
 Example code: read `dist/examples/TableGridSwitch/custom-columns.tsx`
 

package/dist/docs/TableGridSwitchDragAndDrop.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 [`TableGridSwitch`](./?path=/story/base-components-collections-grid-grid--grid) component.
+Enables [drag and drop](./?path=/story/features-sort-drag-and-drop--overview) functionality on a [`TableGridSwitch`](Grid.md) component.
 
 #### Usage
 
-1. Define a [`TableGridSwitch`](./?path=/story/base-components-collections-tablegridswitch-tablegridswitch--tablegridswitch) component.
+1. Define a [`TableGridSwitch`](TableGridSwitch.md) component.
 1. Import and pass the `TableGridSwitchDragAndDrop` to the `dragAndDrop` prop on the `TableGridSwitch`.
-1. Define the relevant drag and drop props on the [`TableGridSwitch`](./?path=/story/base-components-collections-tablegridswitch-tablegridswitch--tablegridswitch&tab=API):
+1. Define the relevant drag and drop props on the [`TableGridSwitch`](TableGridSwitch.md):
 
       * `dragAndDropSubmit`
       * `dragAndDropCancel` (optional)

package/dist/docs/TableGridSwitchFolders.md

@@ -36,7 +36,7 @@ Example code: read `dist/examples/TableGridSwitchFolders/tablegridswitchfolders.
 
 ### With Tags
 
-This example shows a `TableGridSwitchFolders` component with tags. Note that you can only assign tags to table items and not to folders. [See Tags docs](./?path=/story/features-enrich-tags--tags-overview).
+This example shows a `TableGridSwitchFolders` component with tags. Note that you can only assign tags to table items and not to folders. [See Tags docs](<Tags Overview.md>).
 
 Example code: read `dist/examples/TableGridSwitchFolders/with-tags.tsx`
 
@@ -46,37 +46,37 @@ Example code: read `dist/examples/TableGridSwitchFolders/with-tags.tsx`
 
 | Prop | Type | Required | Default | Description |
 |------|------|----------|---------|-------------|
-| `state` | `TableGridSwitchFoldersState<T1, F1, T2, F2>` | Yes | - | A TableGridSwitchFoldersState instance created using [useTableGridSwitchFoldersState](./?path=/story/base-components-collections-tablegridswitchfolders-usetablegridswitchfolders--usetablegridswitchfolders). |
+| `state` | `TableGridSwitchFoldersState<T1, F1, T2, F2>` | Yes | - | A TableGridSwitchFoldersState instance created using [useTableGridSwitchFoldersState](useTableGridSwitchFolders.md). |
 | `secondaryActions` | `ToolbarSecondaryActionsElement` | No | - | Secondary buttons w/o PopoverMenu component to be rendered on the toolbar. |
 | `search` | `boolean \| FilterElement \| CollectionSearchElement` | No | `true` | Displays a search input on the right side of the table toolbar.<br> <br> Accepts a boolean or a custom React element as a parameter. When passing `false`, no search input is displayed. |
-| `title` | `ToolbarTitleElement` | No | - | Displays a title at the left of a toolbar. Accepts a [ToolbarTitle](./?path=/story/features-display-toolbar--toolbartitle) component. |
+| `title` | `ToolbarTitleElement` | No | - | Displays a title at the left of a toolbar. Accepts a [ToolbarTitle](ToolbarTitle.md) component. |
 | `tags` | `TagsElement<T1, Partial<F1 & F2>>` | No | - | Enables tags feature. In this element you can pass the configuration |
-| `errorState` | `((err: unknown, params: { isOnline: boolean; retry: () => void; }) => ReactElement<any, string \| JSXElementConstructor<any>>)` | No | - | A render function to be rendered when there's an error fetching data from the server.<br> The function accepts the following parameters <br> * `err`: The error thrown by the [fetchData](./?path=/story/common-hooks--usecollection) function <br> * `isOnline`: Indicates whether internet connection is available <br> * `retry`: Retry collection fetch on failed response, similar to `collection.retryFetch` <br> Returns [`EmptyState`](https://www.docs.wixdesignsystem.com/?path=/story/components-layout--emptystate) component. |
-| `renderError` | `((params: { err: unknown; isOnline: boolean; retry: () => void; }) => ReactElement<any, string \| JSXElementConstructor<any>>)` | No | - | A render function to be rendered when there's an error fetching data from the server.<br> The function accepts the following parameters <br> * `err`: The error thrown by the [fetchData](./?path=/story/common-hooks--usecollection) function <br> * `isOnline`: Indicates whether internet connection is available <br> * `retry`: Retry collection fetch on failed response, similar to `collection.retryFetch` <br> Returns [`EmptyState`](https://www.docs.wixdesignsystem.com/?path=/story/components-layout--emptystate) component. @deprecated Use `errorState` instead. |
+| `errorState` | `((err: unknown, params: { isOnline: boolean; retry: () => void; }) => ReactElement<any, string \| JSXElementConstructor<any>>)` | No | - | A render function to be rendered when there's an error fetching data from the server.<br> The function accepts the following parameters <br> * `err`: The error thrown by the [fetchData](useCollection.md) function <br> * `isOnline`: Indicates whether internet connection is available <br> * `retry`: Retry collection fetch on failed response, similar to `collection.retryFetch` <br> Returns [`EmptyState`](https://www.docs.wixdesignsystem.com/?path=/story/components-layout--emptystate) component. |
+| `renderError` | `((params: { err: unknown; isOnline: boolean; retry: () => void; }) => ReactElement<any, string \| JSXElementConstructor<any>>)` | No | - | A render function to be rendered when there's an error fetching data from the server.<br> The function accepts the following parameters <br> * `err`: The error thrown by the [fetchData](useCollection.md) function <br> * `isOnline`: Indicates whether internet connection is available <br> * `retry`: Retry collection fetch on failed response, similar to `collection.retryFetch` <br> Returns [`EmptyState`](https://www.docs.wixdesignsystem.com/?path=/story/components-layout--emptystate) component. @deprecated Use `errorState` instead. |
 | `maxSelection` | `number` | No | - | Limits the amount of rows a visitor can select. |
-| `views` | `CollectionViewsDropdownElement<Partial<F1 & F2>>` | No | - | Adds view options to the table headers. Accepts a [Views](./?path=/story/features-display-views--views) component. |
+| `views` | `CollectionViewsDropdownElement<Partial<F1 & F2>>` | No | - | Adds view options to the table headers. Accepts a [Views](Views.md) component. |
 | `filters` | `CollectionToolbarFiltersElement` | No | - | Adds filters to the toolbar and/or a sliding panel. Accepts a `ToolbarFilters` component, which must have the `panelTitle` prop defined. |
-| `tabs` | `TabsFilterElement<TabsFilterProps<T1>>` | No | - | Displays tabs at the left of a toolbar. Accepts a [TabsFilter](./?path=/story/features-filter-components--tabsfilter) component. |
+| `tabs` | `TabsFilterElement<TabsFilterProps<T1>>` | No | - | Displays tabs at the left of a toolbar. Accepts a [TabsFilter](TabsFilter.md) component. |
 | `minCardHeight` | `MinHeight<string \| number>` | No | `300px` | Minimum height for a card's container when showing:<br> - A loader<br> - Empty state<br> - Error state <br><br> If no unit is specified, `px` is used. |
-| `emptyState` | `ReactNode` | No | - | Renders when there are no items to display. Accepts a [`CollectionEmptyState`](./?path=/story/features-display-empty-states--collectionemptystate) component. |
-| `noResultsState` | `ReactNode \| ((params: { hasAvailableItems: boolean; query: ComputedQuery<Partial<F1 & F2>>; }) => ReactNode)` | No | - | Shown when a search or filter has no results. Accepts a [`CollectionNoResultsState`](./?path=/story/features-display-empty-states--collectionnoresultsstate) component, or a function that accepts the following parameters: - `hasAvailableItems`: Indicates whether other items may be shown using other filter or search parameters. - `query`: An instance of [`ComputedQuery`](./?path=/story/common-models--computedquery) representing the query that resulted in the empty state. The function should return [`CollectionNoResultsState`](./?path=/story/features-display-empty-states--collectionnoresultsstate). |
-| `summaryBar` | `ReactNode` | No | - | Display a summary bar below the toolbar. Accepts a [`SummaryBar`](./?path=/story/features-display-toolbar--summarybar) component. |
+| `emptyState` | `ReactNode` | No | - | Renders when there are no items to display. Accepts a [`CollectionEmptyState`](CollectionEmptyState.md) component. |
+| `noResultsState` | `ReactNode \| ((params: { hasAvailableItems: boolean; query: ComputedQuery<Partial<F1 & F2>>; }) => ReactNode)` | No | - | Shown when a search or filter has no results. Accepts a [`CollectionNoResultsState`](CollectionNoResultsState.md) component, or a function that accepts the following parameters: - `hasAvailableItems`: Indicates whether other items may be shown using other filter or search parameters. - `query`: An instance of [`ComputedQuery`](ComputedQuery.md) representing the query that resulted in the empty state. The function should return [`CollectionNoResultsState`](CollectionNoResultsState.md). |
+| `summaryBar` | `ReactNode` | No | - | Display a summary bar below the toolbar. Accepts a [`SummaryBar`](SummaryBar.md) component. |
 | `dragAndDropSubmit` | `DragAndDropSubmit<T1, Partial<F1 & F2>>` | No | - | Function that submits a drop event to the server. <br> <br> The parameter is an event object containing the following details: <br> -`from: {item: T; index: number}`: The dragged item. <br> -`after: null \| [item: T; iindex: number}`: The previous dropped item. If this is the first item to be dropped, this argument is `null`. <br> -`filters`: Applied [Drag and Drop](./?path=/story/features-sort-drag-and-drop--overview) filters. @returns Promise |
 | `dragAndDropBulkSubmit` | `DragAndDropBulkSubmit<T1, Partial<F1 & F2>>` | No | - | Function that submits an array of drop events to the server. <br> <br> The parameter is an array of event objects containing the following details: <br> -`from: {item: T; index: number}`: The dragged item. <br> -`after: null \| [item: T; index: number}`: The previous dropped item. If this is the first item to be dropped, this argument is `null`. <br> -`filters`: Applied [Drag and Drop](./?path=/story/features-sort-drag-and-drop--overview) filters. <br> @returns Promise |
 | `dragAndDropCancel` | `DragAndDropCancel<T1, Partial<F1 & F2>>` | No | - | A function that cancels a drop event. <br> Supported arguments: <br> - `from: {item: T; index: number}`: The dragged item. - `after: null \| {item: T; index: number}`: The item that the dragged item was dropped after. If dropped at the head of the collection, this argument will be `null`. - `filters`: Currently applied filters. Used in cases where your server holds a unique ordering per filtering. See the `dragAndDropCategories` prop. If the move is cancelled, the function returns a toast config object with a message. Otherwise, the function will return a null value. |
 | `extensionMenuItems` | `ExtensionMenuItemsType` | No | - | @deprecated It doesn't need to be passed implicitly anymore. |
 | `dragAndDropReorderModeToolbar` | `ReorderModeToolbarElement \| null` | No | - | Drag and drop reorder mode toolbar. This prop accepts a `ReorderModeToolbar` component.<br> The `ReorderModeToolbar` component accepts the following props:<br> + `learnMoreUrl`: [string] A URL in the toolbar.<br> + `reorderModeTitle`: [string] A title in the toolbar. |
-| `customColumns` | `CustomColumnsElement \| null` | No | - | Adds functionality to allow visitors to create choose which columns to display and in what order. Accepts a [CustomColumns](./?path=/story/features-display--customcolumns) component. |
-| `multiLevelSorting` | `MultiLevelSortingElement` | No | - | Adds functionality to allow visitors to sort multiple columns simultaneously. Accepts a [MultiLevelSorting](./?path=/story/features-sort-sortable-columns-multilevelsorting--multilevelsorting) component. |
-| `primaryActionButton` | `PrimaryActionButtonElement` | No | - | Adds functionality for a primary action button in the toolbar. Accepts a [PrimaryActionButton](./?path=/story/features-actions-primary-actions--primary-action-button) component. |
-| `moreActions` | `MoreActionsElement` | No | - | A [`MoreActions`](./?path=/story/features-actions-more-actions--more-actions) component to be rendered on the header. |
+| `customColumns` | `CustomColumnsElement \| null` | No | - | Adds functionality to allow visitors to create choose which columns to display and in what order. Accepts a [CustomColumns](CustomColumns.md) component. |
+| `multiLevelSorting` | `MultiLevelSortingElement` | No | - | Adds functionality to allow visitors to sort multiple columns simultaneously. Accepts a [MultiLevelSorting](MultiLevelSorting.md) component. |
+| `primaryActionButton` | `PrimaryActionButtonElement` | No | - | Adds functionality for a primary action button in the toolbar. Accepts a [PrimaryActionButton](PrimaryActionButton.md) component. |
+| `moreActions` | `MoreActionsElement` | No | - | A [`MoreActions`](<More Actions.md>) component to be rendered on the header. |
 | `AddApplyFiltersButton` | `AddApplyFiltersButtonType` | No | - | Apply filter button implementation: `import { AddApplyFiltersButton } from '@wix/patterns';` <br> Add `Apply` button to the filters panel footer. Panel filters will be applied only after the button is clicked. |
-| `internalScroll` | `boolean` | No | - | Indicates whether the table should have an [internal scroll](./?path=/story/features-display-internal-scroll--internal-scroll) instead of the default page scroll. |
+| `internalScroll` | `boolean` | No | - | Indicates whether the table should have an [internal scroll](<Internal Scroll.md>) instead of the default page scroll. |
 | `showFieldTypeIcons` | `boolean` | No | `false` | When true, renders prefix icons for field types in column headers, filters, and the customize-columns panel. Each column and filter should have a `fieldType` property set so Cairo can render the matching icon. |
 | `showTitleBar` | `boolean` | No | `true` | Indicates whether to show Table Title Bar or not. Note: if you pass `showTitleBar = false` title bar is not removed from the DOM. For better accessibility column titles should be defined as well. |
-| `exportButton` | `ReactElement<any, string \| JSXElementConstructor<any>>` | No | - | A [`<ExportButton />`](./?path=/story/features-export--exportto) react element to be added to the toolbar |
+| `exportButton` | `ReactElement<any, string \| JSXElementConstructor<any>>` | No | - | A [`<ExportButton />`](ExportTo.md) react element to be added to the toolbar |
 | `importButton` | `ReactElement<any, string \| JSXElementConstructor<any>>` | No | - | A [`<ImportButton />`] react element to be added to the toolbar. |
-| `exportModal` | `ReactElement<any, string \| JSXElementConstructor<any>>` | No | - | A [`<ExportModal />`](./?path=/story/features-export--exportto#CTA_is_out_of_the_table) react element to be rendered in table's context. |
+| `exportModal` | `ReactElement<any, string \| JSXElementConstructor<any>>` | No | - | A [`<ExportModal />`](ExportTo.md) react element to be rendered in table's context. |
 | `importModal` | `ReactElement<any, string \| JSXElementConstructor<any>>` | No | - | A [`<ImportModal />`] react element to be rendered in table's context. |
 | `dragAndDropCategories` | `(keyof F1 \| keyof F2)[][] \| null` | No | - | By default, drag and drop works only without filters. To enable drag and drop with filters, pass an array of filters to this prop. The functionality will then work only for the specified filters, and to enable without filters, you must pass an empty array. For more information, see the [Drag and Drop Overview](//?path=/story/features-sort-drag-and-drop--overview). |
 | `actionCell` | `ActionCell<T1, F1>` | No | - | Adds an action on the grid item. For example, a delete button to delete an item. Accepts an [`ActionCellProps`](https://www.docs.wixdesignsystem.com/?path=/story/components-lists-table--tableactioncell) object, or a function that returns an `ActionCellProps` object. |
@@ -86,9 +86,9 @@ Example code: read `dist/examples/TableGridSwitchFolders/with-tags.tsx`
 | `folderActionCell` | `ActionCell<T2, F2>` | No | - | Same as `actionCell`, but for a folder item. |
 | `renderFolderAddItem` | `(() => ReactElement<AddItemProps, string \| JSXElementConstructor<any>>)` | No | - | Same as `renderAddItem`, but for a folder item. |
 | `skin` | `"standard" \| "neutral"` | No | - | @deprecated The table skin is determined internally and any value passed here is ignored. This prop will be removed in a future release. |
-| `bulkActionToolbar` | `MultiCollectionBulkActionToolbarRenderProps` | No | - | A toolbar for performing bulk actions on multiple items. Supported parameters: + `selectedValues`: Selected item values. + `uncheckedValues`: Unselected item values. + `isSelectAll`: [bool] Whether the **Select All** option is selected. + `openModal`: Opens a modal that contains the component from `bulkActionModal` render prop. + `clearSelection`: Clears all selections. Call this after the action on the selected items finishes. + `closeModal`: Closes the modal. + `openConfirmModal`: Opens a `<MessageModalLayout />` to confirm an action to be applied to the selected items. + `query`: [object] Instance of [ComputedQuery](./?path=/story/common-types--computedquery) that represents the query that resulted in an empty state. Representation of the current paging, sorting and filtering applied. Usually for using together with bulk action such as `updateAll` and `deleteAll`. |
-| `columns` | `TableFoldersColumn<T1, T2>[]` | Yes | - | The same as [Table.columns](./?path=/story/base-components-collections-table-table--table), with the addition of `renderFolder` property. |
-| `hideBulkSelectionCheckbox` | `boolean` | No | - | Hides bulk selection checkbox in the table titlebar, If the [`MultiBulkActionToolbar`](./?path=/story/features-actions-bulk-actions--multibulkactiontoolbar) feature is enabled, this flag will have no effect. |
+| `bulkActionToolbar` | `MultiCollectionBulkActionToolbarRenderProps` | No | - | A toolbar for performing bulk actions on multiple items. Supported parameters: + `selectedValues`: Selected item values. + `uncheckedValues`: Unselected item values. + `isSelectAll`: [bool] Whether the **Select All** option is selected. + `openModal`: Opens a modal that contains the component from `bulkActionModal` render prop. + `clearSelection`: Clears all selections. Call this after the action on the selected items finishes. + `closeModal`: Closes the modal. + `openConfirmModal`: Opens a `<MessageModalLayout />` to confirm an action to be applied to the selected items. + `query`: [object] Instance of [ComputedQuery](ComputedQuery.md) that represents the query that resulted in an empty state. Representation of the current paging, sorting and filtering applied. Usually for using together with bulk action such as `updateAll` and `deleteAll`. |
+| `columns` | `TableFoldersColumn<T1, T2>[]` | Yes | - | The same as [Table.columns](Table.md), with the addition of `renderFolder` property. |
+| `hideBulkSelectionCheckbox` | `boolean` | No | - | Hides bulk selection checkbox in the table titlebar, If the [`MultiBulkActionToolbar`](MultiBulkActionToolbar.md) feature is enabled, this flag will have no effect. |
 | `onSelectionChanged` | `OnSelectionChangedFn` | No | - | Defines a callback function which is called when selection happens. <br /> There are 3 types of selections: * `ALL` - bulk selection checkbox has been triggered to select all items * `SINGLE_TOGGLE` - a checkbox to select one item from the list has been triggered. The change object will also include an `id` prop with the unique item identifier and a `value` prop with the new boolean selection state of the item. * `NONE` - bulk selection has been triggered to unselect all items. |
 | `onSelectionStarted` | `(() => void)` | No | - | Called when item selection triggered but not changed yet. |
 | `showSelection` | `boolean` | No | `false` | Displays selection checkbox as a first column in each row. To hide the selection checkbox from a specific row, set its `row.unselectable` value to true in the data array. |

package/dist/docs/TableGridSwitchFoldersState.md

@@ -6,17 +6,17 @@
 
 ### Overview
 
-`TableGridSwitchFoldersState` manages the state for a [`TableGridSwitchFolders`](./?path=/story/base-components-collections-tablegridswitch--tablegridswitchfolders) component — a collection that supports switching between table and grid views while also displaying folders. Holds a `GridFoldersState`, a `TableFoldersState`, and a `viewTypeState` for toggling layouts.
+`TableGridSwitchFoldersState` manages the state for a [`TableGridSwitchFolders`](TableGridSwitchFolders.md) component — a collection that supports switching between table and grid views while also displaying folders. Holds a `GridFoldersState`, a `TableFoldersState`, and a `viewTypeState` for toggling layouts.
 
 ### Description
 
-`TableGridSwitchFoldersState` is the return value of the [`useTableGridSwitchFolders()`](./?path=/story/base-components-collections-tablegridswitchfolders-usetablegridswitchfolders--usetablegridswitchfolders) hook.
+`TableGridSwitchFoldersState` is the return value of the [`useTableGridSwitchFolders()`](useTableGridSwitchFolders.md) hook.
 
 ### Props
 
 | Prop | Type | Required | Default | Description |
 |------|------|----------|---------|-------------|
-| `gridFoldersState` | `GridFoldersState<T1, F1, T2, F2>` | Yes | - | [GridFoldersState](./?path=/story/base-components-collections-gridfolders-gridfoldersstate--gridfoldersstate) |
-| `tableFoldersState` | `TableFoldersState<T1, F1, T2, F2>` | Yes | - | [TableFoldersState](./?path=/story/base-components-collections-tablefolders-tablefoldersstate--tablefoldersstate) |
-| `toolbar` | `ToolbarCollectionState<T1, {}>` | Yes | - | Underlying [ToolbarCollectionState](./?path=/story/common-state--toolbarcollectionstate) instance |
+| `gridFoldersState` | `GridFoldersState<T1, F1, T2, F2>` | Yes | - | [GridFoldersState](GridFoldersState.md) |
+| `tableFoldersState` | `TableFoldersState<T1, F1, T2, F2>` | Yes | - | [TableFoldersState](TableFoldersState.md) |
+| `toolbar` | `ToolbarCollectionState<T1, {}>` | Yes | - | Underlying [ToolbarCollectionState](ToolbarCollectionState.md) instance |
 

package/dist/docs/TableGridSwitchState.md

@@ -8,11 +8,11 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 ### Overview
 
-`TableGridSwitchState` manages the state for a [`TableGridSwitch`](./?path=/story/base-components-collections-tablegridswitch--tablegridswitch) component, which lets users switch between table and grid views. Wraps a `GridState` and a `TableState` with a shared `viewTypeState`. Created by [`useTableGridSwitchCollection`](./?path=/story/common-hooks--usetablegridswitchcollection).
+`TableGridSwitchState` manages the state for a [`TableGridSwitch`](TableGridSwitch.md) component, which lets users switch between table and grid views. Wraps a `GridState` and a `TableState` with a shared `viewTypeState`. Created by [`useTableGridSwitchCollection`](useTableGridSwitchCollection.md).
 
 ### Description
 
-`TableGridSwitchState` is the return value of the [`useTableGridSwitchCollection()`](./?path=/story/base-components-collections-tablegridswitch-usetablegridswitchcollection--usetablegridswitchcollection) hook.
+`TableGridSwitchState` is the return value of the [`useTableGridSwitchCollection()`](useTableGridSwitchCollection.md) hook.
 
 ### Props
 

package/dist/docs/TableSectionsProp.md

@@ -6,11 +6,11 @@
 
 ### Overview
 
-Configuration object for the `sections` prop on [`Table`](./?path=/story/base-components-collections-table--table). Enables grouping table rows into collapsible sections with headers. Provide a `TableSections` component, a `groupBy` function, a `renderSection` callback, and optional `collapsible` and `events` properties.
+Configuration object for the `sections` prop on [`Table`](Table.md). Enables grouping table rows into collapsible sections with headers. Provide a `TableSections` component, a `groupBy` function, a `renderSection` callback, and optional `collapsible` and `events` properties.
 
 ### Description
 
-Pass to the `sections` prop of a `Table` component to create [Table Sections](./?path=/story/features-display-table-sections--table-sections).
+Pass to the `sections` prop of a `Table` component to create [Table Sections](<Table Sections.md>).
 
 ### Props
 
@@ -18,5 +18,5 @@ Pass to the `sections` prop of a `Table` component to create [Table Sections](./
 |------|------|----------|---------|-------------|
 | `TableSections` | `(<T, F extends FiltersMap>({ groupBy, renderSection, table, columns, rowDetails, collapsible, events, ...collectionTableProps }: TableSectionsProps<T, F>) => Element) & { displayName: string; }` | Yes | - | A `TableSections` 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>` | Yes | - | A callback function to render the table 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>` | Yes | - | A callback function to render the table 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/TableState.md

@@ -8,11 +8,11 @@ Paths written as `dist/…` below are relative to the `@wix/patterns` package ro
 
 ### Overview
 
-`TableState` manages the state for a [`Table`](./?path=/story/base-components-collections-table--table) component. It wraps a `CollectionState` for data, a `ToolbarCollectionState` for the toolbar, tracks visible columns and sorting, and supports virtual scrolling and drag-and-drop. Created by [`useTableCollection`](./?path=/story/base-components-collections-table-usetablecollection--usetablecollection).
+`TableState` manages the state for a [`Table`](Table.md) component. It wraps a `CollectionState` for data, a `ToolbarCollectionState` for the toolbar, tracks visible columns and sorting, and supports virtual scrolling and drag-and-drop. Created by [`useTableCollection`](useTableCollection.md).
 
 ### Description
 
-`TableState` is the return value of the [`useTableCollection()`](./?path=/story/base-components-collections-table-usetablecollection--usetablecollection) hook.
+`TableState` is the return value of the [`useTableCollection()`](useTableCollection.md) hook.
 
 ### Props
 

package/dist/docs/TableTopNotification.md

@@ -37,7 +37,7 @@ Example code: read `dist/examples/TableTopNotification/nested-table.tsx`
 
 ### Set Message
 
-For setting a new message after an event from the server for example, use `collection.topNotification` API returned from the [useCollection](./?path=/story/common-hooks--usecollection) state object:
+For setting a new message after an event from the server for example, use `collection.topNotification` API returned from the [useCollection](useCollection.md) state object:
 
 ```ts
 interface TableTopNotificationAPI {
@@ -85,6 +85,6 @@ Event   |   Description   |
 
 ### Usage
 
-`getTopNotification` API is exposed from the `<Table />` [testkit](./?path=/story/base-components-collections-table-table--table&tab=Testkit)
+`getTopNotification` API is exposed from the `<Table />` [testkit](Table.md)
 
 

package/dist/docs/TabsFilter.md

@@ -83,6 +83,6 @@ Event   |   Description   |
 
 ### Usage
 
-`getToolbarTabs` API is exposed from the `<Table />` [testkit](./?path=/story/base-components-collections-table-table--table&activeTab=Testkit)
+`getToolbarTabs` API is exposed from the `<Table />` [testkit](Table.md)
 
 

package/dist/docs/Tags Overview.md

@@ -43,7 +43,7 @@ Using tags in entity page can be used to manage tags for a specific entity. The
 - Assigning new tags to the entity
 - Removing existing tags from the entity
 
-Read more about [Tags](./?path=/story/features-enrich-tags--tagswidget).
+Read more about [Tags](TagsWidget.md).
 
 
 ## Server Prerequisites

package/dist/docs/Tags.md

@@ -17,7 +17,7 @@ Tags allow users a flexible way to categorize and manage their data.
 Wix Patterns table supports displaying the tags as a column, bulk assign for tags and filtering by tags.
 
 You can opt-in to the Tags feature on your collection by using the tags prop in the Table.
-See [Tags overview](./?path=/story/features-enrich-tags--tags-overview) for an overview of the feature and the required server implementation.
+See [Tags overview](<Tags Overview.md>) for an overview of the feature and the required server implementation.
 
 ## Tags API
 
@@ -32,7 +32,7 @@ Note the following limitations:
 
 ### Getting Started
 
-1. Pass `Tags` to [Table](./?path=/story/base-components-collections-table-table--table)
+1. Pass `Tags` to [Table](Table.md)
 
 ```diff
 import React from 'react';
@@ -116,7 +116,7 @@ import { CollectionPage } from '@wix/patterns/page';
   }
 ```
 
-2. For enabling bulk assignment action add [MultiBulkActionToolbar](./?path=/story/features-actions-bulk-actions--multibulkactiontoolbar).
+2. For enabling bulk assignment action add [MultiBulkActionToolbar](MultiBulkActionToolbar.md).
 
 
 ## Examples

package/dist/docs/TagsWidget.md

@@ -23,9 +23,9 @@ Wix Patterns is responsible for interacting with the tags management service for
 
 ### Getting Started
 
-1. Wrap your app with one of the Wix Patterns providers: [WixPatternsProvider](./?path=/story/base-components-providers--wixpatternsprovider).
+1. Wrap your app with one of the Wix Patterns providers: [WixPatternsProvider](WixPatternsProvider.md).
 
-2. Wrap your page with [WidgetsFormProvider](./?path=/story/base-components-providers--widgetsformprovider).
+2. Wrap your page with [WidgetsFormProvider](WidgetsFormProvider.md).
 
 ```diff
 + import { WidgetsFormProvider } from '@wix/patterns/page';
@@ -85,7 +85,7 @@ function MyEntityPage({ entity }: { entity: MyEntity }) {
   }
 ```
 
-4. In the previous step implementation, the tags will be updated in the server on every action of assign or unassign a tag. If you want to update the tags only on submit of a button, you can use the `TagsWidget` without the `onSubmit` prop and use the updated value of the tags from the `state` object returned from the [useWidgetsFormContext](./?path=/story/common-hooks--usewidgetsformcontext) hook.
+4. In the previous step implementation, the tags will be updated in the server on every action of assign or unassign a tag. If you want to update the tags only on submit of a button, you can use the `TagsWidget` without the `onSubmit` prop and use the updated value of the tags from the `state` object returned from the [useWidgetsFormContext](useWidgetsFormContext.md) hook.
 
 ```diff
 - import { Page } from '@wix/design-system'';

package/dist/docs/ToolbarCollectionState.md

@@ -15,5 +15,5 @@
 | `closeSidePanel` | `() => void` | Yes | - | Closes WixPatterns side panel |
 | `openFiltersPanel` | `() => void` | Yes | - | Opens the filters side panel |
 | `openCustomFieldModal` | `(opts?: Pick<OpenFieldModalOptions, "onSave" \| "customOrigin" \| "initialField" \| "lockedProperties"> \| undefined) => void` | Yes | - | Opens the custom field modal on create mode. `initialField` prefills the type, name, and/or required rule; `lockedProperties` makes any of those non-editable (a `required` lock is dropped if the picked type's settings section can't apply the prefill). `onSave` fires with the new field's id once it's successfully added. |
-| `getPendingFilter` | `<A>(filter: A) => Filter<any> \| A` | Yes | - | Use this function when using [AddApplyFiltersButton](./?path=/story/features-filter-components--toolbarfilters#Apply_changes) to obtain a reference to the filter that is about to be applied. This is useful when you want to modify the filter value within a custom filter component. |
+| `getPendingFilter` | `<A>(filter: A) => Filter<any> \| A` | Yes | - | Use this function when using [AddApplyFiltersButton](ToolbarFilters.md) to obtain a reference to the filter that is about to be applied. This is useful when you want to modify the filter value within a custom filter component. |
 

package/dist/docs/ToolbarFilters.md

@@ -22,7 +22,7 @@ If you don't want any inline filters, then set `inline` to 0:
  
  `<CollectionToolbarFilters inline={0}>` 
  
-> **Note:** Some filters such as the [`DateRangeFilter`](./?path=%/story/features-filter-components--daterangefilter) and [`RadioGroupFilter`](./?path=/story/features-filter-components--radiogroupfilter), are always displayed in the side panel and aren't supported inline in the toolbar.
+> **Note:** Some filters such as the [`DateRangeFilter`](./?path=%/story/features-filter-components--daterangefilter) and [`RadioGroupFilter`](RadioGroupFilter.md), are always displayed in the side panel and aren't supported inline in the toolbar.
 
 **Do:**
 

package/dist/docs/ToolbarSecondaryActions.md

@@ -47,5 +47,5 @@ Example code: read `dist/examples/ToolbarSecondaryActions/grouped-actions-with-d
 
 | Prop | Type | Required | Default | Description |
 |------|------|----------|---------|-------------|
-| `items` | `ActionSubitem[]` | Yes | - | The secondary actions to display in the toolbar. \| [ActionSubitem[][]](./?path=/story/common-types--actionsubitem) |
+| `items` | `ActionSubitem[]` | Yes | - | The secondary actions to display in the toolbar. \| [ActionSubitem[][]](ActionSubItem.md) |
 

package/dist/docs/View.md

@@ -6,7 +6,7 @@
 
 ### Overview
 
-Defines a saved view in the [`Views`](./?path=/story/features-display-views--views) dropdown. A view captures a snapshot of filters, visible columns, column order, sort directions, and layout type (table or grid). Use `isDefaultView` to set the initial view when the collection loads.
+Defines a saved view in the [`Views`](Views.md) dropdown. A view captures a snapshot of filters, visible columns, column order, sort directions, and layout type (table or grid). Use `isDefaultView` to set the initial view when the collection loads.
 
 ### Props
 

package/dist/docs/Views.md

@@ -76,7 +76,7 @@ Example code: read `dist/examples/Views/views-separated-by-category-in-the-dropd
 
 ### Usage
 
-Views API is exposed from the `<Table />` [testkit](./?path=/story/base-components-collections-table-table--table&activeTab=Testkit)
+Views API is exposed from the `<Table />` [testkit](Table.md)
 
 ## APIs List
 

package/dist/docs/WidgetsFormProvider.md

@@ -16,9 +16,9 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 import { WidgetsFormProvider } from '@wix/patterns/page';
 ```
 
-The `WidgetsFormProvider` is designed to being used as an alternative in cases where [EntityPage](./?path=/story/base-components-pages-entity-page--entitypage) doesn’t cover your needs (for example, you have a side panel and not a full page experience for editing your entity). It enables you to include form-based widgets such as [TagsWidget](./?path=/story/features-enrich-tags--tagswidget) and [CustomFieldsWidget](./?path=/story/features-enrich-data-extension-components--customfieldswidget), and access the page’s state and to validate the widgets data through the [useWidgetsFormContext](./?path=/story/common-hooks--usewidgetsformcontext) hook.
+The `WidgetsFormProvider` is designed to being used as an alternative in cases where [EntityPage](EntityPage.md) doesn’t cover your needs (for example, you have a side panel and not a full page experience for editing your entity). It enables you to include form-based widgets such as [TagsWidget](TagsWidget.md) and [CustomFieldsWidget](CustomFieldsWidget.md), and access the page’s state and to validate the widgets data through the [useWidgetsFormContext](useWidgetsFormContext.md) hook.
 
-In any case that you have a full page experience, we suggest to use [EntityPage](./?path=/story/base-components-pages-entity-page--entitypage) and not to use `WidgetsFormProvider`, so you can get more out of the box capabilities.
+In any case that you have a full page experience, we suggest to use [EntityPage](EntityPage.md) and not to use `WidgetsFormProvider`, so you can get more out of the box capabilities.
 
 
 ### Usage
@@ -38,7 +38,7 @@ export const MyPageProvider = () => {
 }
 ```
 
-Inside the page, you will be able to access the `state` object returned from the [useWidgetsFormContext](./?path=/story/common-hooks--useformpagecontext) hook.
+Inside the page, you will be able to access the `state` object returned from the [useWidgetsFormContext](useWidgetsFormContext.md) hook.
 
 ```diff
 + import { useWidgetsFormContext } from '@wix/patterns';

package/dist/docs/WixPatternsEssentialsProvider.md

@@ -24,7 +24,7 @@ Every app must be wrapped with this provider in order to be able to render `Wix
 
 ### Views
 
-When using  the data for the [views feature](./?path=/story/features-display-views--views) will be saved via the user-preferences API.
+When using  the data for the [views feature](Views.md) will be saved via the user-preferences API.
 If your app runs under a specific domain, you'll need too add a mapping to the `/user-preferences` endpoint of [app-settings-service artifact fryingpan dashboard](https://fryingpan.wixpress.com/services/com.wixpress.fed.app-settings-service)
 
 

package/dist/docs/WixPatternsProvider.md

@@ -12,11 +12,11 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 `WixPatternsProvider` is the recommended top-level provider for most Wix Patterns applications. It auto-detects the environment (BM, Essentials, Giza) and supplies the appropriate context. Wrap your entire app with this provider.
 
-> **Note: If you're using [Yoshi BM Flow](https://bo.wix.com/pages/yoshi/docs/business-manager-flow/overview) over Business-Manager, you can use [WixPatternsBMProvider](./?path=/story/base-components-providers--wixpatternsbmprovider) if you prefer.**
+> **Note: If you're using [Yoshi BM Flow](https://bo.wix.com/pages/yoshi/docs/business-manager-flow/overview) over Business-Manager, you can use [WixPatternsBMProvider](WixPatternsBMProvider.md) if you prefer.**
 
-> **Note: If you're using [Yoshi BM Flow](https://bo.wix.com/pages/yoshi/docs/business-manager-flow/overview) over Giza, you may choose to use [WixPatternsGizaProvider](./?path=/story/base-components-providers--wixpatternsgizaprovider) as an option.**
+> **Note: If you're using [Yoshi BM Flow](https://bo.wix.com/pages/yoshi/docs/business-manager-flow/overview) over Giza, you may choose to use [WixPatternsGizaProvider](WixPatternsGizaProvider.md) as an option.**
 
-> **Note: If you're using [Yoshi Fullstack](https://bo.wix.com/pages/yoshi/docs/fullstack-flow/overview), use [WixPatternsEssentialsProvider](./?path=/story/base-components-providers--wixpatternsessentialsprovider) instead.**
+> **Note: If you're using [Yoshi Fullstack](https://bo.wix.com/pages/yoshi/docs/fullstack-flow/overview), use [WixPatternsEssentialsProvider](WixPatternsEssentialsProvider.md) instead.**
 
 
 

package/dist/docs/arrayFilter.md

@@ -14,8 +14,8 @@ A generic filter factory that can be used with the `filters` property of the `us
 
 This is the base factory for the existing factories that we have:
 
-- [idNameArrayFilter](./?path=/story/features-filter-factories--idnamearrayfilter)
-- [stringsArrayFilter](./?path=/story/features-filter-factories--stringsarrayfilter)
+- [idNameArrayFilter](idNameArrayFilter.md)
+- [stringsArrayFilter](stringsArrayFilter.md)
 
 
 ```tsx

package/dist/docs/bulkActionModal.md

@@ -8,14 +8,14 @@ Examples below are illustrative: each one demonstrates this page's API, and ever
 
 ### Overview
 
-`bulkActionModal` is a render-prop passed to collection components (`Table`, `Grid`, `TableFolders`, etc.) that opens a custom modal when a bulk action is triggered from the [`MultiBulkActionToolbar`](./?path=/story/features-actions-bulk-actions--multibulkactiontoolbar).
+`bulkActionModal` is a render-prop passed to collection components (`Table`, `Grid`, `TableFolders`, etc.) that opens a custom modal when a bulk action is triggered from the [`MultiBulkActionToolbar`](MultiBulkActionToolbar.md).
 
 The render function receives:
 - `selectedValues` — the items selected via the checkbox column
 - `uncheckedValues` — the items that were unchecked (relevant when "Select All" is active)
 - `isSelectAll` — whether the "Select All" checkbox is checked
 - `closeModal` — closes the modal
-- `query` — a [`ComputedQuery`](./?path=/story/common-types--computedquery) representing the current paging, sorting, and filtering. Useful for server-side bulk operations like `updateAll` or `deleteAll`.
+- `query` — a [`ComputedQuery`](ComputedQuery.md) representing the current paging, sorting, and filtering. Useful for server-side bulk operations like `updateAll` or `deleteAll`.
 
 Return a React element (typically a `<MessageModalLayout>` or custom modal content) from the render function.