@vendure/docs 0.0.0-202601271334 → 0.0.0-202601281114

package/docs/guides/extending-the-admin-ui/getting-started/index.mdx

@@ -2,7 +2,7 @@
 title: 'Getting Started'
 ---
 
-:::warning Angular Admin UI Deprecation
+:::warning[Angular Admin UI Deprecation]
 The Angular-based Admin UI has been replaced by the new [React Admin Dashboard](/extending-the-dashboard/getting-started/). The Angular Admin UI will not be maintained after **July 2026**. 
 Until then, we will continue patching critical bugs and security issues. Community contributions will always be merged and released.
 

package/docs/guides/extending-the-dashboard/custom-form-components/index.mdx

@@ -254,7 +254,7 @@ operation argument.
 
 You can access validation data for the current field or the whole form by using the `useFormContext` hook.
 
-:::note Error Messages
+:::note[Error Messages]
 Your component does not need to handle standard error messages - the Dashboard will handle them for you.
 
 For example, if your custom field specifies a `pattern` property, the Dashboard will automatically display an error message
@@ -306,7 +306,7 @@ export const ValidatedInputComponent: DashboardFormComponent = ({ value, onChang
 }
 ```
 
-:::tip Best Practices
+:::tip[Best Practices]
 
 1. **Always use Shadcn UI components** from the `@vendure/dashboard` package for consistent styling
 2. **Handle React Hook Form events properly** - call `onChange` and `onBlur` appropriately for custom field components

package/docs/guides/extending-the-dashboard/customizing-pages/page-blocks.mdx

@@ -234,7 +234,7 @@ To find the `pageId` and `blockId` values for positioning your blocks:
 3. Hover over existing blocks to see their IDs
 4. Use these IDs in your block positioning configuration
 
-:::tip Best Practices
+:::tip[Best Practices]
 
 1. **Use descriptive IDs**: Choose clear, unique IDs for your blocks
 2. **Position thoughtfully**: Consider the user experience when placing blocks

package/docs/guides/extending-the-dashboard/deployment/index.mdx

@@ -51,7 +51,7 @@ export default defineConfig({
 
 ### 2. Add DashboardPlugin to Vendure Config
 
-:::info Angular Admin UI compatibility
+:::info[Angular Admin UI compatibility]
 If you want to use the Angular Admin UI and the Dashboard together, both plugins can now be used simultaneously without any special configuration.
 :::
 
@@ -151,7 +151,7 @@ export default defineConfig({
 });
 ```
 
-:::warning Build-Time Variables
+:::warning[Build-Time Variables]
 Environment variables are resolved at **build time** and embedded as static strings in the final bundles. Ensure these variables are available during the build process, not just at runtime.
 :::
 

package/docs/guides/extending-the-dashboard/getting-started/index.mdx

@@ -185,7 +185,7 @@ npx vite
 
 To stop the running dashboard, type `q` and hit enter.
 
-:::info Compatibility with the legacy Admin UI
+:::info[Compatibility with the legacy Admin UI]
 If you still need to run the legacy Angular-based Admin UI in parallel with the Dashboard,
 this is totally possible. Both plugins can now be used simultaneously without any special configuration.
 :::

package/docs/guides/extending-the-dashboard/navigation/index.mdx

@@ -158,7 +158,7 @@ Order values are scoped within each placement area. This means:
 
 This means if you want to add a section between Catalog and Sales in the top area, you might use `order: 250`. If you want to add a section before Settings in the bottom area, you could use `order: 150`.
 
-:::note Default Placement
+:::note[Default Placement]
 If you don't specify a `placement`, sections default to `'top'` placement.
 :::
 
@@ -311,7 +311,7 @@ Common icons for navigation sections:
 
 ## Best Practices
 
-:::tip Navigation Design Guidelines
+:::tip[Navigation Design Guidelines]
 
 1. **Use descriptive section names**: Choose clear, concise names that indicate the section's purpose
 2. **Group related functionality**: Keep logically related menu items in the same section

package/docs/guides/how-to/cms-integration-plugin/index.mdx

@@ -395,7 +395,7 @@ async findCollectionsForVariant(
 }
 ```
 
-:::info Additional Entity Types
+:::info[Additional Entity Types]
 The service can also includes `syncVariantToCms()` and `syncCollectionToCms()` methods that follow the same pattern as the product sync shown above.
 
 These implementations are omitted from this guide for brevity, but they handle their respective entity types with similar data fetching, relationship resolution, and error handling patterns.
@@ -410,7 +410,7 @@ This sync service provides the foundation for handling all Vendure-specific comp
 <Tabs>
 <TabItem value="storyblok" label="Storyblok">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Storyblok implementation can be found in the [Storyblok integration example](https://github.com/vendurehq/examples/tree/master/examples/storyblok-cms-integration). Refer to it for a minimal working implementation.
 :::
 
@@ -728,7 +728,7 @@ The complete implementations can be found in the working [example repositories](
 </TabItem>
 <TabItem value="contentful" label="Contentful">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Contentful implementation can be found in the [Contentful integration example](https://github.com/vendurehq/examples/tree/master/examples/contentful-cms-integration). It includes advanced features like locale mapping, bulk operations, and a robust setup process.
 :::
 
@@ -966,7 +966,7 @@ This same pattern is used to link variants to their parent product and to their
 
 These methods perform the core Create, Read, Update, and Delete logic. They rely on our centralized `makeContentfulRequest` method and handle the specifics of Contentful's API, such as versioning and the publish workflow.
 
-:::info Contentful's Publish Workflow
+:::info[Contentful's Publish Workflow]
 Contentful requires entries to be explicitly published before they are visible in the Delivery API. After creating or updating an entry, we must make a separate API call to publish it. Similarly, to delete an entry, it must first be unpublished.
 :::
 
@@ -1052,7 +1052,7 @@ This configuration provides a complete Contentful CMS integration that automatic
 
 <TabItem value="strapi" label="Strapi">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Strapi implementation can be found in the [Strapi integration example](https://github.com/vendurehq/examples/tree/master/examples/strapi-cms-integration). It includes advanced features like plugin-based content types, batch operations, and relationship management.
 :::
 
@@ -1382,7 +1382,7 @@ The complete implementations can be found in the working [example repositories](
 </TabItem>
 <TabItem value="Sanity" label="Sanity">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Sanity implementation can be found in the [Sanity integration example](https://github.com/vendurehq/examples/tree/master/examples/sanity-cms-integration). It includes advanced features like content type management and bulk operations.
 :::
 
@@ -1647,7 +1647,7 @@ https://github.com/vendurehq/examples/tree/master/examples/sanity-cms-integratio
 </TabItem>
 <TabItem value="payload" label="Payload">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Payload implementation can be found in the [Payload integration example](https://github.com/vendurehq/examples/tree/master/examples/payload-cms-integration). It includes advanced features like local API communication, collection management, and relationship handling.
 :::
 

package/docs/guides/how-to/codegen/index.mdx

@@ -153,7 +153,7 @@ export class OrganizationService {
 
 ## Codegen for Admin UI extensions
 
-:::warning Deprecated
+:::warning[Deprecated]
 This section refers to the deprecated Angular-based Admin UI. The new React-based Dashboard has built-in graphql type safety
 and does not require additional setup.
 :::

package/docs/reference/admin-ui-api/action-bar/action-bar-context.mdx

@@ -4,8 +4,8 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/providers/nav-builder/nav-builder-types.ts" sourceLine="90" packageName="@vendure/admin-ui" />
 
-Providers & data available to the `onClick` & `buttonState` functions of an <DocsLink href="/reference/admin-ui-api/action-bar/action-bar-item#actionbaritem">ActionBarItem</DocsLink>,
-<DocsLink href="/reference/admin-ui-api/action-bar/action-bar-dropdown-menu-item#actionbardropdownmenuitem">ActionBarDropdownMenuItem</DocsLink> or <DocsLink href="/reference/admin-ui-api/nav-menu/nav-menu-item#navmenuitem">NavMenuItem</DocsLink>.
+Providers & data available to the `onClick` & `buttonState` functions of an [ActionBarItem](/reference/admin-ui-api/action-bar/action-bar-item#actionbaritem),
+[ActionBarDropdownMenuItem](/reference/admin-ui-api/action-bar/action-bar-dropdown-menu-item#actionbardropdownmenuitem) or [NavMenuItem](/reference/admin-ui-api/nav-menu/nav-menu-item#navmenuitem).
 
 ```ts title="Signature"
 interface ActionBarContext {

package/docs/reference/admin-ui-api/action-bar/action-bar-dropdown-menu-item.mdx

@@ -71,7 +71,7 @@ set.
 <MemberInfo kind="property" type={`string | string[]`}   />
 
 Control the display of this item based on the user permissions. Note: if you attempt to pass a
-<DocsLink href="/reference/typescript-api/auth/permission-definition#permissiondefinition">PermissionDefinition</DocsLink> object, you will get a compilation error. Instead, pass the plain
+[PermissionDefinition](/reference/typescript-api/auth/permission-definition#permissiondefinition) object, you will get a compilation error. Instead, pass the plain
 string version. For example, if the permission is defined as:
 
 ```ts

package/docs/reference/admin-ui-api/action-bar/action-bar-item.mdx

@@ -83,7 +83,7 @@ set.
 <MemberInfo kind="property" type={`string | string[]`}   />
 
 Control the display of this item based on the user permissions. Note: if you attempt to pass a
-<DocsLink href="/reference/typescript-api/auth/permission-definition#permissiondefinition">PermissionDefinition</DocsLink> object, you will get a compilation error. Instead, pass the plain
+[PermissionDefinition](/reference/typescript-api/auth/permission-definition#permissiondefinition) object, you will get a compilation error. Instead, pass the plain
 string version. For example, if the permission is defined as:
 
 ```ts

package/docs/reference/admin-ui-api/action-bar/action-bar-location-id.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/common/component-registry-types.ts" sourceLine="107" packageName="@vendure/admin-ui" />
 
 The valid locationIds for registering action bar items. For a list of
-values, see <DocsLink href="/reference/admin-ui-api/action-bar/page-location-id#pagelocationid">PageLocationId</DocsLink>.
+values, see [PageLocationId](/reference/admin-ui-api/action-bar/page-location-id#pagelocationid).
 
 ```ts title="Signature"
 type ActionBarLocationId = PageLocationId

package/docs/reference/admin-ui-api/action-bar/router-link-definition.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/providers/nav-builder/nav-builder-types.ts" sourceLine="289" packageName="@vendure/admin-ui" />
 
-A function which returns the router link for an <DocsLink href="/reference/admin-ui-api/action-bar/action-bar-item#actionbaritem">ActionBarItem</DocsLink> or <DocsLink href="/reference/admin-ui-api/nav-menu/nav-menu-item#navmenuitem">NavMenuItem</DocsLink>.
+A function which returns the router link for an [ActionBarItem](/reference/admin-ui-api/action-bar/action-bar-item#actionbaritem) or [NavMenuItem](/reference/admin-ui-api/nav-menu/nav-menu-item#navmenuitem).
 
 ```ts title="Signature"
 type RouterLinkDefinition = ((route: ActivatedRoute, context: ActionBarContext) => any[]) | any[]

package/docs/reference/admin-ui-api/alerts/alert-context.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/providers/alerts/alerts.service.ts" sourceLine="29" packageName="@vendure/admin-ui" since="2.2.0" />
 
 The context object which is passed to the `check`, `isAlert`, `label` and `action` functions of an
-<DocsLink href="/reference/admin-ui-api/alerts/alert-config#alertconfig">AlertConfig</DocsLink> object.
+[AlertConfig](/reference/admin-ui-api/alerts/alert-config#alertconfig) object.
 
 ```ts title="Signature"
 interface AlertContext {

package/docs/reference/admin-ui-api/alerts/register-alert.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/extension/register-alert.ts" sourceLine="12" packageName="@vendure/admin-ui" since="2.2.0" />
 
 Registers an alert which can be displayed in the Admin UI alert dropdown in the top bar.
-The alert is configured using the <DocsLink href="/reference/admin-ui-api/alerts/alert-config#alertconfig">AlertConfig</DocsLink> object.
+The alert is configured using the [AlertConfig](/reference/admin-ui-api/alerts/alert-config#alertconfig) object.
 
 ```ts title="Signature"
 function registerAlert(config: AlertConfig): void

package/docs/reference/admin-ui-api/bulk-actions/bulk-action.mdx

@@ -6,7 +6,7 @@ generated: true
 
 Configures a bulk action which can be performed on all selected items in a list view.
 
-For a full example, see the <DocsLink href="/reference/admin-ui-api/bulk-actions/register-bulk-action#registerbulkaction">registerBulkAction</DocsLink> docs.
+For a full example, see the [registerBulkAction](/reference/admin-ui-api/bulk-actions/register-bulk-action#registerbulkaction) docs.
 
 ```ts title="Signature"
 interface BulkAction<ItemType = any, ComponentType = any> {
@@ -191,7 +191,7 @@ interface BulkActionClickContext<ItemType, ComponentType> extends BulkActionFunc
     event: MouseEvent;
 }
 ```
-* Extends: <DocsLink href="/reference/admin-ui-api/bulk-actions/bulk-action#bulkactionfunctioncontext">`BulkActionFunctionContext`</DocsLink>`<ItemType, ComponentType>`
+* Extends: [`BulkActionFunctionContext`](/reference/admin-ui-api/bulk-actions/bulk-action#bulkactionfunctioncontext)`<ItemType, ComponentType>`
 
 
 

package/docs/reference/admin-ui-api/bulk-actions/register-bulk-action.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/extension/register-bulk-action.ts" sourceLine="52" packageName="@vendure/admin-ui" since="1.8.0" />
 
-Registers a custom <DocsLink href="/reference/admin-ui-api/bulk-actions/bulk-action#bulkaction">BulkAction</DocsLink> which can be invoked from the bulk action menu
+Registers a custom [BulkAction](/reference/admin-ui-api/bulk-actions/bulk-action#bulkaction) which can be invoked from the bulk action menu
 of any supported list view.
 
 This allows you to provide custom functionality that can operate on any of the selected

package/docs/reference/admin-ui-api/components/asset-picker-dialog-component.mdx

@@ -49,7 +49,7 @@ class AssetPickerDialogComponent implements OnInit, AfterViewInit, OnDestroy, Di
     createAssets(files: File[]) => ;
 }
 ```
-* Implements: OnInit, AfterViewInit, OnDestroy, <DocsLink href="/reference/admin-ui-api/services/modal-service#dialog">`Dialog`</DocsLink>`<`<DocsLink href="/reference/typescript-api/entities/asset#asset">`Asset`</DocsLink>`[]>`
+* Implements: OnInit, AfterViewInit, OnDestroy, [`Dialog`](/reference/admin-ui-api/services/modal-service#dialog)`<`[`Asset`](/reference/typescript-api/entities/asset#asset)`[]>`
 
 
 

package/docs/reference/admin-ui-api/components/data-table-component.mdx

@@ -5,9 +5,9 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/shared/components/data-table/data-table.component.ts" sourceLine="86" packageName="@vendure/admin-ui" />
 
 A table for displaying PaginatedList results. It is designed to be used inside components which
-extend the <DocsLink href="/reference/admin-ui-api/list-detail-views/base-list-component#baselistcomponent">BaseListComponent</DocsLink> class.
+extend the [BaseListComponent](/reference/admin-ui-api/list-detail-views/base-list-component#baselistcomponent) class.
 
-**Deprecated** This component is deprecated. Use the <DocsLink href="/reference/admin-ui-api/components/data-table2component#datatable2component">DataTable2Component</DocsLink> instead.
+**Deprecated** This component is deprecated. Use the [DataTable2Component](/reference/admin-ui-api/components/data-table2component#datatable2component) instead.
 
 *Example*
 

package/docs/reference/admin-ui-api/components/data-table2component.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/shared/components/data-table-2/data-table2.component.ts" sourceLine="101" packageName="@vendure/admin-ui" />
 
 A table for displaying PaginatedList results. It is designed to be used inside components which
-extend the <DocsLink href="/reference/admin-ui-api/list-detail-views/base-list-component#baselistcomponent">BaseListComponent</DocsLink> or <DocsLink href="/reference/admin-ui-api/list-detail-views/typed-base-list-component#typedbaselistcomponent">TypedBaseListComponent</DocsLink> class.
+extend the [BaseListComponent](/reference/admin-ui-api/list-detail-views/base-list-component#baselistcomponent) or [TypedBaseListComponent](/reference/admin-ui-api/list-detail-views/typed-base-list-component#typedbaselistcomponent) class.
 
 *Example*
 

package/docs/reference/admin-ui-api/custom-detail-components/custom-detail-component-config.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/providers/custom-detail-component/custom-detail-component-types.ts" sourceLine="25" packageName="@vendure/admin-ui" />
 
-Configures a <DocsLink href="/reference/admin-ui-api/custom-detail-components/custom-detail-component#customdetailcomponent">CustomDetailComponent</DocsLink> to be placed in the given location.
+Configures a [CustomDetailComponent](/reference/admin-ui-api/custom-detail-components/custom-detail-component#customdetailcomponent) to be placed in the given location.
 
 ```ts title="Signature"
 interface CustomDetailComponentConfig {

package/docs/reference/admin-ui-api/custom-detail-components/custom-detail-component-location-id.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/common/component-registry-types.ts" sourceLine="115" packageName="@vendure/admin-ui" />
 
-The valid locations for embedding a <DocsLink href="/reference/admin-ui-api/custom-detail-components/custom-detail-component#customdetailcomponent">CustomDetailComponent</DocsLink>.
+The valid locations for embedding a [CustomDetailComponent](/reference/admin-ui-api/custom-detail-components/custom-detail-component#customdetailcomponent).
 
 ```ts title="Signature"
 type CustomDetailComponentLocationId = | 'administrator-profile'

package/docs/reference/admin-ui-api/custom-detail-components/register-custom-detail-component.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/extension/register-custom-detail-component.ts" sourceLine="57" packageName="@vendure/admin-ui" />
 
-Registers a <DocsLink href="/reference/admin-ui-api/custom-detail-components/custom-detail-component#customdetailcomponent">CustomDetailComponent</DocsLink> to be placed in a given location. This allows you
+Registers a [CustomDetailComponent](/reference/admin-ui-api/custom-detail-components/custom-detail-component#customdetailcomponent) to be placed in a given location. This allows you
 to embed any type of custom Angular component in the entity detail pages of the Admin UI.
 
 *Example*

package/docs/reference/admin-ui-api/custom-history-entry-components/customer-history-entry-component.mdx

@@ -4,14 +4,14 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/providers/custom-history-entry-component/history-entry-component-types.ts" sourceLine="64" packageName="@vendure/admin-ui" since="1.9.0" />
 
-Used to implement a <DocsLink href="/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent">HistoryEntryComponent</DocsLink> which requires access to the Customer object.
+Used to implement a [HistoryEntryComponent](/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent) which requires access to the Customer object.
 
 ```ts title="Signature"
 interface CustomerHistoryEntryComponent extends HistoryEntryComponent {
     customer: CustomerFragment;
 }
 ```
-* Extends: <DocsLink href="/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent">`HistoryEntryComponent`</DocsLink>
+* Extends: [`HistoryEntryComponent`](/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent)
 
 
 

package/docs/reference/admin-ui-api/custom-history-entry-components/history-entry-component.mdx

@@ -6,7 +6,7 @@ generated: true
 
 This interface should be implemented by components intended to display a history entry in the
 Order or Customer history timeline. If the component needs access to the Order or Customer object itself,
-you should implement <DocsLink href="/reference/admin-ui-api/custom-history-entry-components/order-history-entry-component#orderhistoryentrycomponent">OrderHistoryEntryComponent</DocsLink> or <DocsLink href="/reference/admin-ui-api/custom-history-entry-components/customer-history-entry-component#customerhistoryentrycomponent">CustomerHistoryEntryComponent</DocsLink> respectively.
+you should implement [OrderHistoryEntryComponent](/reference/admin-ui-api/custom-history-entry-components/order-history-entry-component#orderhistoryentrycomponent) or [CustomerHistoryEntryComponent](/reference/admin-ui-api/custom-history-entry-components/customer-history-entry-component#customerhistoryentrycomponent) respectively.
 
 ```ts title="Signature"
 interface HistoryEntryComponent {

package/docs/reference/admin-ui-api/custom-history-entry-components/history-entry-config.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/providers/custom-history-entry-component/history-entry-component-types.ts" sourceLine="75" packageName="@vendure/admin-ui" since="1.9.0" />
 
-Configuration for registering a custom <DocsLink href="/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent">HistoryEntryComponent</DocsLink>.
+Configuration for registering a custom [HistoryEntryComponent](/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent).
 
 ```ts title="Signature"
 interface HistoryEntryConfig {

package/docs/reference/admin-ui-api/custom-history-entry-components/order-history-entry-component.mdx

@@ -4,14 +4,14 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/providers/custom-history-entry-component/history-entry-component-types.ts" sourceLine="53" packageName="@vendure/admin-ui" since="1.9.0" />
 
-Used to implement a <DocsLink href="/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent">HistoryEntryComponent</DocsLink> which requires access to the Order object.
+Used to implement a [HistoryEntryComponent](/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent) which requires access to the Order object.
 
 ```ts title="Signature"
 interface OrderHistoryEntryComponent extends HistoryEntryComponent {
     order: OrderDetailFragment;
 }
 ```
-* Extends: <DocsLink href="/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent">`HistoryEntryComponent`</DocsLink>
+* Extends: [`HistoryEntryComponent`](/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent)
 
 
 

package/docs/reference/admin-ui-api/custom-history-entry-components/register-history-entry-component.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/extension/register-history-entry-component.ts" sourceLine="68" packageName="@vendure/admin-ui" since="1.9.0" />
 
-Registers a <DocsLink href="/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent">HistoryEntryComponent</DocsLink> for displaying history entries in the Order/Customer
+Registers a [HistoryEntryComponent](/reference/admin-ui-api/custom-history-entry-components/history-entry-component#historyentrycomponent) for displaying history entries in the Order/Customer
 history timeline.
 
 *Example*

package/docs/reference/admin-ui-api/custom-input-components/default-inputs.mdx

@@ -14,7 +14,7 @@ class BooleanFormInputComponent implements FormInputComponent {
     config: DefaultFormComponentConfig<'boolean-form-input'>;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -58,7 +58,7 @@ class HtmlEditorFormInputComponent extends BaseCodeEditorFormInputComponent impl
 * Extends: BaseCodeEditorFormInputComponent
 
 
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>, AfterViewInit, OnInit
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent), AfterViewInit, OnInit
 
 
 
@@ -97,7 +97,7 @@ class JsonEditorFormInputComponent extends BaseCodeEditorFormInputComponent impl
 * Extends: BaseCodeEditorFormInputComponent
 
 
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>, AfterViewInit, OnInit
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent), AfterViewInit, OnInit
 
 
 
@@ -138,7 +138,7 @@ class CombinationModeFormInputComponent implements FormInputComponent, OnInit {
     setCombinationModeOr() => ;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>, OnInit
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent), OnInit
 
 
 
@@ -206,7 +206,7 @@ class CurrencyFormInputComponent implements FormInputComponent {
     constructor(dataService: DataService)
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -263,7 +263,7 @@ class CustomerGroupFormInputComponent implements FormInputComponent, OnInit {
     compareWith(o1: T, o2: T) => ;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>, OnInit
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent), OnInit
 
 
 
@@ -332,7 +332,7 @@ class DateFormInputComponent implements FormInputComponent {
     yearRange: void
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -398,7 +398,7 @@ class FacetValueFormInputComponent implements FormInputComponent {
     };
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -454,7 +454,7 @@ class NumberFormInputComponent implements FormInputComponent {
     step: void
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -520,7 +520,7 @@ class PasswordFormInputComponent implements FormInputComponent {
     config: InputComponentConfig;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -568,7 +568,7 @@ class ProductSelectorFormInputComponent implements FormInputComponent, OnInit {
     removeProductVariant(id: string) => ;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>, OnInit
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent), OnInit
 
 
 
@@ -631,7 +631,7 @@ class ProductSelectorFormInputComponent implements FormInputComponent, OnInit {
 
 The default input component for `relation` type custom fields. Allows the selection
 of a ProductVariant, Product, Customer or Asset. For other entity types, a custom
-implementation will need to be defined. See <DocsLink href="/reference/admin-ui-api/custom-input-components/register-form-input-component#registerforminputcomponent">registerFormInputComponent</DocsLink>.
+implementation will need to be defined. See [registerFormInputComponent](/reference/admin-ui-api/custom-input-components/register-form-input-component#registerforminputcomponent).
 
 ```ts title="Signature"
 class RelationFormInputComponent implements FormInputComponent {
@@ -641,7 +641,7 @@ class RelationFormInputComponent implements FormInputComponent {
     config: RelationCustomFieldConfig;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -672,7 +672,7 @@ class RelationFormInputComponent implements FormInputComponent {
 </div>
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/shared/dynamic-form-inputs/rich-text-form-input/rich-text-form-input.component.ts" sourceLine="14" packageName="@vendure/admin-ui" />
 
-Uses the <DocsLink href="/reference/admin-ui-api/components/rich-text-editor-component#richtexteditorcomponent">RichTextEditorComponent</DocsLink> as in input for `text` type fields.
+Uses the [RichTextEditorComponent](/reference/admin-ui-api/components/rich-text-editor-component#richtexteditorcomponent) as in input for `text` type fields.
 
 ```ts title="Signature"
 class RichTextFormInputComponent implements FormInputComponent {
@@ -682,7 +682,7 @@ class RichTextFormInputComponent implements FormInputComponent {
     config: DefaultFormComponentConfig<'rich-text-form-input'>;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -729,7 +729,7 @@ class SelectFormInputComponent implements FormInputComponent, OnInit {
     trackByFn(index: number, item: any) => ;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>, OnInit
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent), OnInit
 
 
 
@@ -804,7 +804,7 @@ class StructFormInputComponent implements FormInputComponent, OnInit, OnDestroy
     ngOnDestroy() => ;
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>, OnInit, OnDestroy
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent), OnInit, OnDestroy
 
 
 
@@ -877,7 +877,7 @@ class TextFormInputComponent implements FormInputComponent {
     suffix: void
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 
@@ -929,7 +929,7 @@ class TextareaFormInputComponent implements FormInputComponent {
     spellcheck: boolean
 }
 ```
-* Implements: <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">`FormInputComponent`</DocsLink>
+* Implements: [`FormInputComponent`](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent)
 
 
 

package/docs/reference/admin-ui-api/custom-input-components/register-form-input-component.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/extension/register-form-input-component.ts" sourceLine="53" packageName="@vendure/admin-ui" />
 
 Registers a custom FormInputComponent which can be used to control the argument inputs
-of a <DocsLink href="/reference/typescript-api/configurable-operation-def/#configurableoperationdef">ConfigurableOperationDef</DocsLink> (e.g. CollectionFilter, ShippingMethod etc.) or for
+of a [ConfigurableOperationDef](/reference/typescript-api/configurable-operation-def/#configurableoperationdef) (e.g. CollectionFilter, ShippingMethod etc.) or for
 a custom field.
 
 *Example*
@@ -41,7 +41,7 @@ const config: VendureConfig = {
 }
 ```
 
-or with an argument of a <DocsLink href="/reference/typescript-api/configurable-operation-def/#configurableoperationdef">ConfigurableOperationDef</DocsLink>:
+or with an argument of a [ConfigurableOperationDef](/reference/typescript-api/configurable-operation-def/#configurableoperationdef):
 
 *Example*
 

package/docs/reference/admin-ui-api/custom-table-components/data-table-component-config.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/shared/components/data-table-2/data-table-custom-component.service.ts" sourceLine="54" packageName="@vendure/admin-ui" />
 
-Configures a <DocsLink href="/reference/admin-ui-api/custom-detail-components/custom-detail-component#customdetailcomponent">CustomDetailComponent</DocsLink> to be placed in the given location.
+Configures a [CustomDetailComponent](/reference/admin-ui-api/custom-detail-components/custom-detail-component#customdetailcomponent) to be placed in the given location.
 
 ```ts title="Signature"
 interface DataTableComponentConfig {
@@ -32,7 +32,7 @@ The column in the table where the custom component should be placed.
 <MemberInfo kind="property" type={`Type<<a href='/reference/admin-ui-api/custom-table-components/custom-column-component#customcolumncomponent'>CustomColumnComponent</a>>`}   />
 
 The component to render in the table cell. This component should implement the
-<DocsLink href="/reference/admin-ui-api/custom-table-components/custom-column-component#customcolumncomponent">CustomColumnComponent</DocsLink> interface.
+[CustomColumnComponent](/reference/admin-ui-api/custom-table-components/custom-column-component#customcolumncomponent) interface.
 ### providers
 
 <MemberInfo kind="property" type={`Provider[]`}   />

package/docs/reference/admin-ui-api/custom-table-components/register-data-table-component.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/extension/register-data-table-component.ts" sourceLine="45" packageName="@vendure/admin-ui" />
 
 Allows you to override the default component used to render the data of a particular column in a DataTable.
-The component should implement the <DocsLink href="/reference/admin-ui-api/custom-table-components/custom-column-component#customcolumncomponent">CustomColumnComponent</DocsLink> interface. The tableId and columnId can
+The component should implement the [CustomColumnComponent](/reference/admin-ui-api/custom-table-components/custom-column-component#customcolumncomponent) interface. The tableId and columnId can
 be determined by pressing `ctrl + u` when running the Admin UI in dev mode.
 
 *Example*