@vendure/docs 0.0.0-202601221213 → 0.0.0-202601280949

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

@@ -6,9 +6,9 @@ A CMS integration plugin allows you to automatically synchronize your Vendure pr
 
 This is done in a way that establishes Vendure as the source of truth for the ecommerce's data.
 
-This guide demonstrates how to build a production-ready CMS integration plugin. The principles covered here are designed to be CMS-agnostic, however we do have [working examples](/guides/how-to/cms-integration-plugin/#platform-specific-setup) for various platforms.
+This guide demonstrates how to build a production-ready CMS integration plugin. The principles covered here are designed to be CMS-agnostic, however we do have [working examples](/how-to/cms-integration-plugin/#platform-specific-setup) for various platforms.
 
-Platfroms covered in the [guide](/guides/how-to/cms-integration-plugin/#platform-specific-setup):
+Platfroms covered in the [guide](/how-to/cms-integration-plugin/#platform-specific-setup):
 
 - [Payload](https://payloadcms.com/)
 - [Sanity](https://www.sanity.io/)
@@ -27,16 +27,16 @@ The code examples in this guide are simplified for educational purposes. The act
 ## Prerequisites
 
 - Node.js 20+ with npm package manager
-- An existing Vendure project created with the [Vendure create command](/guides/getting-started/installation/)
+- An existing Vendure project created with the [Vendure create command](/getting-started/installation/)
 - An access key to a CMS platform that provides an API
 
 ## Core Concepts
 
-This [plugin](/guides/developer-guide/plugins/) leverages several key Vendure concepts:
+This [plugin](/developer-guide/plugins/) leverages several key Vendure concepts:
 
-- **[EventBus](/guides/developer-guide/events/)**: Provides real-time notifications when entities are created, updated, or deleted.
-- **[Job Queues](/guides/developer-guide/worker-job-queue/)**: Ensures that synchronization tasks are performed reliably and asynchronously, with retries on failure.
-- **[Plugin API](/guides/developer-guide/plugins/)**: The foundation for extending Vendure with custom capabilities.
+- **[EventBus](/developer-guide/events/)**: Provides real-time notifications when entities are created, updated, or deleted.
+- **[Job Queues](/developer-guide/worker-job-queue/)**: Ensures that synchronization tasks are performed reliably and asynchronously, with retries on failure.
+- **[Plugin API](/developer-guide/plugins/)**: The foundation for extending Vendure with custom capabilities.
 
 ## How It Works
 
@@ -92,11 +92,11 @@ npx vendure add -s CmsSpecificService --selected-plugin CmsPlugin
 # Explained later in the Event-Driven Synchronization Section
 ```
 
-Now we start by defining the main [plugin](/guides/developer-guide/plugins/) class, its [services](/guides/developer-guide/the-service-layer/), and the configuration types.
+Now we start by defining the main [plugin](/developer-guide/plugins/) class, its [services](/developer-guide/the-service-layer/), and the configuration types.
 
 ### Plugin Definition
 
-The `CmsPlugin` class registers the necessary [services](/guides/developer-guide/the-service-layer/) (`CmsSyncService`, `CmsSpecificService`) and sets up any Admin API extensions.
+The `CmsPlugin` class registers the necessary [services](/developer-guide/the-service-layer/) (`CmsSyncService`, `CmsSpecificService`) and sets up any Admin API extensions.
 
 ```ts title="src/plugins/cms/cms.plugin.ts"
 import { VendurePlugin, PluginCommonModule, Type, OnModuleInit } from '@vendure/core';
@@ -161,9 +161,9 @@ export interface SyncResponse {
 
 ## Event-Driven Synchronization
 
-The plugin uses Vendure's [EventBus](/guides/developer-guide/events/) to capture changes in real-time.
+The plugin uses Vendure's [EventBus](/developer-guide/events/) to capture changes in real-time.
 
-In the [onModuleInit](/guides/developer-guide/events/#subscribing-to-events) lifecycle hook, we create job queues and subscribe to entity events.
+In the [onModuleInit](/developer-guide/events/#subscribing-to-events) lifecycle hook, we create job queues and subscribe to entity events.
 
 ### Creating Job Queues and Subscribing to Events
 
@@ -280,7 +280,7 @@ The sync service handles several critical functions:
 
 ### Service Structure and Dependencies
 
-The service follows Vendure's [dependency injection pattern](/guides/developer-guide/the-service-layer/) and requires several core Vendure services:
+The service follows Vendure's [dependency injection pattern](/developer-guide/the-service-layer/) and requires several core Vendure services:
 
 ```ts title="src/plugins/cms/services/cms-sync.service.ts"
 @Injectable()
@@ -395,7 +395,7 @@ async findCollectionsForVariant(
 }
 ```
 
-:::info Additional Entity Types
+:::info[Additional Entity Types]
 The service can also includes `syncVariantToCms()` and `syncCollectionToCms()` methods that follow the same pattern as the product sync shown above.
 
 These implementations are omitted from this guide for brevity, but they handle their respective entity types with similar data fetching, relationship resolution, and error handling patterns.
@@ -410,7 +410,7 @@ This sync service provides the foundation for handling all Vendure-specific comp
 <Tabs>
 <TabItem value="storyblok" label="Storyblok">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Storyblok implementation can be found in the [Storyblok integration example](https://github.com/vendurehq/examples/tree/master/examples/storyblok-cms-integration). Refer to it for a minimal working implementation.
 :::
 
@@ -728,7 +728,7 @@ The complete implementations can be found in the working [example repositories](
 </TabItem>
 <TabItem value="contentful" label="Contentful">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Contentful implementation can be found in the [Contentful integration example](https://github.com/vendurehq/examples/tree/master/examples/contentful-cms-integration). It includes advanced features like locale mapping, bulk operations, and a robust setup process.
 :::
 
@@ -966,7 +966,7 @@ This same pattern is used to link variants to their parent product and to their
 
 These methods perform the core Create, Read, Update, and Delete logic. They rely on our centralized `makeContentfulRequest` method and handle the specifics of Contentful's API, such as versioning and the publish workflow.
 
-:::info Contentful's Publish Workflow
+:::info[Contentful's Publish Workflow]
 Contentful requires entries to be explicitly published before they are visible in the Delivery API. After creating or updating an entry, we must make a separate API call to publish it. Similarly, to delete an entry, it must first be unpublished.
 :::
 
@@ -1052,7 +1052,7 @@ This configuration provides a complete Contentful CMS integration that automatic
 
 <TabItem value="strapi" label="Strapi">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Strapi implementation can be found in the [Strapi integration example](https://github.com/vendurehq/examples/tree/master/examples/strapi-cms-integration). It includes advanced features like plugin-based content types, batch operations, and relationship management.
 :::
 
@@ -1382,7 +1382,7 @@ The complete implementations can be found in the working [example repositories](
 </TabItem>
 <TabItem value="Sanity" label="Sanity">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Sanity implementation can be found in the [Sanity integration example](https://github.com/vendurehq/examples/tree/master/examples/sanity-cms-integration). It includes advanced features like content type management and bulk operations.
 :::
 
@@ -1647,7 +1647,7 @@ https://github.com/vendurehq/examples/tree/master/examples/sanity-cms-integratio
 </TabItem>
 <TabItem value="payload" label="Payload">
 
-:::tip Working Example
+:::tip[Working Example]
 The complete, production-ready Payload implementation can be found in the [Payload integration example](https://github.com/vendurehq/examples/tree/master/examples/payload-cms-integration). It includes advanced features like local API communication, collection management, and relationship handling.
 :::
 

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

@@ -16,7 +16,7 @@ directory.
 :::
 
 :::note
-This guide is for adding codegen to your Vendure plugins. For a guide on adding codegen to your storefront, see the [Storefront Codegen](/guides/storefront/codegen/) guide.
+This guide is for adding codegen to your Vendure plugins. For a guide on adding codegen to your storefront, see the [Storefront Codegen](/storefront/codegen/) guide.
 :::
 
 ## Installation
@@ -153,7 +153,7 @@ export class OrganizationService {
 
 ## Codegen for Admin UI extensions
 
-:::warning Deprecated
+:::warning[Deprecated]
 This section refers to the deprecated Angular-based Admin UI. The new React-based Dashboard has built-in graphql type safety
 and does not require additional setup.
 :::

package/docs/guides/how-to/configurable-products/index.mdx

@@ -8,7 +8,7 @@ A "configurable product" is one where aspects can be configured by the customer,
 - A gift message inserted with the packaging
 - An uploaded image to be printed on a t-shirt
 
-In Vendure this is done by defining one or more [custom fields](/guides/developer-guide/custom-fields/) on the [OrderLine](/reference/typescript-api/entities/order-line/) entity.
+In Vendure this is done by defining one or more [custom fields](/developer-guide/custom-fields/) on the [OrderLine](/reference/typescript-api/entities/order-line/) entity.
 
 ## Defining custom fields
 

package/docs/guides/how-to/digital-products/index.mdx

@@ -40,7 +40,7 @@ export class DigitalProductsPlugin {}
 
 :::note
 You will need to **create a migration** after adding this custom field.
-See the [Migrations](/guides/developer-guide/migrations/) guide for more information.
+See the [Migrations](/developer-guide/migrations/) guide for more information.
 :::
 
 We will also define a custom field on the `ShippingMethod` entity to indicate that this shipping method is only available for digital products:

package/docs/guides/how-to/github-oauth-authentication/index.mdx

@@ -343,7 +343,7 @@ GitHub-authenticated customers are managed like any other Vendure [Customer](/re
 - **External ID**: GitHub username stored for future authentication
 - **Profile**: Name extracted from GitHub profile when available
 
-This means GitHub users work seamlessly with Vendure's [order management](/guides/core-concepts/orders/), [promotions](/guides/core-concepts/promotions/), and customer workflows.
+This means GitHub users work seamlessly with Vendure's [order management](/core-concepts/orders/), [promotions](/core-concepts/promotions/), and customer workflows.
 
 ## Testing the Integration
 

package/docs/guides/how-to/google-oauth-authentication/index.mdx

@@ -12,7 +12,7 @@ This is particularly valuable for **consumer-facing stores** where users prefer
 
 This guide shows you how to **add Google OAuth support** to your Vendure store using a custom [AuthenticationStrategy](/reference/typescript-api/auth/authentication-strategy/) and Google Identity Services.
 
-An **AuthenticationStrategy** in Vendure defines how users can log in to your store. Learn more about [authentication in Vendure](/guides/core-concepts/auth/).
+An **AuthenticationStrategy** in Vendure defines how users can log in to your store. Learn more about [authentication in Vendure](/core-concepts/auth/).
 
 ## Creating the Plugin
 
@@ -22,7 +22,7 @@ An **AuthenticationStrategy** in Vendure defines how users can log in to your st
 npx vendure add -p GoogleAuthPlugin
 ```
 
-This creates a basic [plugin](/guides/developer-guide/plugins/) structure with the necessary files.
+This creates a basic [plugin](/developer-guide/plugins/) structure with the necessary files.
 
 ## Installing Dependencies
 
@@ -477,7 +477,7 @@ mutation AuthenticateWithGoogle {
 - **Profile**: First and last names from Google profile, with fallbacks
 - **Security**: No password stored - authentication handled entirely by Google
 
-This means **Google users work seamlessly** with Vendure's [order management](/guides/core-concepts/orders/), [promotions](/guides/core-concepts/promotions/), and all customer workflows.
+This means **Google users work seamlessly** with Vendure's [order management](/core-concepts/orders/), [promotions](/core-concepts/promotions/), and all customer workflows.
 
 ## Testing the Integration
 

package/docs/guides/how-to/multi-vendor-marketplaces/index.mdx

@@ -20,7 +20,7 @@ All the concepts presented here have been implemented in our [example multi-vend
 
 ## Sellers, Channels & Roles
 
-The core of Vendure's multi-vendor support is Channels. Read the [Channels guide](/guides/core-concepts/channels/) to get a more detailed understanding of how they work.
+The core of Vendure's multi-vendor support is Channels. Read the [Channels guide](/core-concepts/channels/) to get a more detailed understanding of how they work.
 
 Each Channel is assigned to a [Seller](/reference/typescript-api/entities/seller/), which is another term for the vendor who is selling things in our marketplace.
 
@@ -60,7 +60,7 @@ Bob can now log in to the Dashboard using the provided credentials and begin cre
 
 In some marketplaces, the same product may be sold by multiple sellers. When this is the case, the product and its variants
 will be assigned not only to the default channel, but to multiple other channels as well - see the 
-[Channels, Currencies & Prices section](/guides/core-concepts/channels/#channels-currencies--prices) for a visual explanation of how this works.
+[Channels, Currencies & Prices section](/core-concepts/channels/#channels-currencies--prices) for a visual explanation of how this works.
 
 This means that there will be multiple ProductVariantPrice entities per variant, one for each channel. 
  

package/docs/guides/how-to/paginated-list/index.mdx

@@ -7,7 +7,7 @@ to implement your own paginated list queries.
 
 ## API definition
 
-Let's start with defining the GraphQL schema for our query. In this example, we'll image that we have defined a [custom entity](/guides/developer-guide/database-entity/) to
+Let's start with defining the GraphQL schema for our query. In this example, we'll image that we have defined a [custom entity](/developer-guide/database-entity/) to
 represent a `ProductReview`. We want to be able to query a list of reviews in the Admin API. Here's how the schema definition
 would look:
 

package/docs/guides/how-to/publish-plugin/index.mdx

@@ -2,7 +2,7 @@
 title: "Publishing a Plugin"
 ---
 
-Vendure's [plugin-based architecture](/guides/developer-guide/plugins/) means you'll be writing a lot of plugins.
+Vendure's [plugin-based architecture](/developer-guide/plugins/) means you'll be writing a lot of plugins.
 Some of those plugins may be useful to others, and you may want to share them with the community.
 
 We have created [Vendure Hub](https://vendure.io/hub) as a central listing for high-quality Vendure plugins.
@@ -44,7 +44,7 @@ a must. The same goes for any of the transitive dependencies of Vendure core suc
 that these dependencies will be available in the Vendure project that uses your plugin.
 
 As for version compatibility, you should use the
-[compatibility property](/guides/developer-guide/plugins/#step-7-specify-compatibility) in your plugin definition to ensure that the Vendure project
+[compatibility property](/developer-guide/plugins/#step-7-specify-compatibility) in your plugin definition to ensure that the Vendure project
 is using a compatible version of Vendure.
 
 ### License
@@ -380,7 +380,7 @@ export class LoyaltyPointsTransactionEvent extends VendureEvent {
 Testing is an important part of ensuring the quality of your plugin, as well as preventing regressions when you make
 changes.
 
-For plugins of any complexity, you should aim to have a suite of end-to-end tests as covered in the [testing docs](/guides/developer-guide/testing/).
+For plugins of any complexity, you should aim to have a suite of end-to-end tests as covered in the [testing docs](/developer-guide/testing/).
 
 In future we may use the test results to help determine the quality of a plugin.
 

package/docs/guides/how-to/s3-asset-storage/index.mdx

@@ -14,7 +14,7 @@ Refer to the complete working code for full implementation details.
 ## Prerequisites
 
 - Node.js 20+ with npm package manager
-- An existing Vendure project created with the [Vendure create command](/guides/getting-started/installation/)
+- An existing Vendure project created with the [Vendure create command](/getting-started/installation/)
 - An account with one of the supported S3-compatible storage providers
 
 ## S3-Compatible Storage Provider Setup

package/docs/guides/storefront/active-order/index.mdx

@@ -100,7 +100,7 @@ query GetActiveOrder {
 
 ## Add an item
 
-To add an item to the active order, we use the [`addItemToOrder` mutation](/reference/graphql-api/shop/mutations/#additemtoorder), as we have seen in the [Product Detail Page guide](/guides/storefront/product-detail/).
+To add an item to the active order, we use the [`addItemToOrder` mutation](/reference/graphql-api/shop/mutations/#additemtoorder), as we have seen in the [Product Detail Page guide](/storefront/product-detail/).
 
 ```graphql
 mutation AddItemToOrder($productVariantId: ID!, $quantity: Int!) {
@@ -122,7 +122,7 @@ mutation AddItemToOrder($productVariantId: ID!, $quantity: Int!) {
 
 :::info
 If you have defined any custom fields on the `OrderLine` entity, you will be able to pass them as a `customFields` argument to the `addItemToOrder` mutation.
-See the [Configurable Products guide](/guides/how-to/configurable-products/) for more information.
+See the [Configurable Products guide](/how-to/configurable-products/) for more information.
 :::
 
 ## Remove an item
@@ -160,12 +160,12 @@ mutation AdjustOrderLine($orderLineId: ID!, $quantity: Int!) {
 
 :::info
 If you have defined any custom fields on the `OrderLine` entity, you will be able to update their values by passing a `customFields` argument to the `adjustOrderLine` mutation.
-See the [Configurable Products guide](/guides/how-to/configurable-products/) for more information.
+See the [Configurable Products guide](/how-to/configurable-products/) for more information.
 :::
 
 ## Applying a coupon code
 
-If you have defined any [Promotions](/guides/core-concepts/promotions/) which use coupon codes, you can apply the a coupon code to the active order
+If you have defined any [Promotions](/core-concepts/promotions/) which use coupon codes, you can apply the a coupon code to the active order
 using the [`applyCouponCode` mutation](/reference/graphql-api/shop/mutations/#applycouponcode).
 
 ```graphql

package/docs/guides/storefront/checkout-flow/index.mdx

@@ -4,12 +4,12 @@ title: "Checkout Flow"
 
 Once the customer has added the desired products to the active order, it's time to check out.
 
-This guide assumes that you are using the [default OrderProcess](/guides/core-concepts/orders/#the-order-process), so
+This guide assumes that you are using the [default OrderProcess](/core-concepts/orders/#the-order-process), so
 if you have defined a custom process, some of these steps may be slightly different.
 
 :::note
 In this guide, we will assume that an `ActiveOrder` fragment has been defined, as detailed in the
-[Managing the Active Order guide](/guides/storefront/active-order/#define-an-order-fragment), but for the purposes of
+[Managing the Active Order guide](/storefront/active-order/#define-an-order-fragment), but for the purposes of
 checking out the fragment should also include `customer` `shippingAddress` and `billingAddress` fields.
 :::
 
@@ -388,7 +388,7 @@ Our [`MolliePlugin` docs](/reference/core-plugins/payments-plugin/mollie-plugin/
 
 ### Other payment providers
 
-For more information on how to integrate with a payment provider, see the [Payment](/guides/core-concepts/payment/) guide.
+For more information on how to integrate with a payment provider, see the [Payment](/core-concepts/payment/) guide.
 
 ## Display confirmation
 

package/docs/guides/storefront/codegen/index.mdx

@@ -9,7 +9,7 @@ write any types for your API calls.
 To do this, we will use [Graphql Code Generator](https://the-guild.dev/graphql/codegen).
 
 :::note
-This guide is for adding codegen to your storefront. For a guide on adding codegen to your backend Vendure plugins or UI extensions, see the [Plugin Codegen](/guides/how-to/codegen/) guide.
+This guide is for adding codegen to your storefront. For a guide on adding codegen to your backend Vendure plugins or UI extensions, see the [Plugin Codegen](/how-to/codegen/) guide.
 :::
 
 ## Installation

package/docs/guides/storefront/connect-api/index.mdx

@@ -113,7 +113,7 @@ length of time that a session will stay valid since the last API call.
 
 ## Specifying a channel
 
-If your project has multiple [channels](/guides/core-concepts/channels/), you can specify the active channel by setting
+If your project has multiple [channels](/core-concepts/channels/), you can specify the active channel by setting
 the `vendure-token` header on each request to match the `channelToken` for the desired channel.
 
 Let's say you have a channel with the token `uk-channel` and you want to make a request to the Shop API to get the
@@ -161,7 +161,7 @@ POST http://localhost:3000/shop-api?languageCode=de
 If you are building your storefront with TypeScript, we highly recommend you set up code generation to ensure
 that the responses from your queries & mutation are always correctly typed according the fields you request.
 
-See the [GraphQL Code Generation guide](/guides/storefront/codegen/) for more information.
+See the [GraphQL Code Generation guide](/storefront/codegen/) for more information.
 
 ## Examples
 

package/docs/guides/storefront/customer-accounts/index.mdx

@@ -137,7 +137,7 @@ mutation LogOut {
 The `login` mutation, as well as the following mutations related to registration & password recovery only
 apply when using the built-in [`NativeAuthenticationStrategy`](/reference/typescript-api/auth/native-authentication-strategy/).
 
-If you are using alternative authentication strategies in your storefront, you would use the [`authenticate` mutation](/reference/graphql-api/shop/mutations/#authenticate) as covered in the [External Authentication guide](/guides/core-concepts/auth/#external-authentication).
+If you are using alternative authentication strategies in your storefront, you would use the [`authenticate` mutation](/reference/graphql-api/shop/mutations/#authenticate) as covered in the [External Authentication guide](/core-concepts/auth/#external-authentication).
 :::
 
 ## Registering a customer account

package/docs/guides/storefront/listing-products/index.mdx

@@ -13,7 +13,7 @@ be used to fetch a list of products, but they need to perform much more complex
 
 ## Listing products in a collection
 
-Following on from the [navigation example](/guides/storefront/navigation-menu/), let's assume that a customer has
+Following on from the [navigation example](/storefront/navigation-menu/), let's assume that a customer has
 clicked on a collection item from the menu, and we want to display the products in that collection.
 
 Typically, we will know the `slug` of the selected collection, so we can use the `collection` query to fetch the

package/docs/guides/storefront/navigation-menu/index.mdx

@@ -4,7 +4,7 @@ title: "Navigation Menu"
 
 A navigation menu allows your customers to navigate your store and find the products they are looking for.
 
-Typically, navigation is based on a hierarchy of [collections](/guides/core-concepts/collections/). We can get the top-level
+Typically, navigation is based on a hierarchy of [collections](/core-concepts/collections/). We can get the top-level
 collections using the `collections` query with the `topLevelOnly` filter:
 
 

package/docs/guides/storefront/order-workflow/index.mdx

@@ -10,7 +10,7 @@ An Order is a collection of one or more ProductVariants which can be purchased b
 Every Order has a `state` property of type [`OrderState`](/reference/typescript-api/orders/order-process/#orderstate). The following diagram shows the default states and how an Order transitions from one to the next.
 
 :::note
-Note that this default workflow can be modified to better fit your business processes. See the [Customizing the Order Process guide](/guides/core-concepts/orders/#custom-order-processes).
+Note that this default workflow can be modified to better fit your business processes. See the [Customizing the Order Process guide](/core-concepts/orders/#custom-order-processes).
 :::
 
 ![./order_state_diagram.png](./order_state_diagram.png)
@@ -25,7 +25,7 @@ Here is a simplified diagram illustrating this relationship:
 
 ## Shop client order workflow
 
-The [GraphQL Shop API Guide](/guides/storefront/active-order) lists the GraphQL operations you will need to implement this workflow in your storefront client application.
+The [GraphQL Shop API Guide](/storefront/active-order) lists the GraphQL operations you will need to implement this workflow in your storefront client application.
 
 In this section, we'll cover some examples of how these operations would look in your storefront.
 

package/docs/guides/storefront/product-detail/index.mdx

@@ -145,11 +145,11 @@ This single query provides all the data we need to display our PDP.
 
 ## Formatting prices
 
-As explained in the [Money & Currency guide](/guides/core-concepts/money/), the prices are returned as integers in the
+As explained in the [Money & Currency guide](/core-concepts/money/), the prices are returned as integers in the
 smallest unit of the currency (e.g. cents for USD). Therefore, when we display the price, we need to divide by 100 and
 format it according to the currency's formatting rules.
 
-In the demo at the end of this guide, we'll use the [`formatCurrency` function](/guides/core-concepts/money/#displaying-monetary-values)
+In the demo at the end of this guide, we'll use the [`formatCurrency` function](/core-concepts/money/#displaying-monetary-values)
 which makes use of the browser's `Intl` API to format the price according to the user's locale.
 
 ## Displaying images
@@ -274,9 +274,9 @@ fragment UpdatedOrder on Order {
 
 There are some important things to note about this mutation:
 
-- Because the `addItemToOrder` mutation returns a union type, we need to use a [fragment](/guides/getting-started/graphql-intro/#fragments) to specify the fields we want to return.
+- Because the `addItemToOrder` mutation returns a union type, we need to use a [fragment](/getting-started/graphql-intro/#fragments) to specify the fields we want to return.
 In this case we have defined a fragment called `UpdatedOrder` which contains the fields we are interested in.
-- If any [expected errors](/guides/developer-guide/error-handling/) occur, the mutation will return an `ErrorResult` object. We'll be able to
+- If any [expected errors](/developer-guide/error-handling/) occur, the mutation will return an `ErrorResult` object. We'll be able to
 see the `errorCode` and `message` fields in the response, so that we can display a meaningful error message to the user.
 - In the special case of the `InsufficientStockError`, in addition to the `errorCode` and `message` fields, we also get the `quantityAvailable` field
 which tells us how many of the requested quantity are available (and have been added to the order). This is useful information to display to the user.

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

@@ -8,7 +8,7 @@ Defines extensions to the Admin UI application by specifying additional
 Angular [NgModules](https://angular.io/guide/ngmodules) which are compiled
 into the application.
 
-See [Extending the Admin UI](/guides/extending-the-admin-ui/getting-started/) for
+See [Extending the Admin UI](/extending-the-admin-ui/getting-started/) for
 detailed instructions.
 
 ```ts title="Signature"

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

@@ -4,8 +4,8 @@ generated: true
 ---
 <GenerationInfo sourceFile="packages/admin-ui-plugin/src/plugin.ts" sourceLine="147" packageName="@vendure/admin-ui-plugin" />
 
-:::warning Deprecated
-From Vendure v3.5.0, the Angular-based Admin UI has been replaced by the new [React Admin Dashboard](/guides/extending-the-dashboard/getting-started/).
+:::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.
 :::

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

@@ -14,7 +14,7 @@ GraphQL extensions needed for the order metrics on the dashboard index page.
 ## Usage
 
 First you need to set up compilation of the Dashboard, using the Vite configuration
-described in the [Dashboard Getting Started Guide](/guides/extending-the-dashboard/getting-started/)
+described in the [Dashboard Getting Started Guide](/extending-the-dashboard/getting-started/)
 
 ## Development vs Production
 

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

@@ -15,7 +15,7 @@ npm install @vendure/telemetry-plugin
 
 :::info
 For a complete guide to setting up and working with Open Telemetry, see
-the [Implementing Open Telemetry guide](/guides/how-to/telemetry/).
+the [Implementing Open Telemetry guide](/how-to/telemetry/).
 :::
 
 ## Configuration

package/docs/reference/typescript-api/auth/authentication-strategy.mdx

@@ -7,7 +7,7 @@ generated: true
 An AuthenticationStrategy defines how a User (which can be a Customer in the Shop API or
 and Administrator in the Admin API) may be authenticated.
 
-Real-world examples can be found in the [Authentication guide](/guides/core-concepts/auth/).
+Real-world examples can be found in the [Authentication guide](/core-concepts/auth/).
 
 :::info
 

package/docs/reference/typescript-api/common/admin-ui/admin-ui-config.mdx

@@ -128,7 +128,7 @@ A url of a custom image to be used on the login screen, to override the images p
 
 Allows you to provide default reasons for a refund or cancellation. This will be used in the
 refund/cancel dialog. The values can be literal strings (e.g. "Not in stock") or translation
-tokens (see [Adding Admin UI Translations](/guides/extending-the-admin-ui/adding-ui-translations/)).
+tokens (see [Adding Admin UI Translations](/extending-the-admin-ui/adding-ui-translations/)).
 
 
 </div>

package/docs/reference/typescript-api/custom-fields/custom-field-type.mdx

@@ -20,7 +20,7 @@ datetime     | datetime (m,s), timestamp (p)         | DateTime
 struct       | json (m), jsonb (p), text (s)         | JSON
 relation     | many-to-one / many-to-many relation   | As specified in config
 
-Additionally, the CustomFieldType also dictates which [configuration options](/guides/developer-guide/custom-fields/#custom-field-config-properties)
+Additionally, the CustomFieldType also dictates which [configuration options](/developer-guide/custom-fields/#custom-field-config-properties)
 are available for that custom field.
 
 ```ts title="Signature"

package/docs/reference/typescript-api/import-export/import-parser.mdx

@@ -19,7 +19,7 @@ class ImportParser {
 
 <MemberInfo kind="method" type={`(input: string | Stream, mainLanguage: <a href='/reference/typescript-api/common/language-code#languagecode'>LanguageCode</a> = this.configService.defaultLanguageCode) => Promise<<a href='/reference/typescript-api/import-export/import-parser#parseresult'>ParseResult</a><<a href='/reference/typescript-api/import-export/import-parser#parsedproductwithvariants'>ParsedProductWithVariants</a>>>`}   />
 
-Parses the contents of the [product import CSV file](/guides/developer-guide/importing-data/#product-import-format) and
+Parses the contents of the [product import CSV file](/developer-guide/importing-data/#product-import-format) and
 returns a data structure which can then be used to populate Vendure using the <DocsLink href="/reference/typescript-api/import-export/fast-importer-service#fastimporterservice">FastImporterService</DocsLink>.
 
 

package/docs/reference/typescript-api/import-export/importer.mdx

@@ -25,7 +25,7 @@ class Importer {
 
 <MemberInfo kind="method" type={`(input: string | Stream, ctxOrLanguageCode: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a> | <a href='/reference/typescript-api/common/language-code#languagecode'>LanguageCode</a>, reportProgress: boolean = false) => Observable<ImportProgress>`}   />
 
-Parses the contents of the [product import CSV file](/guides/developer-guide/importing-data/#product-import-format) and imports
+Parses the contents of the [product import CSV file](/developer-guide/importing-data/#product-import-format) and imports
 the resulting Product & ProductVariants, as well as any associated Assets, Facets & FacetValues.
 
 The `ctxOrLanguageCode` argument is used to specify the languageCode to be used when creating the Products.

package/docs/reference/typescript-api/import-export/populate.mdx

@@ -6,7 +6,7 @@ generated: true
 
 Populates the Vendure server with some initial data and (optionally) product data from
 a supplied CSV file. The format of the CSV file is described in the section
-[Importing Product Data](/guides/developer-guide/importing-data/).
+[Importing Product Data](/developer-guide/importing-data/).
 
 If the `channelOrToken` argument is provided, all ChannelAware entities (Products, ProductVariants,
 Assets, ShippingMethods, PaymentMethods etc.) will be assigned to the specified Channel.

package/docs/reference/typescript-api/job-queue/default-job-queue-plugin.mdx

@@ -5,7 +5,7 @@ generated: true
 <GenerationInfo sourceFile="packages/core/src/plugin/default-job-queue-plugin/default-job-queue-plugin.ts" sourceLine="127" packageName="@vendure/core" />
 
 A plugin which configures Vendure to use the SQL database to persist the JobQueue jobs using the <DocsLink href="/reference/typescript-api/job-queue/sql-job-queue-strategy#sqljobqueuestrategy">SqlJobQueueStrategy</DocsLink>. If you add this
-plugin to an existing Vendure installation, you'll need to run a [database migration](/guides/developer-guide/migrations), since this
+plugin to an existing Vendure installation, you'll need to run a [database migration](/developer-guide/migrations), since this
 plugin will add a new "job_record" table to the database.
 
 *Example*

package/docs/reference/typescript-api/orders/order-item-price-calculation-strategy.mdx

@@ -49,7 +49,7 @@ A custom OrderItemPriceCalculationStrategy can be used to implement things like:
 * A gift-wrapping service, where a boolean custom field is defined on the OrderLine. If `true`,
   a gift-wrapping surcharge would be added to the price.
 * A product-configurator where e.g. various finishes, colors, and materials can be selected and stored
-  as OrderLine custom fields (see [the Custom Fields guide](/guides/developer-guide/custom-fields/).
+  as OrderLine custom fields (see [the Custom Fields guide](/developer-guide/custom-fields/).
 * Price lists or bulk pricing, where different price bands are stored e.g. in a customField on the ProductVariant, and this
   is used to calculate the price based on the current quantity.
 

package/docs/reference/typescript-api/services/asset-service.mdx

@@ -71,7 +71,7 @@ Create an Asset based on a file uploaded via the GraphQL API. The file should be
 using the [GraphQL multipart request specification](https://github.com/jaydenseric/graphql-multipart-request-spec),
 e.g. using the [apollo-upload-client](https://github.com/jaydenseric/apollo-upload-client) npm package.
 
-See the [Uploading Files docs](/guides/developer-guide/uploading-files) for an example of usage.
+See the [Uploading Files docs](/developer-guide/uploading-files) for an example of usage.
 ### update
 
 <MemberInfo kind="method" type={`(ctx: <a href='/reference/typescript-api/request/request-context#requestcontext'>RequestContext</a>, input: UpdateAssetInput) => Promise<<a href='/reference/typescript-api/entities/asset#asset'>Asset</a>>`}   />

package/docs/reference/typescript-api/services/history-service.mdx

@@ -98,7 +98,7 @@ export class VerificationService {
 ```
 :::info
 It is also possible to define a UI component to display custom history entry types. See the
-[Custom History Timeline Components guide](/guides/extending-the-admin-ui/custom-timeline-components/).
+[Custom History Timeline Components guide](/extending-the-admin-ui/custom-timeline-components/).
 :::
 
 ```ts title="Signature"

package/docs/reference/typescript-api/worker/bootstrap-worker.mdx

@@ -8,7 +8,7 @@ Bootstraps a Vendure worker. Resolves to a <DocsLink href="/reference/typescript
 NestJs [standalone application](https://docs.nestjs.com/standalone-applications) as well as convenience
 methods for starting the job queue and health check server.
 
-Read more about the [Vendure Worker](/guides/developer-guide/worker-job-queue/).
+Read more about the [Vendure Worker](/developer-guide/worker-job-queue/).
 
 *Example*
 

package/docs/user-guide/settings/taxes.mdx

@@ -27,4 +27,4 @@ Tax rates set the rate of tax for a given **tax category** destined for a partic
 
 ## Tax Compliance
 
-Please note that tax compliance is a complex topic that varies significantly between countries. Vendure does not (and cannot) offer a complete out-of-the-box tax solution which is guaranteed to be compliant with your use-case. What we strive to do is to provide a very flexible set of tools that your developers can use to tailor tax calculations exactly to your needs. These are covered in the [Developer's guide to taxes](/guides/core-concepts/taxes/). 
+Please note that tax compliance is a complex topic that varies significantly between countries. Vendure does not (and cannot) offer a complete out-of-the-box tax solution which is guaranteed to be compliant with your use-case. What we strive to do is to provide a very flexible set of tools that your developers can use to tailor tax calculations exactly to your needs. These are covered in the [Developer's guide to taxes](/core-concepts/taxes/).