@vendure/docs 0.0.0-202601201808 → 0.0.0-202601211028

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

@@ -2,13 +2,9 @@
 title: "BullMQPluginOptions"
 generated: true
 ---
-
-
-## BullMQPluginOptions
-
 <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 <a href='/reference/core-plugins/job-queue-plugin/bull-mqjob-queue-plugin#bullmqjobqueueplugin'>BullMQJobQueuePlugin</a>.
+Configuration options for the <DocsLink href="/reference/core-plugins/job-queue-plugin/bull-mqjob-queue-plugin#bullmqjobqueueplugin">BullMQJobQueuePlugin</DocsLink>.
 
 ```ts title="Signature"
 interface BullMQPluginOptions {
@@ -33,21 +29,21 @@ creating a new Queue, Worker and Scheduler instance.
 If omitted, it will attempt to connect to Redis at `127.0.0.1:6379`.
 ### queueOptions
 
-<MemberInfo kind="property" type={`Omit&#60;QueueOptions, 'connection'&#62;`}   />
+<MemberInfo kind="property" type={`Omit<QueueOptions, 'connection'>`}   />
 
 Additional options used when instantiating the BullMQ
 Queue instance.
 See the [BullMQ QueueOptions docs](https://github.com/taskforcesh/bullmq/blob/master/docs/gitbook/api/bullmq.queueoptions.md)
 ### workerOptions
 
-<MemberInfo kind="property" type={`Omit&#60;WorkerOptions, 'connection'&#62;`}   />
+<MemberInfo kind="property" type={`Omit<WorkerOptions, 'connection'>`}   />
 
 Additional options used when instantiating the BullMQ
 Worker instance.
 See the [BullMQ WorkerOptions docs](https://github.com/taskforcesh/bullmq/blob/master/docs/gitbook/api/bullmq.workeroptions.md)
 ### setRetries
 
-<MemberInfo kind="property" type={`(queueName: string, job: Job) =&#62; number`}  since="1.3.0"  />
+<MemberInfo kind="property" type={`(queueName: string, job: Job) => number`}  since="1.3.0"  />
 
 When a job is added to the JobQueue using `JobQueue.add()`, the calling
 code may specify the number of retries in case of failure. This option allows
@@ -69,7 +65,7 @@ setRetries: (queueName, job) => {
  ```
 ### setBackoff
 
-<MemberInfo kind="property" type={`(queueName: string, job: Job) =&#62; <a href='/reference/core-plugins/job-queue-plugin/bull-mqplugin-options#backoffoptions'>BackoffOptions</a> | undefined`} default={`'exponential', 1000`}  since="1.3.0"  />
+<MemberInfo kind="property" type={`(queueName: string, job: Job) => <a href='/reference/core-plugins/job-queue-plugin/bull-mqplugin-options#backoffoptions'>BackoffOptions</a> | undefined`} default={`'exponential', 1000`}  since="1.3.0"  />
 
 This allows you to specify the backoff settings when a failed job gets retried.
 In other words, this determines how much time should pass before attempting to
@@ -88,7 +84,7 @@ setBackoff: (queueName, job) => {
 ```
 ### setJobOptions
 
-<MemberInfo kind="property" type={`(queueName: string, job: Job) =&#62; BullJobsOptions`}  since="3.2.0"  />
+<MemberInfo kind="property" type={`(queueName: string, job: Job) => BullJobsOptions`}  since="3.2.0"  />
 
 This allows you to specify additional options for a job when it is added to the queue.
 The object returned is the BullMQ [JobsOptions](https://api.docs.bullmq.io/types/v5.JobsOptions.html)
@@ -109,10 +105,6 @@ setJobOptions: (queueName, job) => {
 
 
 </div>
-
-
-## BackoffOptions
-
 <GenerationInfo sourceFile="packages/job-queue-plugin/src/bullmq/types.ts" sourceLine="122" packageName="@vendure/job-queue-plugin" since="1.3.0" />
 
 Configuration for the backoff function when retrying failed jobs.

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

@@ -2,14 +2,10 @@
 title: "PubSubJobQueueStrategy"
 generated: true
 ---
-
-
-## PubSubJobQueueStrategy
-
 <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 <a href='/reference/core-plugins/job-queue-plugin/pub-sub-plugin#pubsubplugin'>PubSubPlugin</a>.
+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>.
 
 Note: To use this strategy, you need to manually install the `@google-cloud/pubsub` package:
 
@@ -46,17 +42,17 @@ class PubSubJobQueueStrategy extends InjectableJobQueueStrategy implements JobQu
 
 ### add
 
-<MemberInfo kind="method" type={`(job: Job&#60;Data&#62;) => Promise&#60;Job&#60;Data&#62;&#62;`}   />
+<MemberInfo kind="method" type={`(job: Job<Data>) => Promise<Job<Data>>`}   />
 
 
 ### start
 
-<MemberInfo kind="method" type={`(queueName: string, process: (job: Job&#60;Data&#62;) =&#62; Promise&#60;any&#62;) => `}   />
+<MemberInfo kind="method" type={`(queueName: string, process: (job: Job<Data>) => Promise<any>) => `}   />
 
 
 ### stop
 
-<MemberInfo kind="method" type={`(queueName: string, process: (job: Job&#60;Data&#62;) =&#62; Promise&#60;any&#62;) => `}   />
+<MemberInfo kind="method" type={`(queueName: string, process: (job: Job<Data>) => Promise<any>) => `}   />
 
 
 

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

@@ -2,10 +2,6 @@
 title: "PubSubPlugin"
 generated: true
 ---
-
-
-## PubSubPlugin
-
 <GenerationInfo sourceFile="packages/job-queue-plugin/src/pub-sub/plugin.ts" sourceLine="22" packageName="@vendure/job-queue-plugin" />
 
 This plugin uses Google Cloud Pub/Sub to implement a job queue strategy for Vendure.
@@ -27,7 +23,7 @@ class PubSubPlugin {
 
 ### init
 
-<MemberInfo kind="method" type={`(options: PubSubOptions) => Type&#60;<a href='/reference/core-plugins/job-queue-plugin/pub-sub-plugin#pubsubplugin'>PubSubPlugin</a>&#62;`}   />
+<MemberInfo kind="method" type={`(options: PubSubOptions) => Type<<a href='/reference/core-plugins/job-queue-plugin/pub-sub-plugin#pubsubplugin'>PubSubPlugin</a>>`}   />
 
 
 

package/docs/reference/core-plugins/payments-plugin/braintree-plugin.mdx

@@ -2,10 +2,6 @@
 title: "BraintreePlugin"
 generated: true
 ---
-
-
-## BraintreePlugin
-
 <GenerationInfo sourceFile="packages/payments-plugin/src/braintree/braintree.plugin.ts" sourceLine="241" packageName="@vendure/payments-plugin" />
 
 This plugin enables payments to be processed by [Braintree](https://www.braintreepayments.com/), a popular payment provider.
@@ -251,16 +247,12 @@ class BraintreePlugin {
 
 ### init
 
-<MemberInfo kind="method" type={`(options: <a href='/reference/core-plugins/payments-plugin/braintree-plugin#braintreepluginoptions'>BraintreePluginOptions</a>) => Type&#60;<a href='/reference/core-plugins/payments-plugin/braintree-plugin#braintreeplugin'>BraintreePlugin</a>&#62;`}   />
+<MemberInfo kind="method" type={`(options: <a href='/reference/core-plugins/payments-plugin/braintree-plugin#braintreepluginoptions'>BraintreePluginOptions</a>) => Type<<a href='/reference/core-plugins/payments-plugin/braintree-plugin#braintreeplugin'>BraintreePlugin</a>>`}   />
 
 
 
 
 </div>
-
-
-## BraintreePluginOptions
-
 <GenerationInfo sourceFile="packages/payments-plugin/src/braintree/types.ts" sourceLine="25" packageName="@vendure/payments-plugin" />
 
 Options for the Braintree plugin.
@@ -293,7 +285,7 @@ Since v1.8, it is possible to override vaulting on a per-payment basis by passin
 `generateBraintreeClientToken` mutation.
 ### extractMetadata
 
-<MemberInfo kind="property" type={`(transaction: <a href='/reference/typescript-api/request/transaction-decorator#transaction'>Transaction</a>) =&#62; PaymentMetadata`}  since="1.7.0"  />
+<MemberInfo kind="property" type={`(transaction: <a href='/reference/typescript-api/request/transaction-decorator#transaction'>Transaction</a>) => PaymentMetadata`}  since="1.7.0"  />
 
 Allows you to configure exactly what information from the Braintree
 [Transaction object](https://developer.paypal.com/braintree/docs/reference/response/transaction#result-object) (which is returned by the

package/docs/reference/core-plugins/payments-plugin/mollie-plugin.mdx

@@ -2,10 +2,6 @@
 title: "MolliePlugin"
 generated: true
 ---
-
-
-## MolliePlugin
-
 <GenerationInfo sourceFile="packages/payments-plugin/src/mollie/mollie.plugin.ts" sourceLine="195" packageName="@vendure/payments-plugin" />
 
 Plugin to enable payments through the [Mollie platform](https://docs.mollie.com/).
@@ -140,10 +136,6 @@ Initialize the mollie payment plugin
 
 
 </div>
-
-
-## MolliePluginOptions
-
 <GenerationInfo sourceFile="packages/payments-plugin/src/mollie/mollie.plugin.ts" sourceLine="28" packageName="@vendure/payments-plugin" />
 
 Configuration options for the Mollie payments plugin.
@@ -169,7 +161,7 @@ The host of your Vendure server, e.g. `'https://my-vendure.io'`.
 This is used by Mollie to send webhook events to the Vendure server
 ### enabledPaymentMethodsParams
 
-<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a> | null,     ) =&#62; AdditionalEnabledPaymentMethodsParams | Promise&#60;AdditionalEnabledPaymentMethodsParams&#62;`}  since="2.2.0"  />
+<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a> | null,     ) => AdditionalEnabledPaymentMethodsParams | Promise<AdditionalEnabledPaymentMethodsParams>`}  since="2.2.0"  />
 
 Provide additional parameters to the Mollie enabled payment methods API call. By default,
 the plugin will already pass the `resource` parameter.

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

@@ -2,10 +2,6 @@
 title: "StripePlugin"
 generated: true
 ---
-
-
-## StripePlugin
-
 <GenerationInfo sourceFile="packages/payments-plugin/src/stripe/stripe.plugin.ts" sourceLine="160" packageName="@vendure/payments-plugin" />
 
 Plugin to enable payments through [Stripe](https://stripe.com/docs) via the Payment Intents API.
@@ -41,7 +37,7 @@ the Stripe CLI to test your webhook locally. See the _local development_ section
       }),
     ]
     ````
-    For all the plugin options, see the <a href='/reference/core-plugins/payments-plugin/stripe-plugin#stripepluginoptions'>StripePluginOptions</a> type.
+    For all the plugin options, see the <DocsLink href="/reference/core-plugins/payments-plugin/stripe-plugin#stripepluginoptions">StripePluginOptions</DocsLink> 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.
 
@@ -167,16 +163,12 @@ class StripePlugin {
 
 ### init
 
-<MemberInfo kind="method" type={`(options: <a href='/reference/core-plugins/payments-plugin/stripe-plugin#stripepluginoptions'>StripePluginOptions</a>) => Type&#60;<a href='/reference/core-plugins/payments-plugin/stripe-plugin#stripeplugin'>StripePlugin</a>&#62;`}   />
+<MemberInfo kind="method" type={`(options: <a href='/reference/core-plugins/payments-plugin/stripe-plugin#stripepluginoptions'>StripePluginOptions</a>) => Type<<a href='/reference/core-plugins/payments-plugin/stripe-plugin#stripeplugin'>StripePlugin</a>>`}   />
 
 Initialize the Stripe payment plugin
 
 
 </div>
-
-
-## StripePluginOptions
-
 <GenerationInfo sourceFile="packages/payments-plugin/src/stripe/types.ts" sourceLine="29" packageName="@vendure/payments-plugin" />
 
 Configuration options for the Stripe payments plugin.
@@ -220,7 +212,7 @@ to be used with the same PaymentIntent. This is done by adding a custom field to
 the Stripe customer ID, so switching this on will require a database migration / synchronization.
 ### metadata
 
-<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a>,     ) =&#62; Stripe.MetadataParam | Promise&#60;Stripe.MetadataParam&#62;`}  since="1.9.7"  />
+<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a>,     ) => Stripe.MetadataParam | Promise<Stripe.MetadataParam>`}  since="1.9.7"  />
 
 Attach extra metadata to Stripe payment intent creation call.
 
@@ -250,7 +242,7 @@ Note: If the `paymentIntentCreateParams` is also used and returns a `metadata` k
 returned by both functions will be merged.
 ### paymentIntentCreateParams
 
-<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a>,     ) =&#62; AdditionalPaymentIntentCreateParams | Promise&#60;AdditionalPaymentIntentCreateParams&#62;`}  since="2.1.0"  />
+<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a>,     ) => AdditionalPaymentIntentCreateParams | Promise<AdditionalPaymentIntentCreateParams>`}  since="2.1.0"  />
 
 Provide additional parameters to the Stripe payment intent creation. By default,
 the plugin will already pass the `amount`, `currency`, `customer` and `automatic_payment_methods: { enabled: true }` parameters.
@@ -278,7 +270,7 @@ export const config: VendureConfig = {
 ```
 ### requestOptions
 
-<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a>,     ) =&#62; AdditionalRequestOptions | Promise&#60;AdditionalRequestOptions&#62;`}  since="3.1.0"  />
+<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a>,     ) => AdditionalRequestOptions | Promise<AdditionalRequestOptions>`}  since="3.1.0"  />
 
 Provide additional options to the Stripe payment intent creation. By default,
 the plugin will already pass the `idempotencyKey` parameter.
@@ -306,7 +298,7 @@ export const config: VendureConfig = {
 ```
 ### customerCreateParams
 
-<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a>,     ) =&#62; AdditionalCustomerCreateParams | Promise&#60;AdditionalCustomerCreateParams&#62;`}  since="2.1.0"  />
+<MemberInfo kind="property" type={`(         injector: <a href='/reference/typescript-api/common/injector#injector'>Injector</a>,         ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>,         order: <a href='/reference/typescript-api/entities/order#order'>Order</a>,     ) => AdditionalCustomerCreateParams | Promise<AdditionalCustomerCreateParams>`}  since="2.1.0"  />
 
 Provide additional parameters to the Stripe customer creation. By default,
 the plugin will already pass the `email` and `name` parameters.

package/docs/reference/core-plugins/sentry-plugin/index.mdx

@@ -2,10 +2,6 @@
 title: "SentryPlugin"
 generated: true
 ---
-
-
-## SentryPlugin
-
 <GenerationInfo sourceFile="packages/sentry-plugin/src/sentry-plugin.ts" sourceLine="146" packageName="@vendure/sentry-plugin" />
 
 This plugin integrates the [Sentry](https://sentry.io) error tracking & performance monitoring

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

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

package/docs/reference/core-plugins/sentry-plugin/sentry-service.mdx

@@ -2,10 +2,6 @@
 title: "SentryService"
 generated: true
 ---
-
-
-## SentryService
-
 <GenerationInfo sourceFile="packages/sentry-plugin/src/sentry.service.ts" sourceLine="13" packageName="@vendure/sentry-plugin" />
 
 Service for capturing errors and messages to Sentry.

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

@@ -2,10 +2,6 @@
 title: "StellatePlugin"
 generated: true
 ---
-
-
-## StellatePlugin
-
 <GenerationInfo sourceFile="packages/stellate-plugin/src/stellate-plugin.ts" sourceLine="246" packageName="@vendure/stellate-plugin" since="2.1.5" />
 
 A plugin to integrate the [Stellate](https://stellate.co/) GraphQL caching service with your Vendure server.
@@ -29,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 <a href='/reference/core-plugins/stellate-plugin/purge-rule#purgerule'>PurgeRule</a>s which
+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
 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).
 
@@ -152,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 <a href='/reference/core-plugins/stellate-plugin/purge-rule#purgerule'>PurgeRule</a> comes in.
+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.
 
 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:
@@ -180,7 +176,7 @@ const config: Config = {
 export default config;
 ```
 
-You can then add a custom <a href='/reference/core-plugins/stellate-plugin/purge-rule#purgerule'>PurgeRule</a> to the StellatePlugin configuration:
+You can then add a custom <DocsLink href="/reference/core-plugins/stellate-plugin/purge-rule#purgerule">PurgeRule</DocsLink> to the StellatePlugin configuration:
 
 *Example*
 

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

@@ -2,15 +2,11 @@
 title: "PurgeRule"
 generated: true
 ---
-
-
-## PurgeRule
-
 <GenerationInfo sourceFile="packages/stellate-plugin/src/purge-rule.ts" sourceLine="49" packageName="@vendure/stellate-plugin" />
 
 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 <a href='/reference/core-plugins/stellate-plugin/stellate-service#stellateservice'>StellateService</a> instance.
+the provided <DocsLink href="/reference/core-plugins/stellate-plugin/stellate-service#stellateservice">StellateService</DocsLink> instance.
 
 ```ts title="Signature"
 class PurgeRule<Event extends VendureEvent = VendureEvent> {
@@ -25,7 +21,7 @@ class PurgeRule<Event extends VendureEvent = VendureEvent> {
 
 ### eventType
 
-<MemberInfo kind="property" type={`Type&#60;Event&#62;`}   />
+<MemberInfo kind="property" type={`Type<Event>`}   />
 
 
 ### bufferTimeMs
@@ -40,19 +36,15 @@ class PurgeRule<Event extends VendureEvent = VendureEvent> {
 
 ### constructor
 
-<MemberInfo kind="method" type={`(config: <a href='/reference/core-plugins/stellate-plugin/purge-rule#purgeruleconfig'>PurgeRuleConfig</a>&#60;Event&#62;) => PurgeRule`}   />
+<MemberInfo kind="method" type={`(config: <a href='/reference/core-plugins/stellate-plugin/purge-rule#purgeruleconfig'>PurgeRuleConfig</a><Event>) => PurgeRule`}   />
 
 
 
 
 </div>
-
-
-## PurgeRuleConfig
-
 <GenerationInfo sourceFile="packages/stellate-plugin/src/purge-rule.ts" sourceLine="13" packageName="@vendure/stellate-plugin" />
 
-Configures a <a href='/reference/core-plugins/stellate-plugin/purge-rule#purgerule'>PurgeRule</a>.
+Configures a <DocsLink href="/reference/core-plugins/stellate-plugin/purge-rule#purgerule">PurgeRule</DocsLink>.
 
 ```ts title="Signature"
 interface PurgeRuleConfig<Event extends VendureEvent> {
@@ -70,7 +62,7 @@ interface PurgeRuleConfig<Event extends VendureEvent> {
 
 ### eventType
 
-<MemberInfo kind="property" type={`Type&#60;Event&#62;`}   />
+<MemberInfo kind="property" type={`Type<Event>`}   />
 
 Specifies which VendureEvent will trigger this purge rule.
 ### bufferTime
@@ -81,10 +73,10 @@ How long to buffer events for in milliseconds before executing the handler. This
 us to efficiently batch calls to the Stellate Purge API.
 ### handler
 
-<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>;     }) =&#62; void | Promise&#60;void&#62;`}   />
+<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
-<a href='/reference/core-plugins/stellate-plugin/stellate-service#stellateservice'>StellateService</a> instance to call the Stellate Purge API.
+<DocsLink href="/reference/core-plugins/stellate-plugin/stellate-service#stellateservice">StellateService</DocsLink> instance to call the Stellate Purge API.
 
 
 </div>

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

@@ -2,10 +2,6 @@
 title: "StellatePluginOptions"
 generated: true
 ---
-
-
-## StellatePluginOptions
-
 <GenerationInfo sourceFile="packages/stellate-plugin/src/types.ts" sourceLine="9" packageName="@vendure/stellate-plugin" />
 
 Configuration options for the StellatePlugin.
@@ -38,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 <a href='/reference/core-plugins/stellate-plugin/purge-rule#purgerule'>PurgeRule</a> instances which are used to define how the plugin will
+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
 respond to Vendure events in order to trigger calls to the Stellate Purging API.
 ### defaultBufferTimeMs
 

package/docs/reference/core-plugins/stellate-plugin/stellate-service.mdx

@@ -2,10 +2,6 @@
 title: "StellateService"
 generated: true
 ---
-
-
-## StellateService
-
 <GenerationInfo sourceFile="packages/stellate-plugin/src/service/stellate.service.ts" sourceLine="23" packageName="@vendure/stellate-plugin" />
 
 The StellateService is used to purge the Stellate cache when certain events occur.
@@ -42,7 +38,7 @@ Purges the cache for the given Products.
 Purges the cache for the given ProductVariants.
 ### purgeSearchResults
 
-<MemberInfo kind="method" type={`(items: Array&#60;<a href='/reference/typescript-api/entities/product-variant#productvariant'>ProductVariant</a> | <a href='/reference/typescript-api/entities/product#product'>Product</a>&#62;) => `}   />
+<MemberInfo kind="method" type={`(items: Array<<a href='/reference/typescript-api/entities/product-variant#productvariant'>ProductVariant</a> | <a href='/reference/typescript-api/entities/product#product'>Product</a>>) => `}   />
 
 Purges the cache for SearchResults which contain the given Products or ProductVariants.
 ### purgeAllOfType

package/docs/reference/core-plugins/telemetry-plugin/get-sdk-configuration.mdx

@@ -2,10 +2,6 @@
 title: "GetSdkConfiguration"
 generated: true
 ---
-
-
-## getSdkConfiguration
-
 <GenerationInfo sourceFile="packages/telemetry-plugin/src/instrumentation.ts" sourceLine="89" packageName="@vendure/telemetry-plugin" />
 
 Creates a configuration object for the OpenTelemetry Node SDK. This is used to set up a custom
@@ -58,10 +54,6 @@ Parameters
 
 <MemberInfo kind="parameter" type={`<a href='/reference/core-plugins/telemetry-plugin/get-sdk-configuration#sdkconfigurationoptions'>SdkConfigurationOptions</a>`} />
 
-
-
-## SdkConfigurationOptions
-
 <GenerationInfo sourceFile="packages/telemetry-plugin/src/instrumentation.ts" sourceLine="27" packageName="@vendure/telemetry-plugin" />
 
 Options for configuring the OpenTelemetry Node SDK.
@@ -83,7 +75,7 @@ When set to `true`, the SDK will log spans to the console instead of sending the
 exporter. This should just be used for debugging purposes.
 ### config
 
-<MemberInfo kind="property" type={`Partial&#60;NodeSDKConfiguration&#62;`}   />
+<MemberInfo kind="property" type={`Partial<NodeSDKConfiguration>`}   />
 
 The configuration object for the OpenTelemetry Node SDK.
 

package/docs/reference/core-plugins/telemetry-plugin/index.mdx

@@ -2,10 +2,6 @@
 title: "TelemetryPlugin"
 generated: true
 ---
-
-
-## TelemetryPlugin
-
 <GenerationInfo sourceFile="packages/telemetry-plugin/src/telemetry.plugin.ts" sourceLine="107" packageName="@vendure/telemetry-plugin" since="3.3.0" />
 
 The TelemetryPlugin is used to instrument the Vendure application and collect telemetry data using

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

@@ -2,10 +2,6 @@
 title: "OtelLogger"
 generated: true
 ---
-
-
-## OtelLogger
-
 <GenerationInfo sourceFile="packages/telemetry-plugin/src/config/otel-logger.ts" sourceLine="46" packageName="@vendure/telemetry-plugin" since="3.3.0" />
 
 A logger that emits logs to OpenTelemetry and optionally to the console.
@@ -59,10 +55,6 @@ class OtelLogger implements VendureLogger {
 
 
 </div>
-
-
-## OtelLoggerOptions
-
 <GenerationInfo sourceFile="packages/telemetry-plugin/src/config/otel-logger.ts" sourceLine="14" packageName="@vendure/telemetry-plugin" since="3.3.0" />
 
 Options for the OtelLogger.

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

@@ -2,16 +2,12 @@
 title: "RegisterMethodHooks"
 generated: true
 ---
-
-
-## registerMethodHooks
-
 <GenerationInfo sourceFile="packages/telemetry-plugin/src/service/method-hooks.service.ts" sourceLine="60" packageName="@vendure/telemetry-plugin" since="3.3.0" />
 
 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 <a href='/reference/core-plugins/telemetry-plugin/#telemetryplugin'>TelemetryPlugin</a> via the <a href='/reference/core-plugins/telemetry-plugin/telemetry-plugin-options#telemetrypluginoptions'>TelemetryPluginOptions</a>.
+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>.
 
 *Example*
 
@@ -37,9 +33,9 @@ Parameters
 
 ### target
 
-<MemberInfo kind="parameter" type={`Type&#60;T&#62;`} />
+<MemberInfo kind="parameter" type={`Type<T>`} />
 
 ### hooks
 
-<MemberInfo kind="parameter" type={`MethodHooksForType&#60;T&#62;`} />
+<MemberInfo kind="parameter" type={`MethodHooksForType<T>`} />
 

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

@@ -2,10 +2,6 @@
 title: "TelemetryPluginOptions"
 generated: true
 ---
-
-
-## TelemetryPluginOptions
-
 <GenerationInfo sourceFile="packages/telemetry-plugin/src/types.ts" sourceLine="18" packageName="@vendure/telemetry-plugin" since="3.3.0" />
 
 Configuration options for the TelemetryPlugin.
@@ -38,14 +34,14 @@ TelemetryPlugin.init({
 ```
 ### methodHooks
 
-<MemberInfo kind="property" type={`Array&#60;MethodHookConfig&#60;any&#62;&#62;`}  experimental="true" />
+<MemberInfo kind="property" type={`Array<MethodHookConfig<any>>`}  experimental="true" />
 
 **Status: Developer Preview**
 
 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 <a href='/reference/core-plugins/telemetry-plugin/register-method-hooks#registermethodhooks'>registerMethodHooks</a> function.
+To define hooks on a method, use the <DocsLink href="/reference/core-plugins/telemetry-plugin/register-method-hooks#registermethodhooks">registerMethodHooks</DocsLink> function.
 
 *Example*