@vendure/docs 0.0.0-202601280949 → 0.0.0-202601281114

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

package/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:
 

package/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.
 

package/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.
 

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

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

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

package/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"  />

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

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

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

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

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

package/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:
 

package/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.
 

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

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

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

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

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

package/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"

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

package/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'>`
 
 
 

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

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