fix(docs): Replace DocsLink components with standard markdown links

The DocsLink component was causing MDX parsing issues. This change
modifies the documentation generator to output standard markdown
link syntax instead of DocsLink components for both heritage clauses
(extends/implements) and @link JSDoc references.

docs/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 {

docs/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

docs/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

docs/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

docs/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[]

docs/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 {

docs/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

docs/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>`
 
 
 

docs/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

docs/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)`[]>`
 
 
 

docs/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*
 

docs/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*
 

docs/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 {

docs/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'

docs/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*

docs/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)
 
 
 

docs/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 {

docs/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 {

docs/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)
 
 
 

docs/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*

docs/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)
 
 
 

docs/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*
 

docs/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[]`}   />

docs/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*

docs/docs/reference/admin-ui-api/dashboard-widgets/register-dashboard-widget.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/extension/register-dashboard-widget.ts" sourceLine="16" packageName="@vendure/admin-ui" />
 
 Registers a dashboard widget. Once registered, the widget can be set as part of the default
-(using <DocsLink href="/reference/admin-ui-api/dashboard-widgets/set-dashboard-widget-layout#setdashboardwidgetlayout">setDashboardWidgetLayout</DocsLink>).
+(using [setDashboardWidgetLayout](/reference/admin-ui-api/dashboard-widgets/set-dashboard-widget-layout#setdashboardwidgetlayout)).
 
 ```ts title="Signature"
 function registerDashboardWidget(id: string, config: DashboardWidgetConfig): void

docs/docs/reference/admin-ui-api/directives/if-permissions-directive.mdx

@@ -22,7 +22,7 @@ class IfPermissionsDirective extends IfDirectiveBase<Array<Permission[] | null>>
     constructor(_viewContainer: ViewContainerRef, templateRef: TemplateRef<any>, changeDetectorRef: ChangeDetectorRef, permissionsService: PermissionsService)
 }
 ```
-* Extends: `IfDirectiveBase<Array<`<DocsLink href="/reference/typescript-api/common/permission#permission">`Permission`</DocsLink>`[] | null>>`
+* Extends: `IfDirectiveBase<Array<`[`Permission`](/reference/typescript-api/common/permission#permission)`[] | null>>`
 
 
 

docs/docs/reference/admin-ui-api/list-detail-views/base-detail-component.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/common/base-detail.component.ts" sourceLine="57" packageName="@vendure/admin-ui" />
 
 A base class for entity detail views. It should be used in conjunction with the
-<DocsLink href="/reference/admin-ui-api/list-detail-views/base-entity-resolver#baseentityresolver">BaseEntityResolver</DocsLink>.
+[BaseEntityResolver](/reference/admin-ui-api/list-detail-views/base-entity-resolver#baseentityresolver).
 
 *Example*
 

docs/docs/reference/admin-ui-api/list-detail-views/base-entity-resolver.mdx

@@ -6,7 +6,7 @@ generated: true
 
 A base resolver for an entity detail route. Resolves to an observable of the given entity, or a "blank"
 version if the route id equals "create". Should be used together with details views which extend the
-<DocsLink href="/reference/admin-ui-api/list-detail-views/base-detail-component#basedetailcomponent">BaseDetailComponent</DocsLink>.
+[BaseDetailComponent](/reference/admin-ui-api/list-detail-views/base-detail-component#basedetailcomponent).
 
 *Example*
 

docs/docs/reference/admin-ui-api/list-detail-views/base-list-component.mdx

@@ -7,7 +7,7 @@ generated: true
 This is a base class which implements the logic required to fetch and manipulate
 a list of data from a query which returns a PaginatedList type.
 
-It is normally used in combination with the <DocsLink href="/reference/admin-ui-api/components/data-table2component#datatable2component">DataTable2Component</DocsLink>.
+It is normally used in combination with the [DataTable2Component](/reference/admin-ui-api/components/data-table2component#datatable2component).
 
 ```ts title="Signature"
 class BaseListComponent<ResultType, ItemType, VariableType extends Record<string, any> = any> implements OnInit, OnDestroy {

docs/docs/reference/admin-ui-api/list-detail-views/detail-component-with-resolver.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/common/base-detail.component.ts" sourceLine="256" packageName="@vendure/admin-ui" />
 
-A helper function for creating tabs that point to a <DocsLink href="/reference/admin-ui-api/list-detail-views/typed-base-detail-component#typedbasedetailcomponent">TypedBaseDetailComponent</DocsLink>. This takes
+A helper function for creating tabs that point to a [TypedBaseDetailComponent](/reference/admin-ui-api/list-detail-views/typed-base-detail-component#typedbasedetailcomponent). This takes
 care of the route resolver parts so that the detail component automatically has access to the
 correct resolved detail data.
 

docs/docs/reference/admin-ui-api/list-detail-views/typed-base-detail-component.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/common/base-detail.component.ts" sourceLine="186" packageName="@vendure/admin-ui" />
 
-A version of the <DocsLink href="/reference/admin-ui-api/list-detail-views/base-detail-component#basedetailcomponent">BaseDetailComponent</DocsLink> which is designed to be used with a
+A version of the [BaseDetailComponent](/reference/admin-ui-api/list-detail-views/base-detail-component#basedetailcomponent) which is designed to be used with a
 [TypedDocumentNode](https://the-guild.dev/graphql/codegen/plugins/typescript/typed-document-node).
 
 ```ts title="Signature"
@@ -15,7 +15,7 @@ class TypedBaseDetailComponent<T extends TypedDocumentNode<any, any>, Field exte
     init() => ;
 }
 ```
-* Extends: <DocsLink href="/reference/admin-ui-api/list-detail-views/base-detail-component#basedetailcomponent">`BaseDetailComponent`</DocsLink>`<NonNullable<ResultOf<T>[Field]>>`
+* Extends: [`BaseDetailComponent`](/reference/admin-ui-api/list-detail-views/base-detail-component#basedetailcomponent)`<NonNullable<ResultOf<T>[Field]>>`
 
 
 

docs/docs/reference/admin-ui-api/list-detail-views/typed-base-list-component.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/core/src/common/base-list.component.ts" sourceLine="217" packageName="@vendure/admin-ui" />
 
-A version of the <DocsLink href="/reference/admin-ui-api/list-detail-views/base-list-component#baselistcomponent">BaseListComponent</DocsLink> which is designed to be used with a
+A version of the [BaseListComponent](/reference/admin-ui-api/list-detail-views/base-list-component#baselistcomponent) which is designed to be used with a
 [TypedDocumentNode](https://the-guild.dev/graphql/codegen/plugins/typescript/typed-document-node).
 
 ```ts title="Signature"
@@ -31,7 +31,7 @@ class TypedBaseListComponent<T extends TypedDocumentNode<any, Vars>, Field exten
     getCustomFieldConfig(key: Exclude<keyof CustomFields, '__typename'> | string) => CustomFieldConfig[];
 }
 ```
-* Extends: <DocsLink href="/reference/admin-ui-api/list-detail-views/base-list-component#baselistcomponent">`BaseListComponent`</DocsLink>`<ResultOf<T>, ItemOf<ResultOf<T>, Field>, VariablesOf<T>>`
+* Extends: [`BaseListComponent`](/reference/admin-ui-api/list-detail-views/base-list-component#baselistcomponent)`<ResultOf<T>, ItemOf<ResultOf<T>, Field>, VariablesOf<T>>`
 
 
 * Implements: OnInit

docs/docs/reference/admin-ui-api/nav-menu/nav-menu-section.mdx

@@ -52,7 +52,7 @@ interface NavMenuSection {
 <MemberInfo kind="property" type={`string | ((userPermissions: string[]) => boolean)`}   />
 
 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
 export const MyPermission = new PermissionDefinition('ProductReview');

docs/docs/reference/admin-ui-api/react-extensions/react-data-table-component-config.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/react/src/register-react-data-table-component.ts" sourceLine="19" 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 ReactDataTableComponentConfig {

docs/docs/reference/admin-ui-api/react-extensions/register-react-custom-detail-component.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/react/src/register-react-custom-detail-component.ts" sourceLine="40" packageName="@vendure/admin-ui" />
 
 Registers a React component to be rendered in a detail page in the given location.
-Components used as custom detail components can make use of the <DocsLink href="/reference/admin-ui-api/react-hooks/use-detail-component-data#usedetailcomponentdata">useDetailComponentData</DocsLink> hook.
+Components used as custom detail components can make use of the [useDetailComponentData](/reference/admin-ui-api/react-hooks/use-detail-component-data#usedetailcomponentdata) hook.
 
 ```ts title="Signature"
 function registerReactCustomDetailComponent(config: ReactCustomDetailComponentConfig): void

docs/docs/reference/admin-ui-api/react-extensions/register-react-form-input-component.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui/src/lib/react/src/register-react-form-input-component.ts" sourceLine="15" packageName="@vendure/admin-ui" />
 
-Registers a React component to be used as a <DocsLink href="/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent">FormInputComponent</DocsLink>.
+Registers a React component to be used as a [FormInputComponent](/reference/admin-ui-api/custom-input-components/form-input-component#forminputcomponent).
 
 ```ts title="Signature"
 function registerReactFormInputComponent(id: string, component: ElementType): void

docs/docs/reference/admin-ui-api/services/data-service.mdx

@@ -22,7 +22,7 @@ class DataService {
 
 <MemberInfo kind="method" type={`(query: DocumentNode | TypedDocumentNode<T, V>, variables?: V, fetchPolicy: WatchQueryFetchPolicy = 'cache-and-network', options: ExtendedQueryOptions = {}) => <a href='/reference/admin-ui-api/services/data-service#queryresult'>QueryResult</a><T, V>`}   />
 
-Perform a GraphQL query. Returns a <DocsLink href="/reference/admin-ui-api/services/data-service#queryresult">QueryResult</DocsLink> which allows further control over
+Perform a GraphQL query. Returns a [QueryResult](/reference/admin-ui-api/services/data-service#queryresult) which allows further control over
 they type of result returned, e.g. stream of values, single value etc.
 
 *Example*

docs/docs/reference/admin-ui-api/services/modal-service.mdx

@@ -26,7 +26,7 @@ class ModalService {
 
 <MemberInfo kind="method" type={`(component: Type<T> &#38; Type<<a href='/reference/admin-ui-api/services/modal-service#dialog'>Dialog</a><R>>, options?: <a href='/reference/admin-ui-api/services/modal-service#modaloptions'>ModalOptions</a><T>) => Observable<R | undefined>`}   />
 
-Create a modal from a component. The component must implement the <DocsLink href="/reference/admin-ui-api/services/modal-service#dialog">Dialog</DocsLink> interface.
+Create a modal from a component. The component must implement the [Dialog](/reference/admin-ui-api/services/modal-service#dialog) interface.
 Additionally, the component should include templates for the title and the buttons to be
 displayed in the modal dialog. See example:
 

docs/docs/reference/admin-ui-api/ui-devkit/admin-ui-extension.mdx

@@ -12,9 +12,7 @@ See [Extending the Admin UI](/extending-the-admin-ui/getting-started/) for
 detailed instructions.
 
 ```ts title="Signature"
-interface AdminUiExtension extends Partial<TranslationExtension>,
-        Partial<StaticAssetExtension>,
-        Partial<GlobalStylesExtension> {
+interface AdminUiExtension extends Partial<TranslationExtension>, Partial<StaticAssetExtension>, Partial<GlobalStylesExtension> {
     id?: string;
     extensionPath: string;
     ngModules?: Array<AdminUiExtensionSharedModule | AdminUiExtensionLazyModule>;
@@ -24,7 +22,7 @@ interface AdminUiExtension extends Partial<TranslationExtension>,
     exclude?: string[];
 }
 ```
-* Extends: `Partial<`<DocsLink href="/reference/admin-ui-api/ui-devkit/admin-ui-extension#translationextension">`TranslationExtension`</DocsLink>`>`, `Partial<`<DocsLink href="/reference/admin-ui-api/ui-devkit/admin-ui-extension#staticassetextension">`StaticAssetExtension`</DocsLink>`>`, `Partial<`<DocsLink href="/reference/admin-ui-api/ui-devkit/admin-ui-extension#globalstylesextension">`GlobalStylesExtension`</DocsLink>`>`
+* Extends: `Partial<`[`TranslationExtension`](/reference/admin-ui-api/ui-devkit/admin-ui-extension#translationextension)`>`, `Partial<`[`StaticAssetExtension`](/reference/admin-ui-api/ui-devkit/admin-ui-extension#staticassetextension)`>`, `Partial<`[`GlobalStylesExtension`](/reference/admin-ui-api/ui-devkit/admin-ui-extension#globalstylesextension)`>`
 
 
 
@@ -165,7 +163,7 @@ exclude: ['**/*.spec.ts']
 <GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="18" packageName="@vendure/ui-devkit" />
 
 Defines extensions to the Admin UI translations. Can be used as a stand-alone extension definition which only adds translations
-without adding new UI functionality, or as part of a full <DocsLink href="/reference/admin-ui-api/ui-devkit/admin-ui-extension#adminuiextension">AdminUiExtension</DocsLink>.
+without adding new UI functionality, or as part of a full [AdminUiExtension](/reference/admin-ui-api/ui-devkit/admin-ui-extension#adminuiextension).
 
 ```ts title="Signature"
 interface TranslationExtension {
@@ -295,7 +293,7 @@ This is useful when the extension is intended to replace the default Admin UI, r
 
 
 </div>
-<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="280" packageName="@vendure/ui-devkit" />
+<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="278" packageName="@vendure/ui-devkit" />
 
 A static asset can be provided as a path to the asset, or as an object containing a path and a new
 name, which will cause the compiler to copy and then rename the asset.
@@ -303,7 +301,7 @@ name, which will cause the compiler to copy and then rename the asset.
 ```ts title="Signature"
 type StaticAssetDefinition = string | { path: string; rename: string }
 ```
-<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="289" packageName="@vendure/ui-devkit" />
+<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="287" packageName="@vendure/ui-devkit" />
 
 Configuration defining a single NgModule with which to extend the Admin UI.
 
@@ -337,7 +335,7 @@ The name of the extension module class.
 
 
 </div>
-<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="316" packageName="@vendure/ui-devkit" />
+<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="314" packageName="@vendure/ui-devkit" />
 
 Configuration defining a single NgModule with which to extend the Admin UI.
 

docs/docs/reference/admin-ui-api/ui-devkit/ui-extension-build-command.mdx

@@ -2,7 +2,7 @@
 title: "UiExtensionBuildCommand"
 generated: true
 ---
-<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="356" packageName="@vendure/ui-devkit" />
+<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="354" packageName="@vendure/ui-devkit" />
 
 The package manager to use when invoking the Angular CLI to build UI extensions.
 

docs/docs/reference/admin-ui-api/ui-devkit/ui-extension-compiler-options.mdx

@@ -2,7 +2,7 @@
 title: "UiExtensionCompilerOptions"
 generated: true
 ---
-<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="364" packageName="@vendure/ui-devkit" />
+<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="362" packageName="@vendure/ui-devkit" />
 
 Options to configure how the Admin UI should be compiled.
 
@@ -68,7 +68,7 @@ Allows the baseHref of the compiled Admin UI app to be set. This determines the
 of the app, for example with the default value of `'/admin/'`, the Admin UI app
 will be configured to be served from `http://<host>/admin/`.
 
-Note: if you are using this in conjunction with the <DocsLink href="/reference/core-plugins/admin-ui-plugin/#adminuiplugin">AdminUiPlugin</DocsLink> then you should
+Note: if you are using this in conjunction with the [AdminUiPlugin](/reference/core-plugins/admin-ui-plugin/#adminuiplugin) then you should
 also set the `route` option to match this value.
 
 *Example*

docs/docs/reference/admin-ui-api/ui-devkit/ui-extension-compiler-process-argument.mdx

@@ -2,7 +2,7 @@
 title: "UiExtensionCompilerProcessArgument"
 generated: true
 ---
-<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="348" packageName="@vendure/ui-devkit" />
+<GenerationInfo sourceFile="packages/ui-devkit/src/compiler/types.ts" sourceLine="346" packageName="@vendure/ui-devkit" />
 
 Argument to configure process (watch or compile)
 

docs/docs/reference/core-plugins/admin-ui-plugin/admin-ui-plugin-options.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui-plugin/src/plugin.ts" sourceLine="44" packageName="@vendure/admin-ui-plugin" />
 
-Configuration options for the <DocsLink href="/reference/core-plugins/admin-ui-plugin/#adminuiplugin">AdminUiPlugin</DocsLink>.
+Configuration options for the [AdminUiPlugin](/reference/core-plugins/admin-ui-plugin/#adminuiplugin).
 
 ```ts title="Signature"
 interface AdminUiPluginOptions {

docs/docs/reference/core-plugins/admin-ui-plugin/index.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui-plugin/src/plugin.ts" sourceLine="147" packageName="@vendure/admin-ui-plugin" />
 
-:::warning[Deprecated]
+:::warning Deprecated
 From Vendure v3.5.0, 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.

docs/docs/reference/core-plugins/asset-server-plugin/asset-server-options.mdx

@@ -35,7 +35,7 @@ The route to the asset server.
 
 <MemberInfo kind="property" type={`string`}   />
 
-The local directory to which assets will be uploaded when using the <DocsLink href="/reference/core-plugins/asset-server-plugin/local-asset-storage-strategy#localassetstoragestrategy">LocalAssetStorageStrategy</DocsLink>.
+The local directory to which assets will be uploaded when using the [LocalAssetStorageStrategy](/reference/core-plugins/asset-server-plugin/local-asset-storage-strategy#localassetstoragestrategy).
 ### assetUrlPrefix
 
 <MemberInfo kind="property" type={`string | ((ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>, identifier: string) => string)`}   />
@@ -61,7 +61,7 @@ The max height in pixels of a generated preview image.
 
 <MemberInfo kind="property" type={`<a href='/reference/core-plugins/asset-server-plugin/image-transform-preset#imagetransformpreset'>ImageTransformPreset</a>[]`}   />
 
-An array of additional <DocsLink href="/reference/core-plugins/asset-server-plugin/image-transform-preset#imagetransformpreset">ImageTransformPreset</DocsLink> objects.
+An array of additional [ImageTransformPreset](/reference/core-plugins/asset-server-plugin/image-transform-preset#imagetransformpreset) objects.
 ### imageTransformStrategy
 
 <MemberInfo kind="property" type={`<a href='/reference/core-plugins/asset-server-plugin/image-transform-strategy#imagetransformstrategy'>ImageTransformStrategy</a> | <a href='/reference/core-plugins/asset-server-plugin/image-transform-strategy#imagetransformstrategy'>ImageTransformStrategy</a>[]`} default={`[]`}  since="3.1.0"  />
@@ -83,13 +83,13 @@ Defines how asset files and preview images are named before being saved.
 <MemberInfo kind="property" type={`<a href='/reference/typescript-api/assets/asset-preview-strategy#assetpreviewstrategy'>AssetPreviewStrategy</a>`}  since="1.7.0"  />
 
 Defines how previews are generated for a given Asset binary. By default, this uses
-the <DocsLink href="/reference/core-plugins/asset-server-plugin/sharp-asset-preview-strategy#sharpassetpreviewstrategy">SharpAssetPreviewStrategy</DocsLink>
+the [SharpAssetPreviewStrategy](/reference/core-plugins/asset-server-plugin/sharp-asset-preview-strategy#sharpassetpreviewstrategy)
 ### storageStrategyFactory
 
 <MemberInfo kind="property" type={`(         options: <a href='/reference/core-plugins/asset-server-plugin/asset-server-options#assetserveroptions'>AssetServerOptions</a>,     ) => <a href='/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy'>AssetStorageStrategy</a> | Promise<<a href='/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy'>AssetStorageStrategy</a>>`} default={`() => <a href='/reference/core-plugins/asset-server-plugin/local-asset-storage-strategy#localassetstoragestrategy'>LocalAssetStorageStrategy</a>`}   />
 
-A function which can be used to configure an <DocsLink href="/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy">AssetStorageStrategy</DocsLink>. This is useful e.g. if you wish to store your assets
-using a cloud storage provider. By default, the <DocsLink href="/reference/core-plugins/asset-server-plugin/local-asset-storage-strategy#localassetstoragestrategy">LocalAssetStorageStrategy</DocsLink> is used.
+A function which can be used to configure an [AssetStorageStrategy](/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy). This is useful e.g. if you wish to store your assets
+using a cloud storage provider. By default, the [LocalAssetStorageStrategy](/reference/core-plugins/asset-server-plugin/local-asset-storage-strategy#localassetstoragestrategy) is used.
 ### cacheHeader
 
 <MemberInfo kind="property" type={`<a href='/reference/core-plugins/asset-server-plugin/cache-config#cacheconfig'>CacheConfig</a> | string`} default={`'public, max-age=15552000'`}  since="1.9.3"  />

docs/docs/reference/core-plugins/asset-server-plugin/hashed-asset-naming-strategy.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/asset-server-plugin/src/config/hashed-asset-naming-strategy.ts" sourceLine="20" packageName="@vendure/asset-server-plugin" />
 
-An extension of the <DocsLink href="/reference/typescript-api/assets/default-asset-naming-strategy#defaultassetnamingstrategy">DefaultAssetNamingStrategy</DocsLink> which prefixes file names with
+An extension of the [DefaultAssetNamingStrategy](/reference/typescript-api/assets/default-asset-naming-strategy#defaultassetnamingstrategy) which prefixes file names with
 the type (`'source'` or `'preview'`) as well as a 2-character sub-directory based on
 the md5 hash of the original file name.
 
@@ -21,7 +21,7 @@ class HashedAssetNamingStrategy extends DefaultAssetNamingStrategy {
     generatePreviewFileName(ctx: RequestContext, originalFileName: string, conflictFileName?: string) => string;
 }
 ```
-* Extends: <DocsLink href="/reference/typescript-api/assets/default-asset-naming-strategy#defaultassetnamingstrategy">`DefaultAssetNamingStrategy`</DocsLink>
+* Extends: [`DefaultAssetNamingStrategy`](/reference/typescript-api/assets/default-asset-naming-strategy#defaultassetnamingstrategy)
 
 
 

docs/docs/reference/core-plugins/asset-server-plugin/image-transform-strategy.mdx

@@ -21,7 +21,7 @@ interface ImageTransformStrategy extends InjectableStrategy {
     ): Promise<ImageTransformParameters> | ImageTransformParameters;
 }
 ```
-* Extends: <DocsLink href="/reference/typescript-api/common/injectable-strategy#injectablestrategy">`InjectableStrategy`</DocsLink>
+* Extends: [`InjectableStrategy`](/reference/typescript-api/common/injectable-strategy#injectablestrategy)
 
 
 

docs/docs/reference/core-plugins/asset-server-plugin/index.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/asset-server-plugin/src/plugin.ts" sourceLine="176" packageName="@vendure/asset-server-plugin" />
 
 The `AssetServerPlugin` serves assets (images and other files) from the local file system, and can also be configured to use
-other storage strategies (e.g. <DocsLink href="/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy#s3assetstoragestrategy">S3AssetStorageStrategy</DocsLink>. It can also perform on-the-fly image transformations
+other storage strategies (e.g. [S3AssetStorageStrategy](/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy#s3assetstoragestrategy). It can also perform on-the-fly image transformations
 and caches the results for subsequent calls.
 
 ## Installation
@@ -127,11 +127,11 @@ a given configuration. Caching can be disabled per-request by setting the `?cach
 ### Limiting transformations
 
 By default, the AssetServerPlugin will allow any transformation to be performed on an image. However, it is possible to restrict the transformations
-which can be performed by using an <DocsLink href="/reference/core-plugins/asset-server-plugin/image-transform-strategy#imagetransformstrategy">ImageTransformStrategy</DocsLink>. This can be used to limit the transformations to a known set of presets, for example.
+which can be performed by using an [ImageTransformStrategy](/reference/core-plugins/asset-server-plugin/image-transform-strategy#imagetransformstrategy). This can be used to limit the transformations to a known set of presets, for example.
 
 This is advisable in order to prevent abuse of the image transformation feature, as it can be computationally expensive.
 
-Since v3.1.0 we ship with a <DocsLink href="/reference/core-plugins/asset-server-plugin/preset-only-strategy#presetonlystrategy">PresetOnlyStrategy</DocsLink> which allows only transformations using a known set of presets.
+Since v3.1.0 we ship with a [PresetOnlyStrategy](/reference/core-plugins/asset-server-plugin/preset-only-strategy#presetonlystrategy) which allows only transformations using a known set of presets.
 
 *Example*
 

docs/docs/reference/core-plugins/asset-server-plugin/local-asset-storage-strategy.mdx

@@ -18,7 +18,7 @@ class LocalAssetStorageStrategy implements AssetStorageStrategy {
     deleteFile(identifier: string) => Promise<void>;
 }
 ```
-* Implements: <DocsLink href="/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy">`AssetStorageStrategy`</DocsLink>
+* Implements: [`AssetStorageStrategy`](/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy)
 
 
 

docs/docs/reference/core-plugins/asset-server-plugin/preset-only-strategy.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/asset-server-plugin/src/config/preset-only-strategy.ts" sourceLine="85" packageName="@vendure/asset-server-plugin" since="3.1.0" />
 
-An <DocsLink href="/reference/core-plugins/asset-server-plugin/image-transform-strategy#imagetransformstrategy">ImageTransformStrategy</DocsLink> which only allows transformations to be made using
+An [ImageTransformStrategy](/reference/core-plugins/asset-server-plugin/image-transform-strategy#imagetransformstrategy) which only allows transformations to be made using
 presets which are defined in the available presets.
 
 With this strategy enabled, requests to the asset server must include a `preset` parameter (or use the default preset)
@@ -45,7 +45,7 @@ class PresetOnlyStrategy implements ImageTransformStrategy {
     }: GetImageTransformParametersArgs) => Promise<ImageTransformParameters> | ImageTransformParameters;
 }
 ```
-* Implements: <DocsLink href="/reference/core-plugins/asset-server-plugin/image-transform-strategy#imagetransformstrategy">`ImageTransformStrategy`</DocsLink>
+* Implements: [`ImageTransformStrategy`](/reference/core-plugins/asset-server-plugin/image-transform-strategy#imagetransformstrategy)
 
 
 
@@ -69,7 +69,7 @@ class PresetOnlyStrategy implements ImageTransformStrategy {
 </div>
 <GenerationInfo sourceFile="packages/asset-server-plugin/src/config/preset-only-strategy.ts" sourceLine="16" packageName="@vendure/asset-server-plugin" />
 
-Configuration options for the <DocsLink href="/reference/core-plugins/asset-server-plugin/preset-only-strategy#presetonlystrategy">PresetOnlyStrategy</DocsLink>.
+Configuration options for the [PresetOnlyStrategy](/reference/core-plugins/asset-server-plugin/preset-only-strategy#presetonlystrategy).
 
 ```ts title="Signature"
 interface PresetOnlyStrategyOptions {

docs/docs/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/asset-server-plugin/src/config/s3-asset-storage-strategy.ts" sourceLine="155" packageName="@vendure/asset-server-plugin" />
 
-An <DocsLink href="/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy">AssetStorageStrategy</DocsLink> which uses [Amazon S3](https://aws.amazon.com/s3/) object storage service.
+An [AssetStorageStrategy](/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy) which uses [Amazon S3](https://aws.amazon.com/s3/) object storage service.
 To us this strategy you must first have access to an AWS account.
 See their [getting started guide](https://aws.amazon.com/s3/getting-started/) for how to get set up.
 
@@ -14,11 +14,11 @@ Before using this strategy, make sure you have the `@aws-sdk/client-s3` and `@aw
 npm install @aws-sdk/client-s3 @aws-sdk/lib-storage
 ```
 
-**Note:** Rather than instantiating this manually, use the <DocsLink href="/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy#configures3assetstorage">configureS3AssetStorage</DocsLink> function.
+**Note:** Rather than instantiating this manually, use the [configureS3AssetStorage](/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy#configures3assetstorage) function.
 
 ## Use with S3-compatible services (MinIO)
 This strategy will also work with any S3-compatible object storage solutions, such as [MinIO](https://min.io/).
-See the <DocsLink href="/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy#configures3assetstorage">configureS3AssetStorage</DocsLink> for an example with MinIO.
+See the [configureS3AssetStorage](/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy#configures3assetstorage) for an example with MinIO.
 
 ```ts title="Signature"
 class S3AssetStorageStrategy implements AssetStorageStrategy {
@@ -33,7 +33,7 @@ class S3AssetStorageStrategy implements AssetStorageStrategy {
     fileExists(fileName: string) => ;
 }
 ```
-* Implements: <DocsLink href="/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy">`AssetStorageStrategy`</DocsLink>
+* Implements: [`AssetStorageStrategy`](/reference/typescript-api/assets/asset-storage-strategy#assetstoragestrategy)
 
 
 
@@ -134,7 +134,7 @@ Using type `any` in order to avoid the need to include `aws-sdk` dependency in g
 </div>
 <GenerationInfo sourceFile="packages/asset-server-plugin/src/config/s3-asset-storage-strategy.ts" sourceLine="119" packageName="@vendure/asset-server-plugin" />
 
-Returns a configured instance of the <DocsLink href="/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy#s3assetstoragestrategy">S3AssetStorageStrategy</DocsLink> which can then be passed to the <DocsLink href="/reference/core-plugins/asset-server-plugin/asset-server-options#assetserveroptions">AssetServerOptions</DocsLink>`storageStrategyFactory` property.
+Returns a configured instance of the [S3AssetStorageStrategy](/reference/core-plugins/asset-server-plugin/s3asset-storage-strategy#s3assetstoragestrategy) which can then be passed to the [AssetServerOptions](/reference/core-plugins/asset-server-plugin/asset-server-options#assetserveroptions)`storageStrategyFactory` property.
 
 Before using this strategy, make sure you have the `@aws-sdk/client-s3` and `@aws-sdk/lib-storage` package installed:
 

docs/docs/reference/core-plugins/asset-server-plugin/sharp-asset-preview-strategy.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/asset-server-plugin/src/config/sharp-asset-preview-strategy.ts" sourceLine="95" packageName="@vendure/asset-server-plugin" />
 
-This <DocsLink href="/reference/typescript-api/assets/asset-preview-strategy#assetpreviewstrategy">AssetPreviewStrategy</DocsLink> uses the [Sharp library](https://sharp.pixelplumbing.com/) to generate
+This [AssetPreviewStrategy](/reference/typescript-api/assets/asset-preview-strategy#assetpreviewstrategy) uses the [Sharp library](https://sharp.pixelplumbing.com/) to generate
 preview images of uploaded binary files. For non-image binaries, a generic "file" icon with the mime type
 overlay will be generated.
 
@@ -30,7 +30,7 @@ class SharpAssetPreviewStrategy implements AssetPreviewStrategy {
     generatePreviewImage(ctx: RequestContext, mimeType: string, data: Buffer) => Promise<Buffer>;
 }
 ```
-* Implements: <DocsLink href="/reference/typescript-api/assets/asset-preview-strategy#assetpreviewstrategy">`AssetPreviewStrategy`</DocsLink>
+* Implements: [`AssetPreviewStrategy`](/reference/typescript-api/assets/asset-preview-strategy#assetpreviewstrategy)
 
 
 
@@ -51,7 +51,7 @@ class SharpAssetPreviewStrategy implements AssetPreviewStrategy {
 </div>
 <GenerationInfo sourceFile="packages/asset-server-plugin/src/config/sharp-asset-preview-strategy.ts" sourceLine="17" packageName="@vendure/asset-server-plugin" />
 
-This <DocsLink href="/reference/typescript-api/assets/asset-preview-strategy#assetpreviewstrategy">AssetPreviewStrategy</DocsLink> uses the [Sharp library](https://sharp.pixelplumbing.com/) to generate
+This [AssetPreviewStrategy](/reference/typescript-api/assets/asset-preview-strategy#assetpreviewstrategy) uses the [Sharp library](https://sharp.pixelplumbing.com/) to generate
 preview images of uploaded binary files. For non-image binaries, a generic "file" icon with the mime type
 overlay will be generated.
 

docs/docs/reference/core-plugins/dashboard-plugin/dashboard-plugin-options.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/dashboard/plugin/dashboard.plugin.ts" sourceLine="29" packageName="@vendure/dashboard" />
 
-Configuration options for the <DocsLink href="/reference/core-plugins/dashboard-plugin/#dashboardplugin">DashboardPlugin</DocsLink>.
+Configuration options for the [DashboardPlugin](/reference/core-plugins/dashboard-plugin/#dashboardplugin).
 
 ```ts title="Signature"
 interface DashboardPluginOptions {

docs/docs/reference/core-plugins/elasticsearch-plugin/elasticsearch-options.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/elasticsearch-plugin/src/options.ts" sourceLine="30" packageName="@vendure/elasticsearch-plugin" />
 
-Configuration options for the <DocsLink href="/reference/core-plugins/elasticsearch-plugin/#elasticsearchplugin">ElasticsearchPlugin</DocsLink>.
+Configuration options for the [ElasticsearchPlugin](/reference/core-plugins/elasticsearch-plugin/#elasticsearchplugin).
 
 ```ts title="Signature"
 interface ElasticsearchOptions {

docs/docs/reference/core-plugins/elasticsearch-plugin/index.mdx

@@ -23,7 +23,7 @@ or
 
 Make sure to remove the `DefaultSearchPlugin` if it is still in the VendureConfig plugins array.
 
-Then add the `ElasticsearchPlugin`, calling the `.init()` method with <DocsLink href="/reference/core-plugins/elasticsearch-plugin/elasticsearch-options#elasticsearchoptions">ElasticsearchOptions</DocsLink>:
+Then add the `ElasticsearchPlugin`, calling the `.init()` method with [ElasticsearchOptions](/reference/core-plugins/elasticsearch-plugin/elasticsearch-options#elasticsearchoptions):
 
 *Example*
 

docs/docs/reference/core-plugins/email-plugin/email-event-handler-with-async-data.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/email-plugin/src/handler/event-handler.ts" sourceLine="506" packageName="@vendure/email-plugin" />
 
-Identical to the <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink> but with a `data` property added to the `event` based on the result
+Identical to the [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler) but with a `data` property added to the `event` based on the result
 of the `.loadData()` function.
 
 ```ts title="Signature"
@@ -12,7 +12,7 @@ class EmailEventHandlerWithAsyncData<Data, T extends string = string, InputEvent
     constructor(_loadDataFn: LoadDataFn<InputEvent, Data>, listener: EmailEventListener<T>, event: Type<InputEvent>)
 }
 ```
-* Extends: <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">`EmailEventHandler`</DocsLink>`<T, Event>`
+* Extends: [`EmailEventHandler`](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler)`<T, Event>`
 
 
 

docs/docs/reference/core-plugins/email-plugin/email-event-handler.mdx

@@ -6,7 +6,7 @@ generated: true
 
 The EmailEventHandler defines how the EmailPlugin will respond to a given event.
 
-A handler is created by creating a new <DocsLink href="/reference/core-plugins/email-plugin/email-event-listener#emaileventlistener">EmailEventListener</DocsLink> and calling the `.on()` method
+A handler is created by creating a new [EmailEventListener](/reference/core-plugins/email-plugin/email-event-listener#emaileventlistener) and calling the `.on()` method
 to specify which event to respond to.
 
 *Example*
@@ -34,9 +34,9 @@ By default, the handler will respond to all events on all channels and use the s
 and body template.
 
 Since v2.0 the `.addTemplate()` method has been **deprecated**. To serve different templates — for example, based on the current
-`languageCode` — implement a custom <DocsLink href="/reference/core-plugins/email-plugin/template-loader#templateloader">TemplateLoader</DocsLink> and pass it to `EmailPlugin.init({ templateLoader: new MyTemplateLoader() })`.
+`languageCode` — implement a custom [TemplateLoader](/reference/core-plugins/email-plugin/template-loader#templateloader) and pass it to `EmailPlugin.init({ templateLoader: new MyTemplateLoader() })`.
 
-The language is typically determined by the `languageCode` property of the event's `ctx` (<DocsLink href="/reference/typescript-api/request/request-context#requestcontext">RequestContext</DocsLink>) object, so the
+The language is typically determined by the `languageCode` property of the event's `ctx` ([RequestContext](/reference/typescript-api/request/request-context#requestcontext)) object, so the
 `loadTemplate()` method can use that to locate the correct template file.
 
 *Example*
@@ -65,7 +65,7 @@ EmailPlugin.init({
 ## Defining a custom handler
 
 Let's say you have a plugin which defines a new event type, `QuoteRequestedEvent`. In your plugin you have defined a mutation
-which is executed when the customer requests a quote in your storefront, and in your resolver, you use the <DocsLink href="/reference/typescript-api/events/event-bus#eventbus">EventBus</DocsLink> to publish a
+which is executed when the customer requests a quote in your storefront, and in your resolver, you use the [EventBus](/reference/typescript-api/events/event-bus#eventbus) to publish a
 new `QuoteRequestedEvent`.
 
 You now want to email the customer with their quote. Here are the steps you would take to set this up:
@@ -197,17 +197,17 @@ setTemplateVars() method.
 
 <MemberInfo kind="method" type={`(optionalAddressFieldsFn: <a href='/reference/core-plugins/email-plugin/email-plugin-types#setoptionaladdressfieldsfn'>SetOptionalAddressFieldsFn</a><Event>) => `}  since="1.1.0"  />
 
-A function which allows <DocsLink href="/reference/core-plugins/email-plugin/email-plugin-types#optionaladdressfields">OptionalAddressFields</DocsLink> to be specified such as "cc" and "bcc".
+A function which allows [OptionalAddressFields](/reference/core-plugins/email-plugin/email-plugin-types#optionaladdressfields) to be specified such as "cc" and "bcc".
 ### setMetadata
 
 <MemberInfo kind="method" type={`(optionalSetMetadataFn: <a href='/reference/core-plugins/email-plugin/email-plugin-types#setmetadatafn'>SetMetadataFn</a><Event>) => `}  since="3.1.0"  />
 
-A function which allows <DocsLink href="/reference/core-plugins/email-plugin/email-plugin-types#emailmetadata">EmailMetadata</DocsLink> to be specified for the email. This can be used
+A function which allows [EmailMetadata](/reference/core-plugins/email-plugin/email-plugin-types#emailmetadata) to be specified for the email. This can be used
 to store arbitrary data about the email which can be used for tracking or other purposes.
 
-It will be exposed in the <DocsLink href="/reference/core-plugins/email-plugin/email-send-event#emailsendevent">EmailSendEvent</DocsLink> as `event.metadata`. Here's an example of usage:
+It will be exposed in the [EmailSendEvent](/reference/core-plugins/email-plugin/email-send-event#emailsendevent) as `event.metadata`. Here's an example of usage:
 
-- An <DocsLink href="/reference/typescript-api/events/event-types#orderstatetransitionevent">OrderStateTransitionEvent</DocsLink> occurs, and the EmailEventListener starts processing it.
+- An [OrderStateTransitionEvent](/reference/typescript-api/events/event-types#orderstatetransitionevent) occurs, and the EmailEventListener starts processing it.
 - The EmailEventHandler attaches metadata to the email:
    ```ts
    new EmailEventListener(EventType.ORDER_CONFIRMATION)
@@ -217,7 +217,7 @@ It will be exposed in the <DocsLink href="/reference/core-plugins/email-plugin/e
        orderId: event.order.id,
      }));
   ```
-- Then, the EmailPlugin tries to send the email and publishes <DocsLink href="/reference/core-plugins/email-plugin/email-send-event#emailsendevent">EmailSendEvent</DocsLink>,
+- Then, the EmailPlugin tries to send the email and publishes [EmailSendEvent](/reference/core-plugins/email-plugin/email-send-event#emailsendevent),
   passing ctx, emailDetails, error or success, and this metadata.
 - In another part of the server, we have an eventBus that subscribes to EmailSendEvent. We can use
   `metadata.type` and `metadata.orderId` to identify the related order. For example, we can indicate on the
@@ -264,7 +264,7 @@ templates for channels or languageCodes other than the default.
 Allows data to be loaded asynchronously which can then be used as template variables.
 The `loadDataFn` has access to the event, the TypeORM `Connection` object, and an
 `inject()` function which can be used to inject any of the providers exported
-by the <DocsLink href="/reference/typescript-api/plugin/plugin-common-module#plugincommonmodule">PluginCommonModule</DocsLink>. The return value of the `loadDataFn` will be
+by the [PluginCommonModule](/reference/typescript-api/plugin/plugin-common-module#plugincommonmodule). The return value of the `loadDataFn` will be
 added to the `event` as the `data` property.
 
 *Example*

docs/docs/reference/core-plugins/email-plugin/email-event-listener.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/email-plugin/src/event-listener.ts" sourceLine="13" packageName="@vendure/email-plugin" />
 
-An EmailEventListener is used to listen for events and set up a <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink> which
+An EmailEventListener is used to listen for events and set up a [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler) which
 defines how an email will be generated from this event.
 
 ```ts title="Signature"

docs/docs/reference/core-plugins/email-plugin/email-generator.mdx

@@ -17,7 +17,7 @@ interface EmailGenerator<T extends string = any, E extends VendureEvent = any> e
     ): Pick<EmailDetails, 'from' | 'subject' | 'body'>;
 }
 ```
-* Extends: <DocsLink href="/reference/typescript-api/common/injectable-strategy#injectablestrategy">`InjectableStrategy`</DocsLink>
+* Extends: [`InjectableStrategy`](/reference/typescript-api/common/injectable-strategy#injectablestrategy)
 
 
 
@@ -48,7 +48,7 @@ class HandlebarsMjmlGenerator implements EmailGenerator {
     generate(from: string, subject: string, template: string, templateVars: any) => ;
 }
 ```
-* Implements: <DocsLink href="/reference/core-plugins/email-plugin/email-generator#emailgenerator">`EmailGenerator`</DocsLink>
+* Implements: [`EmailGenerator`](/reference/core-plugins/email-plugin/email-generator#emailgenerator)
 
 
 

docs/docs/reference/core-plugins/email-plugin/email-plugin-options.mdx

@@ -46,7 +46,7 @@ Configures how the emails are sent.
 
 <MemberInfo kind="property" type={`Array<<a href='/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler'>EmailEventHandler</a><string, any>>`}   />
 
-An array of <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink>s which define which Vendure events will trigger
+An array of [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler)s which define which Vendure events will trigger
 emails, and how those emails are generated.
 ### globalTemplateVars
 
@@ -115,7 +115,7 @@ interface EmailPluginDevModeOptions extends Omit<EmailPluginOptions, 'transport'
     route: string;
 }
 ```
-* Extends: `Omit<`<DocsLink href="/reference/core-plugins/email-plugin/email-plugin-options#emailpluginoptions">`EmailPluginOptions`</DocsLink>`, 'transport'>`
+* Extends: `Omit<`[`EmailPluginOptions`](/reference/core-plugins/email-plugin/email-plugin-options#emailpluginoptions)`, 'transport'>`
 
 
 

docs/docs/reference/core-plugins/email-plugin/email-plugin-types.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="22" packageName="@vendure/email-plugin" />
 
 A VendureEvent which also includes a `ctx` property containing the current
-<DocsLink href="/reference/typescript-api/request/request-context#requestcontext">RequestContext</DocsLink>, which is used to determine the channel and language
+[RequestContext](/reference/typescript-api/request/request-context#requestcontext), which is used to determine the channel and language
 to use when generating the email.
 
 ```ts title="Signature"
@@ -13,8 +13,8 @@ type EventWithContext = VendureEvent & { ctx: RequestContext }
 ```
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="32" packageName="@vendure/email-plugin" />
 
-A VendureEvent with a <DocsLink href="/reference/typescript-api/request/request-context#requestcontext">RequestContext</DocsLink> and a `data` property which contains the
-value resolved from the <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink>`.loadData()` callback.
+A VendureEvent with a [RequestContext](/reference/typescript-api/request/request-context#requestcontext) and a `data` property which contains the
+value resolved from the [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler)`.loadData()` callback.
 
 ```ts title="Signature"
 type EventWithAsyncData<Event extends EventWithContext, R> = Event & { data: R }
@@ -83,7 +83,7 @@ interface EmailDetails<Type extends 'serialized' | 'unserialized' = 'unserialize
 </div>
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="322" packageName="@vendure/email-plugin" />
 
-A function used to load async data for use by an <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink>.
+A function used to load async data for use by an [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler).
 
 ```ts title="Signature"
 type LoadDataFn<Event extends EventWithContext, R> = (context: {
@@ -103,7 +103,7 @@ type EmailAttachment = Omit<Attachment, 'raw'> & { path?: string }
 ```
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="402" packageName="@vendure/email-plugin" />
 
-The object passed to the <DocsLink href="/reference/core-plugins/email-plugin/template-loader#templateloader">TemplateLoader</DocsLink> `loadTemplate()` method.
+The object passed to the [TemplateLoader](/reference/core-plugins/email-plugin/template-loader#templateloader) `loadTemplate()` method.
 
 ```ts title="Signature"
 interface LoadTemplateInput {
@@ -138,7 +138,7 @@ EmailEventHandler's `setTemplateVars()` method.
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="435" packageName="@vendure/email-plugin" />
 
 A function used to define template variables available to email templates.
-See <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink>.setTemplateVars().
+See [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler).setTemplateVars().
 
 ```ts title="Signature"
 type SetTemplateVarsFn<Event> = (
@@ -200,7 +200,7 @@ An email address that will appear on the _Reply-To:_ field
 </div>
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="497" packageName="@vendure/email-plugin" since="1.1.0" />
 
-A function used to set the <DocsLink href="/reference/core-plugins/email-plugin/email-plugin-types#optionaladdressfields">OptionalAddressFields</DocsLink>.
+A function used to set the [OptionalAddressFields](/reference/core-plugins/email-plugin/email-plugin-types#optionaladdressfields).
 
 ```ts title="Signature"
 type SetOptionalAddressFieldsFn<Event> = (
@@ -209,14 +209,14 @@ type SetOptionalAddressFieldsFn<Event> = (
 ```
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="509" packageName="@vendure/email-plugin" since="3.1.0" />
 
-A function used to set the <DocsLink href="/reference/core-plugins/email-plugin/email-plugin-types#emailmetadata">EmailMetadata</DocsLink>.
+A function used to set the [EmailMetadata](/reference/core-plugins/email-plugin/email-plugin-types#emailmetadata).
 
 ```ts title="Signature"
 type SetMetadataFn<Event> = (event: Event) => EmailMetadata | Promise<EmailMetadata>
 ```
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="519" packageName="@vendure/email-plugin" since="3.1.0" />
 
-Metadata that can be attached to an email via the <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink>`.setMetadata()` method.
+Metadata that can be attached to an email via the [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler)`.setMetadata()` method.
 
 ```ts title="Signature"
 type EmailMetadata = Record<string, any>

docs/docs/reference/core-plugins/email-plugin/email-send-event.mdx

@@ -13,7 +13,7 @@ class EmailSendEvent extends VendureEvent {
     constructor(ctx: RequestContext, details: EmailDetails, success: boolean, error?: Error, metadata?: EmailMetadata)
 }
 ```
-* Extends: <DocsLink href="/reference/typescript-api/events/vendure-event#vendureevent">`VendureEvent`</DocsLink>
+* Extends: [`VendureEvent`](/reference/typescript-api/events/vendure-event#vendureevent)
 
 
 

docs/docs/reference/core-plugins/email-plugin/email-sender.mdx

@@ -6,7 +6,7 @@ generated: true
 
 An EmailSender is responsible for sending the email, e.g. via an SMTP connection
 or using some other mail-sending API. By default, the EmailPlugin uses the
-<DocsLink href="/reference/core-plugins/email-plugin/email-sender#nodemaileremailsender">NodemailerEmailSender</DocsLink>, but it is also possible to supply a custom implementation:
+[NodemailerEmailSender](/reference/core-plugins/email-plugin/email-sender#nodemaileremailsender), but it is also possible to supply a custom implementation:
 
 *Example*
 
@@ -44,7 +44,7 @@ interface EmailSender extends InjectableStrategy {
     send: (email: EmailDetails, options: EmailTransportOptions) => void | Promise<void>;
 }
 ```
-* Extends: <DocsLink href="/reference/typescript-api/common/injectable-strategy#injectablestrategy">`InjectableStrategy`</DocsLink>
+* Extends: [`InjectableStrategy`](/reference/typescript-api/common/injectable-strategy#injectablestrategy)
 
 
 
@@ -67,7 +67,7 @@ class NodemailerEmailSender implements EmailSender {
     send(email: EmailDetails, options: EmailTransportOptions) => ;
 }
 ```
-* Implements: <DocsLink href="/reference/core-plugins/email-plugin/email-sender#emailsender">`EmailSender`</DocsLink>
+* Implements: [`EmailSender`](/reference/core-plugins/email-plugin/email-sender#emailsender)
 
 
 

docs/docs/reference/core-plugins/email-plugin/index.mdx

@@ -8,7 +8,7 @@ The EmailPlugin creates and sends transactional emails based on Vendure events.
 email generator to generate the email body and [Nodemailer](https://nodemailer.com/about/) to send the emails.
 
 ## High-level description
-Vendure has an internal events system (see <DocsLink href="/reference/typescript-api/events/event-bus#eventbus">EventBus</DocsLink>) that allows plugins to subscribe to events. The EmailPlugin is configured with <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink>s
+Vendure has an internal events system (see [EventBus](/reference/typescript-api/events/event-bus#eventbus)) that allows plugins to subscribe to events. The EmailPlugin is configured with [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler)s
 that listen for a specific event and when it is published, the handler defines which template to use to generate the resulting email.
 
 The plugin comes with a set of default handler for the following events:
@@ -17,7 +17,7 @@ The plugin comes with a set of default handler for the following events:
 - Password reset request
 - Email address change request
 
-You can also create your own handler and register them with the plugin - see the <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink> docs for more details.
+You can also create your own handler and register them with the plugin - see the [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler) docs for more details.
 
 ## Installation
 
@@ -188,7 +188,7 @@ EmailPlugin.init({
 }),
 ```
 
-For all available methods of extending a handler, see the <DocsLink href="/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler">EmailEventHandler</DocsLink> documentation.
+For all available methods of extending a handler, see the [EmailEventHandler](/reference/core-plugins/email-plugin/email-event-handler#emaileventhandler) documentation.
 
 ## Dynamic SMTP settings
 
@@ -224,7 +224,7 @@ const config: VendureConfig = {
 ## Dev mode
 
 For development, the `transport` option can be replaced by `devMode: true`. Doing so configures Vendure to use the
-file transport (See <DocsLink href="/reference/core-plugins/email-plugin/transport-options#filetransportoptions">FileTransportOptions</DocsLink>) and outputs emails as rendered HTML files in the directory specified by the
+file transport (See [FileTransportOptions](/reference/core-plugins/email-plugin/transport-options#filetransportoptions)) and outputs emails as rendered HTML files in the directory specified by the
 `outputPath` property.
 
 ```ts

docs/docs/reference/core-plugins/email-plugin/template-loader.mdx

@@ -61,7 +61,7 @@ class FileBasedTemplateLoader implements TemplateLoader {
     loadPartials() => Promise<Partial[]>;
 }
 ```
-* Implements: <DocsLink href="/reference/core-plugins/email-plugin/template-loader#templateloader">`TemplateLoader`</DocsLink>
+* Implements: [`TemplateLoader`](/reference/core-plugins/email-plugin/template-loader#templateloader)
 
 
 

docs/docs/reference/core-plugins/email-plugin/transport-options.mdx

@@ -39,7 +39,7 @@ interface SMTPTransportOptions extends SMTPTransport.Options {
 
 <MemberInfo kind="property" type={`boolean`} default={`false`}   />
 
-If true, uses the configured <DocsLink href="/reference/typescript-api/logger/vendure-logger#vendurelogger">VendureLogger</DocsLink> to log messages from Nodemailer as it interacts with
+If true, uses the configured [VendureLogger](/reference/typescript-api/logger/vendure-logger#vendurelogger) to log messages from Nodemailer as it interacts with
 the SMTP server.
 
 
@@ -166,7 +166,7 @@ interface FileTransportOptions {
 <GenerationInfo sourceFile="packages/email-plugin/src/types.ts" sourceLine="277" packageName="@vendure/email-plugin" />
 
 Does nothing with the generated email. Intended for use in testing where we don't care about the email transport,
-or when using a custom <DocsLink href="/reference/core-plugins/email-plugin/email-sender#emailsender">EmailSender</DocsLink> which does not require transport options.
+or when using a custom [EmailSender](/reference/core-plugins/email-plugin/email-sender#emailsender) which does not require transport options.
 
 ```ts title="Signature"
 interface NoopTransportOptions {

docs/docs/reference/core-plugins/harden-plugin/harden-plugin-options.mdx

@@ -36,7 +36,7 @@ A query which exceeds the maximum score will result in an error.
 <MemberInfo kind="property" type={`ComplexityEstimator[]`}   />
 
 An array of custom estimator functions for calculating the complexity of a query. By default,
-the plugin will use the <DocsLink href="/reference/core-plugins/harden-plugin/default-vendure-complexity-estimator#defaultvendurecomplexityestimator">defaultVendureComplexityEstimator</DocsLink> which is specifically
+the plugin will use the [defaultVendureComplexityEstimator](/reference/core-plugins/harden-plugin/default-vendure-complexity-estimator#defaultvendurecomplexityestimator) which is specifically
 tuned to accurately estimate Vendure queries.
 ### logComplexityScore
 

docs/docs/reference/core-plugins/harden-plugin/index.mdx

@@ -21,7 +21,7 @@ or
 
 `npm install @vendure/harden-plugin`
 
-Then add the `HardenPlugin`, calling the `.init()` method with <DocsLink href="/reference/core-plugins/harden-plugin/harden-plugin-options#hardenpluginoptions">HardenPluginOptions</DocsLink>:
+Then add the `HardenPlugin`, calling the `.init()` method with [HardenPluginOptions](/reference/core-plugins/harden-plugin/harden-plugin-options#hardenpluginoptions):
 
 *Example*
 
@@ -79,7 +79,7 @@ query EvilQuery {
 This evil query has a complexity score of 2,443,203 - much greater than the default of 1,000!
 
 The complexity score is calculated by the [graphql-query-complexity library](https://www.npmjs.com/package/graphql-query-complexity),
-and by default uses the <DocsLink href="/reference/core-plugins/harden-plugin/default-vendure-complexity-estimator#defaultvendurecomplexityestimator">defaultVendureComplexityEstimator</DocsLink>, which is tuned specifically to the Vendure Shop API.
+and by default uses the [defaultVendureComplexityEstimator](/reference/core-plugins/harden-plugin/default-vendure-complexity-estimator#defaultvendurecomplexityestimator), which is tuned specifically to the Vendure Shop API.
 
 :::caution
 Note: By default, if the "take" argument is omitted from a list query (e.g. the `products` or `collections` query), a default factor of 1000 is applied.

docs/docs/reference/core-plugins/job-queue-plugin/bull-mqjob-queue-strategy.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/job-queue-plugin/src/bullmq/bullmq-job-queue-strategy.ts" sourceLine="53" packageName="@vendure/job-queue-plugin" />
 
 This JobQueueStrategy uses [BullMQ](https://docs.bullmq.io/) to implement a push-based job queue
-on top of Redis. It should not be used alone, but as part of the <DocsLink href="/reference/core-plugins/job-queue-plugin/bull-mqjob-queue-plugin#bullmqjobqueueplugin">BullMQJobQueuePlugin</DocsLink>.
+on top of Redis. It should not be used alone, but as part of the [BullMQJobQueuePlugin](/reference/core-plugins/job-queue-plugin/bull-mqjob-queue-plugin#bullmqjobqueueplugin).
 
 Note: To use this strategy, you need to manually install the `bullmq` package:
 

docs/docs/reference/core-plugins/job-queue-plugin/bull-mqplugin-options.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/job-queue-plugin/src/bullmq/types.ts" sourceLine="21" packageName="@vendure/job-queue-plugin" since="1.2.0" />
 
-Configuration options for the <DocsLink href="/reference/core-plugins/job-queue-plugin/bull-mqjob-queue-plugin#bullmqjobqueueplugin">BullMQJobQueuePlugin</DocsLink>.
+Configuration options for the [BullMQJobQueuePlugin](/reference/core-plugins/job-queue-plugin/bull-mqjob-queue-plugin#bullmqjobqueueplugin).
 
 ```ts title="Signature"
 interface BullMQPluginOptions {

docs/docs/reference/core-plugins/job-queue-plugin/pub-sub-job-queue-strategy.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/job-queue-plugin/src/pub-sub/pub-sub-job-queue-strategy.ts" sourceLine="29" packageName="@vendure/job-queue-plugin" />
 
 This JobQueueStrategy uses Google Cloud Pub/Sub to implement a job queue for Vendure.
-It should not be used alone, but as part of the <DocsLink href="/reference/core-plugins/job-queue-plugin/pub-sub-plugin#pubsubplugin">PubSubPlugin</DocsLink>.
+It should not be used alone, but as part of the [PubSubPlugin](/reference/core-plugins/job-queue-plugin/pub-sub-plugin#pubsubplugin).
 
 Note: To use this strategy, you need to manually install the `@google-cloud/pubsub` package:
 

docs/docs/reference/core-plugins/payments-plugin/stripe-plugin.mdx

@@ -37,7 +37,7 @@ the Stripe CLI to test your webhook locally. See the _local development_ section
       }),
     ]
     ````
-    For all the plugin options, see the <DocsLink href="/reference/core-plugins/payments-plugin/stripe-plugin#stripepluginoptions">StripePluginOptions</DocsLink> type.
+    For all the plugin options, see the [StripePluginOptions](/reference/core-plugins/payments-plugin/stripe-plugin#stripepluginoptions) type.
 2. Create a new PaymentMethod in the Admin UI, and select "Stripe payments" as the handler.
 3. Set the webhook secret and API key in the PaymentMethod form.
 

docs/docs/reference/core-plugins/sentry-plugin/sentry-plugin-options.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/sentry-plugin/src/types.ts" sourceLine="7" packageName="@vendure/sentry-plugin" />
 
-Configuration options for the <DocsLink href="/reference/core-plugins/sentry-plugin/#sentryplugin">SentryPlugin</DocsLink>.
+Configuration options for the [SentryPlugin](/reference/core-plugins/sentry-plugin/#sentryplugin).
 
 ```ts title="Signature"
 interface SentryPluginOptions {

docs/docs/reference/core-plugins/stellate-plugin/index.mdx

@@ -25,7 +25,7 @@ npm install @vendure/stellate-plugin
 ## Configuration
 
 The plugin is configured via the `StellatePlugin.init()` method. This method accepts an options object
-which defines the Stellate service name and API token, as well as an array of <DocsLink href="/reference/core-plugins/stellate-plugin/purge-rule#purgerule">PurgeRule</DocsLink>s which
+which defines the Stellate service name and API token, as well as an array of [PurgeRule](/reference/core-plugins/stellate-plugin/purge-rule#purgerule)s which
 define how the plugin will respond to Vendure events in order to trigger calls to the
 Stellate [Purging API](https://stellate.co/docs/graphql-edge-cache/purging-api).
 
@@ -148,7 +148,7 @@ export const searchProductsDocument = graphql(`
 
 The configuration above only accounts for caching of some of the built-in Vendure entity types. If you have
 custom entity types, you may well want to add them to the Stellate cache. In this case, you'll also need a way to
-purge those entities from the cache when they are updated. This is where the <DocsLink href="/reference/core-plugins/stellate-plugin/purge-rule#purgerule">PurgeRule</DocsLink> comes in.
+purge those entities from the cache when they are updated. This is where the [PurgeRule](/reference/core-plugins/stellate-plugin/purge-rule#purgerule) comes in.
 
 Let's imagine that you have built a simple CMS plugin for Vendure which exposes an `Article` entity in your Shop API, and
 you have added this to your Stellate configuration:
@@ -176,7 +176,7 @@ const config: Config = {
 export default config;
 ```
 
-You can then add a custom <DocsLink href="/reference/core-plugins/stellate-plugin/purge-rule#purgerule">PurgeRule</DocsLink> to the StellatePlugin configuration:
+You can then add a custom [PurgeRule](/reference/core-plugins/stellate-plugin/purge-rule#purgerule) to the StellatePlugin configuration:
 
 *Example*
 

docs/docs/reference/core-plugins/stellate-plugin/purge-rule.mdx

@@ -6,7 +6,7 @@ generated: true
 
 Defines a rule that listens for a particular VendureEvent and uses that to
 make calls to the [Stellate Purging API](https://docs.stellate.co/docs/purging-api) via
-the provided <DocsLink href="/reference/core-plugins/stellate-plugin/stellate-service#stellateservice">StellateService</DocsLink> instance.
+the provided [StellateService](/reference/core-plugins/stellate-plugin/stellate-service#stellateservice) instance.
 
 ```ts title="Signature"
 class PurgeRule<Event extends VendureEvent = VendureEvent> {
@@ -44,7 +44,7 @@ class PurgeRule<Event extends VendureEvent = VendureEvent> {
 </div>
 <GenerationInfo sourceFile="packages/stellate-plugin/src/purge-rule.ts" sourceLine="13" packageName="@vendure/stellate-plugin" />
 
-Configures a <DocsLink href="/reference/core-plugins/stellate-plugin/purge-rule#purgerule">PurgeRule</DocsLink>.
+Configures a [PurgeRule](/reference/core-plugins/stellate-plugin/purge-rule#purgerule).
 
 ```ts title="Signature"
 interface PurgeRuleConfig<Event extends VendureEvent> {
@@ -76,7 +76,7 @@ us to efficiently batch calls to the Stellate Purge API.
 <MemberInfo kind="property" type={`(handlerArgs: {         events: Event[];         stellateService: <a href='/reference/core-plugins/stellate-plugin/stellate-service#stellateservice'>StellateService</a>;         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>;     }) => void | Promise<void>`}   />
 
 The function to invoke when the specified event is published. This function should use the
-<DocsLink href="/reference/core-plugins/stellate-plugin/stellate-service#stellateservice">StellateService</DocsLink> instance to call the Stellate Purge API.
+[StellateService](/reference/core-plugins/stellate-plugin/stellate-service#stellateservice) instance to call the Stellate Purge API.
 
 
 </div>

docs/docs/reference/core-plugins/stellate-plugin/stellate-plugin-options.mdx

@@ -34,7 +34,7 @@ see the [Stellate docs](https://docs.stellate.co/docs/purging-api#authentication
 
 <MemberInfo kind="property" type={`<a href='/reference/core-plugins/stellate-plugin/purge-rule#purgerule'>PurgeRule</a>[]`}   />
 
-An array of <DocsLink href="/reference/core-plugins/stellate-plugin/purge-rule#purgerule">PurgeRule</DocsLink> instances which are used to define how the plugin will
+An array of [PurgeRule](/reference/core-plugins/stellate-plugin/purge-rule#purgerule) instances which are used to define how the plugin will
 respond to Vendure events in order to trigger calls to the Stellate Purging API.
 ### defaultBufferTimeMs
 

docs/docs/reference/core-plugins/telemetry-plugin/otel-logger.mdx

@@ -16,7 +16,7 @@ class OtelLogger implements VendureLogger {
     verbose(message: string, context?: string) => void;
 }
 ```
-* Implements: <DocsLink href="/reference/typescript-api/logger/vendure-logger#vendurelogger">`VendureLogger`</DocsLink>
+* Implements: [`VendureLogger`](/reference/typescript-api/logger/vendure-logger#vendurelogger)
 
 
 

docs/docs/reference/core-plugins/telemetry-plugin/register-method-hooks.mdx

@@ -7,7 +7,7 @@ generated: true
 Allows you to register hooks for a specific method of an instrumented class.
 These hooks allow extra telemetry actions to be performed on the method.
 
-They can then be passed to the <DocsLink href="/reference/core-plugins/telemetry-plugin/#telemetryplugin">TelemetryPlugin</DocsLink> via the <DocsLink href="/reference/core-plugins/telemetry-plugin/telemetry-plugin-options#telemetrypluginoptions">TelemetryPluginOptions</DocsLink>.
+They can then be passed to the [TelemetryPlugin](/reference/core-plugins/telemetry-plugin/#telemetryplugin) via the [TelemetryPluginOptions](/reference/core-plugins/telemetry-plugin/telemetry-plugin-options#telemetrypluginoptions).
 
 *Example*
 

docs/docs/reference/core-plugins/telemetry-plugin/telemetry-plugin-options.mdx

@@ -41,7 +41,7 @@ TelemetryPlugin.init({
 This API may change in a future release.
 
 Method hooks allow you to add extra telemetry actions to specific methods.
-To define hooks on a method, use the <DocsLink href="/reference/core-plugins/telemetry-plugin/register-method-hooks#registermethodhooks">registerMethodHooks</DocsLink> function.
+To define hooks on a method, use the [registerMethodHooks](/reference/core-plugins/telemetry-plugin/register-method-hooks#registermethodhooks) function.
 
 *Example*
 

docs/docs/reference/dashboard/components/asset-gallery.mdx

@@ -29,7 +29,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/asset/asset-gallery.tsx" sourceLine="83" packageName="@vendure/dashboard" />
 
-Props for the <DocsLink href="/reference/dashboard/components/asset-gallery#assetgallery">AssetGallery</DocsLink> component.
+Props for the [AssetGallery](/reference/dashboard/components/asset-gallery#assetgallery) component.
 
 ```ts title="Signature"
 interface AssetGalleryProps {

docs/docs/reference/dashboard/components/asset-picker-dialog.mdx

@@ -17,7 +17,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/asset/asset-picker-dialog.tsx" sourceLine="19" packageName="@vendure/dashboard" />
 
-Props for the <DocsLink href="/reference/dashboard/components/asset-picker-dialog#assetpickerdialog">AssetPickerDialog</DocsLink> component.
+Props for the [AssetPickerDialog](/reference/dashboard/components/asset-picker-dialog#assetpickerdialog) component.
 
 ```ts title="Signature"
 interface AssetPickerDialogProps {

docs/docs/reference/dashboard/components/vendure-image.mdx

@@ -37,7 +37,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/vendure-image.tsx" sourceLine="59" packageName="@vendure/dashboard" since="3.4.0" />
 
-The props for the <DocsLink href="/reference/dashboard/components/vendure-image#vendureimage">VendureImage</DocsLink> component.
+The props for the [VendureImage](/reference/dashboard/components/vendure-image#vendureimage) component.
 
 ```ts title="Signature"
 interface VendureImageProps extends React.ImgHTMLAttributes<HTMLImageElement> {
@@ -115,7 +115,7 @@ The ref to the image element.
 </div>
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/vendure-image.tsx" sourceLine="13" packageName="@vendure/dashboard" since="3.4.0" />
 
-The type of object that can be used as an asset in the <DocsLink href="/reference/dashboard/components/vendure-image#vendureimage">VendureImage</DocsLink> component.
+The type of object that can be used as an asset in the [VendureImage](/reference/dashboard/components/vendure-image#vendureimage) component.
 
 ```ts title="Signature"
 interface AssetLike {
@@ -153,21 +153,21 @@ interface AssetLike {
 </div>
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/vendure-image.tsx" sourceLine="28" packageName="@vendure/dashboard" since="3.4.0" />
 
-The presets that can be used for the <DocsLink href="/reference/dashboard/components/vendure-image#vendureimage">VendureImage</DocsLink> component.
+The presets that can be used for the [VendureImage](/reference/dashboard/components/vendure-image#vendureimage) component.
 
 ```ts title="Signature"
 type ImagePreset = 'tiny' | 'thumb' | 'small' | 'medium' | 'large' | 'full' | null
 ```
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/vendure-image.tsx" sourceLine="38" packageName="@vendure/dashboard" since="3.4.0" />
 
-The formats that can be used for the <DocsLink href="/reference/dashboard/components/vendure-image#vendureimage">VendureImage</DocsLink> component.
+The formats that can be used for the [VendureImage](/reference/dashboard/components/vendure-image#vendureimage) component.
 
 ```ts title="Signature"
 type ImageFormat = 'jpg' | 'jpeg' | 'png' | 'webp' | 'avif' | null
 ```
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/vendure-image.tsx" sourceLine="48" packageName="@vendure/dashboard" since="3.4.0" />
 
-The modes that can be used for the <DocsLink href="/reference/dashboard/components/vendure-image#vendureimage">VendureImage</DocsLink> component.
+The modes that can be used for the [VendureImage](/reference/dashboard/components/vendure-image#vendureimage) component.
 
 ```ts title="Signature"
 type ImageMode = 'crop' | 'resize' | null

docs/docs/reference/dashboard/detail-views/detail-page.mdx

@@ -6,7 +6,7 @@ generated: true
 
 Auto-generates a detail page with a form based on the provided query and mutation documents.
 
-For more control over the layout, you would use the more low-level <DocsLink href="/reference/dashboard/page-layout/page#page">Page</DocsLink> component.
+For more control over the layout, you would use the more low-level [Page](/reference/dashboard/page-layout/page#page) component.
 
 ```ts title="Signature"
 function DetailPage<T extends TypedDocumentNode<any, any>, C extends TypedDocumentNode<any, any>, U extends TypedDocumentNode<any, any>>(props: DetailPageProps<T, C, U>): void
@@ -19,7 +19,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/page/detail-page.tsx" sourceLine="43" packageName="@vendure/dashboard" since="3.3.0" />
 
-Props to configure the <DocsLink href="/reference/dashboard/detail-views/detail-page#detailpage">DetailPage</DocsLink> component.
+Props to configure the [DetailPage](/reference/dashboard/detail-views/detail-page#detailpage) component.
 
 ```ts title="Signature"
 interface DetailPageProps<T extends TypedDocumentNode<any, any>, C extends TypedDocumentNode<any, any>, U extends TypedDocumentNode<any, any>, EntityField extends keyof ResultOf<T> = DetailEntityPath<T>> {

docs/docs/reference/dashboard/detail-views/use-generated-form.mdx

@@ -8,7 +8,7 @@ This hook is used to create a form from a document and an entity.
 It will create a form with the fields defined in the document's input type.
 It will also create a submit handler that will submit the form to the server.
 
-This hook is mostly used internally by the higher-level <DocsLink href="/reference/dashboard/detail-views/use-detail-page#usedetailpage">useDetailPage</DocsLink> hook,
+This hook is mostly used internally by the higher-level [useDetailPage](/reference/dashboard/detail-views/use-detail-page#usedetailpage) hook,
 but can in some cases be useful to use directly.
 
 *Example*

docs/docs/reference/dashboard/extensions-api/form-components.mdx

@@ -92,7 +92,7 @@ type DashboardFormComponentProps<TFieldValues extends FieldValues = FieldValues,
 ```
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/form-engine/form-engine-types.ts" sourceLine="124" packageName="@vendure/dashboard" since="3.4.0" />
 
-Metadata which can be defined on a <DocsLink href="/reference/dashboard/extensions-api/form-components#dashboardformcomponent">DashboardFormComponent</DocsLink> which
+Metadata which can be defined on a [DashboardFormComponent](/reference/dashboard/extensions-api/form-components#dashboardformcomponent) which
 provides additional information about how the dashboard should render the
 component.
 

docs/docs/reference/dashboard/extensions-api/history-entries.mdx

@@ -54,14 +54,14 @@ The `type` should correspond to a valid `HistoryEntryType`, such as
 
 - `CUSTOMER_REGISTERED`
 - `ORDER_STATE_TRANSITION`
-- some custom type - see the <DocsLink href="/reference/typescript-api/services/history-service#historyservice">HistoryService</DocsLink> docs for a guide on
+- some custom type - see the [HistoryService](/reference/typescript-api/services/history-service#historyservice) docs for a guide on
   how to define custom history entry types.
 ### component
 
 <MemberInfo kind="property" type={`React.ComponentType<{         entry: <a href='/reference/dashboard/extensions-api/history-entries#historyentryitem'>HistoryEntryItem</a>;         entity: OrderHistoryOrderDetail | CustomerHistoryCustomerDetail;     }>`}   />
 
 The component which is used to render the timeline entry. It should use the
-<DocsLink href="/reference/dashboard/extensions-api/history-entries#historyentry">HistoryEntry</DocsLink> component and pass the appropriate props to configure
+[HistoryEntry](/reference/dashboard/extensions-api/history-entries#historyentry) component and pass the appropriate props to configure
 how it will be displayed.
 
 The `entity` prop will be a subset of the Order object for Order history entries,
@@ -142,7 +142,7 @@ and the `ORDER_STATE_TRANSITION` data looks like this:
 </div>
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/history-entry/history-entry.tsx" sourceLine="14" packageName="@vendure/dashboard" since="3.4.3" />
 
-The props for the <DocsLink href="/reference/dashboard/extensions-api/history-entries#historyentry">HistoryEntry</DocsLink> component.
+The props for the [HistoryEntry](/reference/dashboard/extensions-api/history-entries#historyentry) component.
 
 ```ts title="Signature"
 interface HistoryEntryProps {

docs/docs/reference/dashboard/form-components/form-field-wrapper.mdx

@@ -30,7 +30,7 @@ overridden form components.
 </PageBlock>
 ```
 
-If you are dealing with translatable fields, use the <DocsLink href="/reference/dashboard/form-components/translatable-form-field-wrapper#translatableformfieldwrapper">TranslatableFormFieldWrapper</DocsLink> component instead.
+If you are dealing with translatable fields, use the [TranslatableFormFieldWrapper](/reference/dashboard/form-components/translatable-form-field-wrapper#translatableformfieldwrapper) component instead.
 
 ```ts title="Signature"
 function FormFieldWrapper<TFieldValues extends FieldValues = FieldValues, TName extends FieldPath<TFieldValues> = FieldPath<TFieldValues>>(props: FormFieldWrapperProps<TFieldValues, TName>): void

docs/docs/reference/dashboard/form-components/translatable-form-field-wrapper.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/translatable-form-field.tsx" sourceLine="112" packageName="@vendure/dashboard" since="3.4.0" />
 
-This is the equivalent of the <DocsLink href="/reference/dashboard/form-components/form-field-wrapper#formfieldwrapper">FormFieldWrapper</DocsLink> component, but for translatable fields.
+This is the equivalent of the [FormFieldWrapper](/reference/dashboard/form-components/form-field-wrapper#formfieldwrapper) component, but for translatable fields.
 
 *Example*
 

docs/docs/reference/dashboard/hooks/use-auth.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/dashboard/src/lib/hooks/use-auth.tsx" sourceLine="15" packageName="@vendure/dashboard" since="3.3.0" />
 
-Provides access to the <DocsLink href="/reference/dashboard/hooks/use-auth#authcontext">AuthContext</DocsLink> which contains information
+Provides access to the [AuthContext](/reference/dashboard/hooks/use-auth#authcontext) which contains information
 about the active channel.
 
 ```ts title="Signature"

docs/docs/reference/dashboard/hooks/use-channel.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/dashboard/src/lib/hooks/use-channel.ts" sourceLine="21" packageName="@vendure/dashboard" since="3.3.0" />
 
-Provides access to the <DocsLink href="/reference/dashboard/hooks/use-channel#channelcontext">ChannelContext</DocsLink> which contains information
+Provides access to the [ChannelContext](/reference/dashboard/hooks/use-channel#channelcontext) which contains information
 about the active channel.
 
 *Example*

docs/docs/reference/dashboard/list-views/data-table.mdx

@@ -19,7 +19,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/data-table/data-table.tsx" sourceLine="113" packageName="@vendure/dashboard" since="3.4.0" />
 
-Props for configuring the <DocsLink href="/reference/dashboard/list-views/data-table#datatable">DataTable</DocsLink>.
+Props for configuring the [DataTable](/reference/dashboard/list-views/data-table#datatable).
 
 ```ts title="Signature"
 interface DataTableProps<TData> {

docs/docs/reference/dashboard/list-views/list-page.mdx

@@ -103,7 +103,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/page/list-page.tsx" sourceLine="36" packageName="@vendure/dashboard" since="3.3.0" />
 
-Props to configure the <DocsLink href="/reference/dashboard/list-views/list-page#listpage">ListPage</DocsLink> component.
+Props to configure the [ListPage](/reference/dashboard/list-views/list-page#listpage) component.
 
 ```ts title="Signature"
 interface ListPageProps<T extends TypedDocumentNode<U, V>, U extends ListQueryShape, V extends ListQueryOptionsShape, AC extends AdditionalColumns<T>> {
@@ -435,7 +435,7 @@ Bulk actions are actions that can be applied to one or more table rows, and incl
 - Assigning the rows to another channel
 - Bulk editing some aspect of the rows
 
-See the <DocsLink href="/reference/dashboard/list-views/bulk-actions#bulkaction">BulkAction</DocsLink> docs for an example of how to build the component.
+See the [BulkAction](/reference/dashboard/list-views/bulk-actions#bulkaction) docs for an example of how to build the component.
 
 *Example*
 

docs/docs/reference/dashboard/list-views/paginated-list-data-table.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/paginated-list-data-table.tsx" sourceLine="366" packageName="@vendure/dashboard" since="3.4.0" />
 
-A wrapper around the <DocsLink href="/reference/dashboard/list-views/data-table#datatable">DataTable</DocsLink> component, which automatically configures functionality common to
+A wrapper around the [DataTable](/reference/dashboard/list-views/data-table#datatable) component, which automatically configures functionality common to
 list queries that implement the `PaginatedList` interface, which is the common way of representing lists
 of data in Vendure.
 
@@ -119,7 +119,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/components/shared/paginated-list-data-table.tsx" sourceLine="202" packageName="@vendure/dashboard" since="3.4.0" />
 
-Props to configure the <DocsLink href="/reference/dashboard/list-views/paginated-list-data-table#paginatedlistdatatable">PaginatedListDataTable</DocsLink> component.
+Props to configure the [PaginatedListDataTable](/reference/dashboard/list-views/paginated-list-data-table#paginatedlistdatatable) component.
 
 ```ts title="Signature"
 interface PaginatedListDataTableProps<T extends TypedDocumentNode<U, V>, U extends ListQueryShape, V extends ListQueryOptionsShape, AC extends AdditionalColumns<T>> {

docs/docs/reference/dashboard/page-layout/index.mdx

@@ -5,8 +5,8 @@ generated: true
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/layout-engine/page-layout.tsx" sourceLine="211" packageName="@vendure/dashboard" since="3.3.0" />
 
 *
-This component governs the layout of the contents of a <DocsLink href="/reference/dashboard/page-layout/page#page">Page</DocsLink> component.
-It should contain all the <DocsLink href="/reference/dashboard/page-layout/page-block#pageblock">PageBlock</DocsLink> components that are to be displayed on the page.
+This component governs the layout of the contents of a [Page](/reference/dashboard/page-layout/page#page) component.
+It should contain all the [PageBlock](/reference/dashboard/page-layout/page-block#pageblock) components that are to be displayed on the page.
 
 ```ts title="Signature"
 function PageLayout(props: Readonly<PageLayoutProps>): void

docs/docs/reference/dashboard/page-layout/page-action-bar.mdx

@@ -5,8 +5,8 @@ generated: true
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/layout-engine/page-layout.tsx" sourceLine="351" packageName="@vendure/dashboard" since="3.3.0" />
 
 *
-A component for displaying the main actions for a page. This should be used inside the <DocsLink href="/reference/dashboard/page-layout/page#page">Page</DocsLink> component.
-It should be used in conjunction with the <DocsLink href="/reference/dashboard/page-layout/page-action-bar#pageactionbarleft">PageActionBarLeft</DocsLink> and <DocsLink href="/reference/dashboard/page-layout/page-action-bar#pageactionbarright">PageActionBarRight</DocsLink> components
+A component for displaying the main actions for a page. This should be used inside the [Page](/reference/dashboard/page-layout/page#page) component.
+It should be used in conjunction with the [PageActionBarLeft](/reference/dashboard/page-layout/page-action-bar#pageactionbarleft) and [PageActionBarRight](/reference/dashboard/page-layout/page-action-bar#pageactionbarright) components
 as direct children.
 
 ```ts title="Signature"

docs/docs/reference/dashboard/page-layout/page-block.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/layout-engine/page-layout.tsx" sourceLine="591" packageName="@vendure/dashboard" since="3.3.0" />
 
 *
-A component for displaying a block of content on a page. This should be used inside the <DocsLink href="/reference/dashboard/page-layout/#pagelayout">PageLayout</DocsLink> component.
+A component for displaying a block of content on a page. This should be used inside the [PageLayout](/reference/dashboard/page-layout/#pagelayout) component.
 It should be provided with a `column` prop to determine which column it should appear in, and a `blockId` prop
 to identify the block.
 
@@ -28,7 +28,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/layout-engine/page-layout.tsx" sourceLine="540" packageName="@vendure/dashboard" since="3.3.0" />
 
-Props used to configure the <DocsLink href="/reference/dashboard/page-layout/page-block#pageblock">PageBlock</DocsLink> component.
+Props used to configure the [PageBlock](/reference/dashboard/page-layout/page-block#pageblock) component.
 
 ```ts title="Signature"
 type PageBlockProps = {
@@ -81,7 +81,7 @@ An optional set of CSS classes to apply to the block.
 **Status: Developer Preview**
 
 A component for displaying a block of content on a page that takes up the full width of the page.
-This should be used inside the <DocsLink href="/reference/dashboard/page-layout/#pagelayout">PageLayout</DocsLink> component.
+This should be used inside the [PageLayout](/reference/dashboard/page-layout/#pagelayout) component.
 
 ```ts title="Signature"
 function FullWidthPageBlock(props: Readonly<Pick<PageBlockProps, 'children' | 'className' | 'blockId'>>): void
@@ -96,7 +96,7 @@ Parameters
 
 *
 A component for displaying an auto-generated form for custom fields on a page.
-This is a special form of <DocsLink href="/reference/dashboard/page-layout/page-block#pageblock">PageBlock</DocsLink> that automatically generates
+This is a special form of [PageBlock](/reference/dashboard/page-layout/page-block#pageblock) that automatically generates
 a form corresponding to the custom fields for the given entity type.
 
 *Example*

docs/docs/reference/dashboard/page-layout/page-title.mdx

@@ -4,7 +4,7 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/layout-engine/page-layout.tsx" sourceLine="336" packageName="@vendure/dashboard" since="3.3.0" />
 
-A component for displaying the title of a page. This should be used inside the <DocsLink href="/reference/dashboard/page-layout/page#page">Page</DocsLink> component.
+A component for displaying the title of a page. This should be used inside the [Page](/reference/dashboard/page-layout/page#page) component.
 
 ```ts title="Signature"
 function PageTitle(props: Readonly<{ children: React.ReactNode }>): void

docs/docs/reference/dashboard/page-layout/page.mdx

@@ -9,9 +9,9 @@ a consistent layout as well as a context for the slot-based PageBlock system.
 
 The typical hierarchy of a page is as follows:
 - `Page`
- - <DocsLink href="/reference/dashboard/page-layout/page-title#pagetitle">PageTitle</DocsLink>
- - <DocsLink href="/reference/dashboard/page-layout/page-action-bar#pageactionbar">PageActionBar</DocsLink>
- - <DocsLink href="/reference/dashboard/page-layout/#pagelayout">PageLayout</DocsLink>
+ - [PageTitle](/reference/dashboard/page-layout/page-title#pagetitle)
+ - [PageActionBar](/reference/dashboard/page-layout/page-action-bar#pageactionbar)
+ - [PageLayout](/reference/dashboard/page-layout/#pagelayout)
 
 *Example*
 
@@ -50,7 +50,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/src/lib/framework/layout-engine/page-layout.tsx" sourceLine="38" packageName="@vendure/dashboard" since="3.3.0" />
 
-The props used to configure the <DocsLink href="/reference/dashboard/page-layout/page#page">Page</DocsLink> component.
+The props used to configure the [Page](/reference/dashboard/page-layout/page#page) component.
 
 ```ts title="Signature"
 interface PageProps extends ComponentProps<'div'> {

docs/docs/reference/dashboard/vite-plugin/vendure-dashboard-plugin.mdx

@@ -21,7 +21,7 @@ Parameters
 
 <GenerationInfo sourceFile="packages/dashboard/vite/vite-plugin-vendure-dashboard.ts" sourceLine="32" packageName="@vendure/dashboard" since="3.4.0" />
 
-Options for the <DocsLink href="/reference/dashboard/vite-plugin/vendure-dashboard-plugin#venduredashboardplugin">vendureDashboardPlugin</DocsLink> Vite plugin.
+Options for the [vendureDashboardPlugin](/reference/dashboard/vite-plugin/vendure-dashboard-plugin#venduredashboardplugin) Vite plugin.
 
 ```ts title="Signature"
 type VitePluginVendureDashboardOptions = {
@@ -201,7 +201,7 @@ A function to determine the path to the compiled Vendure config file.
 </div>
 <GenerationInfo sourceFile="packages/dashboard/vite/vite-plugin-ui-config.ts" sourceLine="19" packageName="@vendure/dashboard" since="3.4.0" />
 
-Options used by the <DocsLink href="/reference/dashboard/vite-plugin/vendure-dashboard-plugin#venduredashboardplugin">vendureDashboardPlugin</DocsLink> to configure how the Dashboard
+Options used by the [vendureDashboardPlugin](/reference/dashboard/vite-plugin/vendure-dashboard-plugin#venduredashboardplugin) to configure how the Dashboard
 connects to the Vendure Admin API
 
 ```ts title="Signature"
@@ -260,7 +260,7 @@ setting of the server's `apiOptions.channelTokenKey` config option.
 </div>
 <GenerationInfo sourceFile="packages/dashboard/vite/vite-plugin-ui-config.ts" sourceLine="81" packageName="@vendure/dashboard" since="3.4.0" />
 
-Options used by the <DocsLink href="/reference/dashboard/vite-plugin/vendure-dashboard-plugin#venduredashboardplugin">vendureDashboardPlugin</DocsLink> to configure aspects of the
+Options used by the [vendureDashboardPlugin](/reference/dashboard/vite-plugin/vendure-dashboard-plugin#venduredashboardplugin) to configure aspects of the
 Dashboard UI behaviour.
 
 ```ts title="Signature"
@@ -304,7 +304,7 @@ An array of locales to be used on Admin UI.
 </div>
 <GenerationInfo sourceFile="packages/dashboard/vite/vite-plugin-ui-config.ts" sourceLine="124" packageName="@vendure/dashboard" since="3.4.0" />
 
-Options used by the <DocsLink href="/reference/dashboard/vite-plugin/vendure-dashboard-plugin#venduredashboardplugin">vendureDashboardPlugin</DocsLink> to configure aspects of the
+Options used by the [vendureDashboardPlugin](/reference/dashboard/vite-plugin/vendure-dashboard-plugin#venduredashboardplugin) to configure aspects of the
 Dashboard UI behaviour.
 
 ```ts title="Signature"

docs/docs/reference/typescript-api/assets/asset-naming-strategy.mdx

@@ -20,7 +20,7 @@ interface AssetNamingStrategy extends InjectableStrategy {
     generatePreviewFileName(ctx: RequestContext, sourceFileName: string, conflictFileName?: string): string;
 }
 ```
-* Extends: <DocsLink href="/reference/typescript-api/common/injectable-strategy#injectablestrategy">`InjectableStrategy`</DocsLink>
+* Extends: [`InjectableStrategy`](/reference/typescript-api/common/injectable-strategy#injectablestrategy)