@vendure/docs 0.0.0-202601161603 → 0.0.0-202601161637

package/docs/guides/core-concepts/collections/index.mdx

@@ -2,9 +2,6 @@
 title: 'Collections'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 [`Collections`](/reference/typescript-api/entities/collection/) are used to categorize and organize your catalog. A collection
 contains multiple product variants, and a product variant can belong to multiple collections. Collections can be nested to
 create a hierarchy of categories, which is typically used to create a menu structure in the storefront.

package/docs/guides/core-concepts/orders/index.mdx

@@ -2,10 +2,6 @@
 title: 'Orders'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
-
 In Vendure, the [`Order`](/reference/typescript-api/entities/order/) entity represents the entire lifecycle of an order, from the moment a customer adds an item to their cart, through to the point where the order is completed and the customer has received their goods.
 
 An [`Order`](/reference/typescript-api/entities/order/) is composed of one or more [`OrderLines`](/reference/typescript-api/entities/order-line/).

package/docs/guides/core-concepts/payment/index.mdx

@@ -2,9 +2,6 @@
 title: 'Payment'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Vendure can support many kinds of payment workflows, such as authorizing and capturing payment in a single step upon checkout or authorizing on checkout and then capturing on fulfillment.
 
 :::info

package/docs/guides/core-concepts/shipping/index.mdx

@@ -2,9 +2,6 @@
 title: "Shipping & Fulfillment"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Shipping in Vendure is handled by [ShippingMethods](/reference/typescript-api/entities/shipping-method/). 
 A ShippingMethod is composed of a **checker** and a **calculator**. 
 

package/docs/guides/core-concepts/stock-control/index.mdx

@@ -2,9 +2,6 @@
 title: "Stock Control"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Vendure includes features to help manage your stock levels, stock allocations and back orders. The basic purpose is to help you keep track of how many of a given ProductVariant you have available to sell.
 
 Stock control is enabled globally via the Global Settings:

package/docs/guides/deployment/deploy-to-northflank/index.mdx

@@ -5,9 +5,6 @@ images:
   - "/docs/deployment/deploy-to-northflank/deploy-to-northflank.webp"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 ![./deploy-to-northflank.webp](./deploy-to-northflank.webp)
 
 [Northflank](https://northflank.com) is a comprehensive developer platform to build and scale your apps. It has an outstanding developer experience and has a free tier for small projects, and is well-suited for deploying and scaling Vendure applications.

package/docs/guides/deployment/getting-data-into-production.mdx

@@ -4,8 +4,6 @@ showtoc: true
 weight: 4
 ---
 
-# Getting data into production
-
 Once you have set up your production deployment, you'll need some way to get your products and other data into the system.
 
 The main tasks will be:

package/docs/guides/deployment/horizontal-scaling.mdx

@@ -4,8 +4,6 @@ showtoc: true
 weight: 2
 ---
 
-# Horizontal scaling
-
 "Horizontal scaling" refers to increasing the performance capacity of your application by running multiple instances.
 
 This type of scaling has two main advantages:

package/docs/guides/deployment/production-configuration/index.mdx

@@ -4,8 +4,6 @@ showtoc: true
 weight: 0
 ---
 
-# Production configuration
-
 This is a guide to the recommended configuration for a production Vendure application.
 
 ## Environment variables

package/docs/guides/deployment/using-docker.mdx

@@ -4,8 +4,6 @@ showtoc: true
 weight: 3
 ---
 
-# Using Docker
-
 [Docker](https://docs.docker.com/) is a technology which allows you to run your Vendure application inside a [container](https://docs.docker.com/get-started/#what-is-a-container).
 The default installation with `@vendure/create` includes a sample Dockerfile:
 

package/docs/guides/developer-guide/cli/index.mdx

@@ -2,9 +2,6 @@
 title: 'CLI'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The Vendure CLI is a command-line tool for boosting your productivity as a developer by automating common tasks
 such as creating new plugins, entities, API extensions and more.
 

package/docs/guides/developer-guide/configuration/index.mdx

@@ -3,8 +3,6 @@ title: "Configuration"
 sidebar_position: 3
 ---
 
-# Configuration
-
 Every aspect of the Vendure server is configured via a single, central [`VendureConfig`](/reference/typescript-api/configuration/vendure-config/) object. This object is passed into the [`bootstrap`](/reference/typescript-api/common/bootstrap/) and [`bootstrapWorker`](/reference/typescript-api/worker/bootstrap-worker/) functions to start up the Vendure server and worker respectively.
 
 The `VendureConfig` object is organised into sections, grouping related settings together. For example, [`VendureConfig.apiOptions`](/reference/typescript-api/configuration/api-options/) contains all the config for the GraphQL APIs, whereas [`VendureConfig.authOptions`](/reference/typescript-api/auth/auth-options/) deals with authentication.

package/docs/guides/developer-guide/custom-fields/index.mdx

@@ -3,10 +3,6 @@ title: 'Custom Fields'
 sidebar_position: 3
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import CustomFieldProperty from '@site/src/components/CustomFieldProperty';
-
 Custom fields allow you to add your own custom data properties to almost every Vendure entity. The entities which may have custom fields defined are listed in the [CustomFields interface documentation](/reference/typescript-api/custom-fields/).
 
 Some use-cases for custom fields include:

package/docs/guides/developer-guide/db-subscribers/index.mdx

@@ -2,8 +2,6 @@
 title: "Database subscribers"
 ---
 
-# Defining database subscribers
-
 TypeORM allows us to define [subscribers](https://typeorm.io/listeners-and-subscribers#what-is-a-subscriber). With a subscriber, we can listen to specific entity events and take actions based on inserts, updates, deletions and more.
 
 If you need lower-level access to database changes that you get with the [Vendure EventBus system](/reference/typescript-api/events/event-bus/), TypeORM subscribers can be useful.

package/docs/guides/developer-guide/error-handling/index.mdx

@@ -3,10 +3,6 @@ title: "Error Handling"
 showtoc: true
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import Stackblitz from '@site/src/components/Stackblitz';
-
 Errors in Vendure can be divided into two categories:
 
 * Unexpected errors

package/docs/guides/developer-guide/logging/index.mdx

@@ -3,8 +3,6 @@ title: "Logging"
 showtoc: true
 ---
 
-# Logging
-
 Logging allows you to see what is happening inside the Vendure server. It is useful for debugging and for monitoring the health of the server in production.
 
 In Vendure, logging is configured using the `logger` property of the [VendureConfig](/reference/typescript-api/configuration/vendure-config/#logger) object. The logger must implement the [VendureLogger](/reference/typescript-api/logger/vendure-logger) interface.

package/docs/guides/developer-guide/migrating-from-v1/breaking-api-changes.mdx

@@ -3,8 +3,6 @@ title: "Breaking API Changes"
 sidebar_position: 3
 ---
 
-# Breaking API Changes
-
 ## Breaks from updated dependencies
 
 ### TypeScript

package/docs/guides/developer-guide/migrating-from-v1/database-migration.mdx

@@ -3,8 +3,6 @@ title: "Database Migration"
 sidebar_position: 2
 ---
 
-# v2 Database Migration
-
 Vendure v2 introduces a number of breaking changes to the database schema, some of which require quite complex migrations in order to preserve existing data. To make this process as smooth as possible, we have created a migration tool which will handle the hard parts for you!
 
 :::warning

package/docs/guides/developer-guide/migrating-from-v1/index.mdx

@@ -4,8 +4,6 @@ weight: 2
 sidebar_position: 1
 ---
 
-# Migrating from Vendure 1 to 2
-
 This section contains guides for migrating from Vendure v1 to v2.
 
 There are a number of breaking changes between the two versions, which are due to a few major factors:

package/docs/guides/developer-guide/migrating-from-v1/storefront-migration.mdx

@@ -3,8 +3,6 @@ title: "Storefront Migration"
 sidebar_position: 4
 ---
 
-# Storefront migration
-
 There are relatively few breaking changes that will affect the storefront.
 
 - The `setOrderShippingMethod` mutation now takes an array of shipping method IDs rather than just a single one. This is so we can support multiple shipping methods per Order.

package/docs/guides/developer-guide/migrations/index.mdx

@@ -2,9 +2,6 @@
 title: "Migrations"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Database migrations are needed whenever the database schema changes. This can be caused by:
 
 * changes to the [custom fields](/guides/developer-guide/custom-fields/) configuration

package/docs/guides/developer-guide/plugins/index.mdx

@@ -3,9 +3,6 @@ title: 'Plugins'
 sidebar_position: 6
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The heart of Vendure is its plugin system. Plugins not only allow you to instantly add new functionality to your
 Vendure server via third-part npm packages, they are also the means by which you build out the custom business
 logic of your application.

package/docs/guides/developer-guide/settings-store/index.mdx

@@ -3,13 +3,6 @@ title: 'Settings Store'
 showtoc: true
 ---
 
-
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
-# Settings Store
-
 The Settings Store is a flexible system for storing configuration data with support for scoping, permissions,
 and validation. It allows plugins and the core system to store and retrieve arbitrary JSON data with
 fine-grained control over access and isolation.

package/docs/guides/developer-guide/stand-alone-scripts/index.mdx

@@ -2,8 +2,6 @@
 title: "Stand-alone CLI Scripts"
 ---
 
-# Stand-alone CLI Scripts
-
 It is possible to create stand-alone scripts that can be run from the command-line by using the [bootstrapWorker function](/reference/typescript-api/worker/bootstrap-worker/). This can be useful for a variety of use-cases such as running cron jobs or importing data.
 
 ## Minimal example

package/docs/guides/developer-guide/testing/index.mdx

@@ -3,8 +3,6 @@ title: "Testing"
 showtoc: true
 ---
 
-# Testing
-
 Vendure plugins allow you to extend all aspects of the standard Vendure server. When a plugin gets somewhat complex (defining new entities, extending the GraphQL schema, implementing custom resolvers), you may wish to create automated tests to ensure your plugin is correct.
 
 The `@vendure/testing` package gives you some simple but powerful tooling for creating end-to-end tests for your custom Vendure code.

package/docs/guides/developer-guide/the-api-layer/index.mdx

@@ -3,9 +3,6 @@ title: 'The API Layer'
 sidebar_position: 1
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Vendure is a headless platform, which means that all functionality is exposed via GraphQL APIs. The API can be thought of
 as a number of layers through which a request will pass, each of which is responsible for a different aspect of the
 request/response lifecycle.

package/docs/guides/developer-guide/updating/index.mdx

@@ -3,8 +3,6 @@ title: "Updating Vendure"
 showtoc: true
 ---
 
-# Updating Vendure
-
 This guide provides guidance for updating the Vendure core framework to a newer version.
 
 ## How to update

package/docs/guides/developer-guide/uploading-files/index.mdx

@@ -3,8 +3,6 @@ title: "Uploading Files"
 showtoc: true
 ---
 
-# Uploading Files 
-
 Vendure handles file uploads with the [GraphQL multipart request specification](https://github.com/jaydenseric/graphql-multipart-request-spec). Internally, we use the [graphql-upload package](https://github.com/jaydenseric/graphql-upload). Once uploaded, a file is known as an [Asset](/guides/core-concepts/images-assets/). Assets are typically used for images, but can represent any kind of binary data such as PDF files or videos.
 
 ## Upload clients

package/docs/guides/extending-the-admin-ui/add-actions-to-pages/index.mdx

@@ -3,9 +3,6 @@ title: 'Page ActionBar Buttons'
 weight: 5
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The `ActionBar` is the horizontal area at the top of each list or detail page, which contains the main buttons for that page.
 This guide explains how to add new buttons and dropdown menu items to the ActionBar.
 

package/docs/guides/extending-the-admin-ui/creating-detail-views/index.mdx

@@ -2,8 +2,6 @@
 title: 'Creating Detail Views'
 ---
 
-# Creating Detail Views
-
 The two most common type of components you'll be creating in your UI extensions are list components and detail components.
 
 In Vendure, we have standardized the way you write these components so that your ui extensions can be made to fit seamlessly into the rest of the app.

package/docs/guides/extending-the-admin-ui/custom-data-table-components/index.mdx

@@ -3,9 +3,6 @@ title: 'Custom DataTable Components'
 weight: 6
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The Admin UI list views are powered by a data table component which features sorting, advanced filtering, pagination and more. It will also give you the option of displaying any configured [custom fields](/guides/developer-guide/custom-fields/) for the entity in question.
 
 With Admin UI extensions, you can specify custom components to use in rendering any column of any data table - both custom fields _and_ built-in fields, using either Angular or React components.

package/docs/guides/extending-the-admin-ui/custom-detail-components/index.mdx

@@ -2,9 +2,6 @@
 title: 'Custom Detail Components'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Detail views can be extended with custom Angular or React components using the [`registerCustomDetailComponent`](/reference/admin-ui-api/custom-detail-components/register-custom-detail-component/) and [`registerReactCustomDetailComponent`](/reference/admin-ui-api/react-extensions/register-react-custom-detail-component) functions.
 
 Any components registered in this way will appear below the main detail form.

package/docs/guides/extending-the-admin-ui/custom-form-inputs/index.mdx

@@ -2,9 +2,6 @@
 title: 'Custom Form Inputs'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 You can define custom Angular or React components which can be used to render [Custom Fields](/guides/developer-guide/custom-fields/) you have defined on your entities as well as [configurable args](/reference/typescript-api/configurable-operation-def/config-args/) used by custom [Configurable Operations](/guides/developer-guide/strategies-configurable-operations/#configurable-operations).
 
 ## For Custom Fields

package/docs/guides/extending-the-admin-ui/defining-routes/index.mdx

@@ -2,9 +2,6 @@
 title: 'Defining routes'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Routes allow you to mount entirely custom components at a given URL in the Admin UI. New routes will appear in this area of the Admin UI:
 
 ![Route area](./route-area.webp)

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

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

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

@@ -2,9 +2,6 @@
 title: "UI Component Library"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The Admin UI is built on a customized version of the [Clarity Design System](https://clarity.design/documentation/get-started). This means that if you are writing Angular-based UI extensions, you can use the same components that are used in the rest of the Admin UI. If you are using React, we are gradually exporting the most-used components for use with React.
 
 ## Buttons

package/docs/guides/extending-the-dashboard/creating-pages/detail-pages.mdx

@@ -2,9 +2,6 @@
 title: 'Creating Detail Pages'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 ## Setup
 
 :::info

package/docs/guides/extending-the-dashboard/creating-pages/index.mdx

@@ -2,9 +2,6 @@
 title: 'Creating Pages'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 ## Page Structure
 
 All pages in the Dashboard follow this structure:

package/docs/guides/extending-the-dashboard/creating-pages/list-pages.mdx

@@ -2,9 +2,6 @@
 title: 'Creating List Pages'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 ## Setup
 
 :::info

package/docs/guides/extending-the-dashboard/creating-pages/tabbed-pages.mdx

@@ -2,9 +2,6 @@
 title: 'Creating Tabbed Pages'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 ## Setup
 
 :::info

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

@@ -2,10 +2,6 @@
 title: 'Form Component Examples'
 ---
 
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 ## Email Input with Validation
 
 This example uses the `react-hook-form` validation state in order to display an icon indicating

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

@@ -2,9 +2,6 @@
 title: 'Extending the Dashboard'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The custom functionality you create in your Vendure plugins often needs to be exposed via the Dashboard so that
 administrators can interact with it.
 

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

@@ -2,9 +2,6 @@
 title: 'Getting Started'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 :::info
 From Vendure v3.5.0, the `@vendure/dashboard` package and configuration comes as standard with new projects that are started with
 the `npx @vendure/create` command.

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

@@ -3,8 +3,6 @@ title: Migrating from Admin UI
 sidebar_position: 1
 ---
 
-# Migrating from Admin UI
-
 If you have existing extensions to the legacy Angular-based Admin UI, you will want to migrate to the new Dashboard to enjoy
 an improved developer experience, many more customization options, and ongoing support from the Vendure team.
 

package/docs/guides/getting-started/graphql-intro/index.mdx

@@ -1,9 +1,6 @@
 ---
 title: Introducing GraphQL
 ---
-import Playground from '@site/src/components/Playground';
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
 
 :::info
 

package/docs/guides/getting-started/installation/index.mdx

@@ -3,9 +3,6 @@ title: 'Installation'
 sidebar_position: 1
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 ## Requirements
 
 - [Node.js](https://nodejs.org/en/) **v20**, **v22** and **v24** - these versions are tested and supported. (Odd-numbered versions above v20 should still work but are not officially supported.)

package/docs/guides/getting-started/try-the-api/index.mdx

@@ -2,9 +2,6 @@
 title: 'Try the API'
 ---
 
-
-import Playground from '@site/src/components/Playground';
-
 Once you have successfully installed Vendure locally following the [installation guide](/guides/getting-started/installation),
 it's time to try out the API!
 

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

@@ -2,9 +2,6 @@
 title: 'Building a CMS Integration Plugin'
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 A CMS integration plugin allows you to automatically synchronize your Vendure product catalog with an external Content Management System.
 
 This is done in a way that establishes Vendure as the source of truth for the ecommerce's data.

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

@@ -2,10 +2,6 @@
 title: "Digital Products"
 ---
 
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Digital products include things like ebooks, online courses, and software. They are products that are delivered to the customer electronically, and do not require
 physical shipping.
 

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

@@ -2,10 +2,6 @@
 title: "GitHub OAuth Authentication"
 ---
 
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 :::info
 The complete source of the following example plugin can be found here: [example-plugins/github-auth-plugin](https://github.com/vendurehq/examples/tree/publish/examples/shop-github-auth)
 :::

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

@@ -2,10 +2,6 @@
 title: "Google OAuth Authentication"
 ---
 
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 :::info
 The complete source of the following example plugin can be found here: [example-plugins/google-auth-plugin](https://github.com/vendurehq/examples/tree/publish/examples/shop-google-auth)
 :::

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

@@ -2,8 +2,6 @@
 title: "Multi-vendor Marketplaces"
 ---
 
-# Multi-vendor Marketplaces
-
 Vendure v2.0 introduced a number of changes and new APIs to enable developers to build multi-vendor marketplace apps.
 
 This is a type of application in which multiple sellers are able to list products, and then customers can create orders containing products from one or more of these sellers. Well-known examples include Amazon, Ebay, Etsy and Airbnb.

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

@@ -2,9 +2,6 @@
 title: "Paginated lists"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Vendure's list queries follow a set pattern which allows for pagination, filtering & sorting. This guide will demonstrate how
 to implement your own paginated list queries.
 

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

@@ -2,9 +2,6 @@
 title: "Publishing a Plugin"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Vendure's [plugin-based architecture](/guides/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.
 

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

@@ -2,10 +2,6 @@
 title: "Integrating S3-Compatible Asset Storage"
 ---
 
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This guide demonstrates how to integrate S3-compatible asset storage into your Vendure application using multiple cloud storage platforms. You'll learn to configure a single, platform-agnostic storage solution that works seamlessly with AWS S3, DigitalOcean Spaces, MinIO, CloudFlare R2, and Supabase Storage.
 
 ## Working Example Repository

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

@@ -2,8 +2,6 @@
 title: "Managing the Active Order"
 ---
 
-import Stackblitz from '@site/src/components/Stackblitz';
-
 The "active order" is what is also known as the "cart" - it is the order that is currently being worked on by the customer.
 
 An order remains active until it is completed, and during this time it can be modified by the customer in various ways:

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

@@ -2,9 +2,6 @@
 title: "Checkout Flow"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 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

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

@@ -2,10 +2,6 @@
 title: Connect to the API
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import Stackblitz from '@site/src/components/Stackblitz';
-
 The first thing you'll need to do is to connect your storefront app to the **Shop API**. The Shop API is a GraphQL API
 that provides access to the products, collections, customer data, and exposes mutations that allow you to add items to
 the cart, checkout, manage customer accounts, and more.

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

@@ -2,9 +2,6 @@
 title: "Customer Accounts"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Customers can register accounts and thereby gain the ability to:
 
 - View past orders

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

@@ -2,10 +2,6 @@
 title: "Listing Products"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import Stackblitz from '@site/src/components/Stackblitz';
-
 Products are listed when:
 
 - Displaying the contents of a collection

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

@@ -2,10 +2,6 @@
 title: "Navigation Menu"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import Stackblitz from '@site/src/components/Stackblitz';
-
 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

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

@@ -3,8 +3,6 @@ title: "Order Workflow"
 showtoc: true
 ---
 
-# Order Workflow
-
 An Order is a collection of one or more ProductVariants which can be purchased by a Customer. Orders are represented internally by the [Order entity](/reference/typescript-api/entities/order/) and in the GraphQL API by the [Order type](/reference/graphql-api/admin/enums/#ordertype).
 
 ## Order State

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

@@ -2,10 +2,6 @@
 title: "Product Detail Page"
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import Stackblitz from '@site/src/components/Stackblitz';
-
 The product detail page (often abbreviated to PDP) is the page that shows the details of a product and allows the user to add it to their cart.
 
 Typically, the PDP should include:

package/docs/reference/admin-ui-api/index.mdx

@@ -4,8 +4,6 @@ weight: 10
 showtoc: false
 ---
 
-# Vendure Admin UI API Docs
-
 These APIs are used when building your own custom extensions to the Admin UI provided by the AdminUiPlugin.
 
 :::note

package/docs/reference/graphql-api/_index.mdx

@@ -4,8 +4,6 @@ weight: 3
 showtoc: false
 ---
 
-# GraphQL API 
-
 This section contains a description of all queries, mutations and related types available in the Vendure GraphQL API.
 
 The API is split into two distinct endpoints: *Shop* and *Admin*. The Shop API is for storefront client applications, whereas the Admin API is used for administrative tasks.

package/docs/reference/graphql-api/admin/_index.mdx

@@ -4,8 +4,6 @@ weight: 4
 showtoc: false
 ---
 
-# GraphQL Admin API
-
 The Admin API is primarily used by the included Admin UI web app to perform administrative tasks such as inventory management, order tracking etc.
 
 :::note

package/docs/reference/graphql-api/shop/_index.mdx

@@ -4,8 +4,6 @@ weight: 3
 showtoc: false
 ---
 
-# GraphQL Shop API
-
 The Shop API is used by storefront applications. It provides all the necessary queries and mutations for finding and viewing products, creating and updating orders, checking out, managing a customer account etc.
 
 :::note

package/docs/reference/typescript-api/_index.mdx

@@ -4,8 +4,6 @@ weight: 9
 showtoc: false
 ---
 
-# Vendure TypeScript API Docs
-
 The Vendure TypeScript API is used when configuring the server (via the [`VendureConfig`](/reference/typescript-api/configuration/vendure-config/#vendureconfig) object) and when writing plugins that extend the functionality of Vendure core.
 
 :::note

package/docs/user-guide/catalog/collections.mdx

@@ -3,8 +3,6 @@ title: "Collections"
 weight: 2
 ---
 
-# Collections
-
 Collections allow you to group ProductVariants together by various criteria. A typical use of Collections is to create a hierarchical category tree which can be used in a navigation menu in your storefront.
 
 ## Populating Collections

package/docs/user-guide/catalog/facets.mdx

@@ -3,8 +3,6 @@ title: "Facets"
 weight: 1
 ---
 
-# Facets
-
 Facets are the primary means to attach structured data to your Products & ProductVariants. Typical uses of Facets include:
 
 * Enabling faceted search & filtering in the storefront

package/docs/user-guide/catalog/products.mdx

@@ -2,8 +2,6 @@
 title: "Products"
 ---
 
-# Products
-
 Products represent the items you want to sell to your customers.
 
 ## Products vs ProductVariants

package/docs/user-guide/customers/index.mdx

@@ -3,8 +3,6 @@ title: "Customers"
 weight: 2
 ---
 
-# Customers
-
 A Customer is anybody who has:
 
 * Placed an order

package/docs/user-guide/index.mdx

@@ -1,7 +1,9 @@
-# Vendure User Guide
+---
+title: "Vendure User Guide"
+---
 
 This section is for store owners and staff who are charged with running a Vendure-based store.
 
 This guide assumes that your Vendure instance is running the AdminUiPlugin.
 
-We will roughly structure this guide to conform to the default layout of the Admin UI main navigation menu. 
+We will roughly structure this guide to conform to the default layout of the Admin UI main navigation menu.

package/docs/user-guide/localization/index.mdx

@@ -3,8 +3,6 @@ title: "Localization"
 weight: 10
 ---
 
-# Localization
-
 Vendure supports **customer-facing** (Shop API) localization by allowing you to define translations for the following objects:
 
 * Collections

package/docs/user-guide/orders/draft-orders.mdx

@@ -2,8 +2,6 @@
 title: "Draft Orders"
 ---
 
-# Draft Orders
-
 Draft Orders are used when an Administrator would like to manually create an order via the Admin UI. For example, this can be useful when:
 
 - A customer phones up to place an order

package/docs/user-guide/orders/orders.mdx

@@ -3,8 +3,6 @@ title: "Orders"
 weight: 3
 ---
 
-# Orders
-
 An Order is created whenever someone adds an item to their cart in the storefront. In Vendure, there is no distinction between a "cart" and an "order". Thus a "cart" is just an Order which has not yet passed through the checkout process.
 
 ## The Order Workflow

package/docs/user-guide/promotions/index.mdx

@@ -3,8 +3,6 @@ title: "Promotions"
 weight: 4
 ---
 
-# Promotions
-
 Promotions are a means of offering discounts on an order based on various criteria. A Promotion consists of _conditions_ and _actions_.
 
 * **conditions** are the rules which determine whether the Promotion should be applied to the order.

package/docs/user-guide/settings/administrators-roles.mdx

@@ -2,8 +2,6 @@
 title: "Administrators & Roles"
 ---
 
-# Administrators & Roles
-
 An **administrator** is a staff member who has access to the Admin UI, and is able to view and modify some or all of the items and settings.
 
 The exact permissions of _what_ a given administrator may view and modify is defined by which **roles** are assigned to that administrator.

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

@@ -2,8 +2,6 @@
 title: "Channels"
 ---
 
-# Channels
-
 Channels allow you to split your store into multiple sub-stores, each of which can have its own selection of inventory, customers, orders, shipping methods etc.
 
 There are various reasons why you might want to do this:

package/docs/user-guide/settings/countries-zones.mdx

@@ -2,8 +2,6 @@
 title: "Countries & Zones"
 ---
 
-# Countries & Zones
-
 **Countries** are where you define the list of countries which are relevant to your operations. This does not only include those countries you ship to, but also those countries which may appear on a billing address.
 
 By default, Vendure includes all countries in the list, but you are free to remove or disable any that you don't need.

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

@@ -2,8 +2,6 @@
 title: "Global Settings"
 ---
 
-# Global Settings
-
 The global settings allow you to define certain configurations that affect _all_ channels.
 
 * **Available languages** defines which languages you wish to make available for translations. When more than one language has been enabled, you will see the language switcher appear when viewing translatable objects such as products, collections, facets and shipping methods.

package/docs/user-guide/settings/payment-methods.mdx

@@ -2,8 +2,6 @@
 title: "Payment Methods"
 ---
 
-# Payment Methods
-
 Payment methods define how your storefront handles payments. Your storefront may offer multiple payment methods or just one.
 
 A Payment method consists of two parts: an **eligibility checker** and a **handler**

package/docs/user-guide/settings/shipping-methods.mdx

@@ -2,8 +2,6 @@
 title: "Shipping Methods"
 ---
 
-# Shipping Methods
-
 Shipping methods define:
 
 * Whether an order is eligible for a particular shipping method

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

@@ -2,8 +2,6 @@
 title: "Taxes"
 ---
 
-# Taxes
-
 Taxes represent extra charges on top of the base price of a product. There are various forms of taxes that might be applicable, depending on local laws and the laws of the regions that your business serves. Common forms of applicable taxes are:
 
 * Value added tax (VAT)

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@vendure/docs",
-    "version": "0.0.0-202601161603",
+    "version": "0.0.0-202601161637",
     "type": "module",
     "main": "dist/index.js",
     "types": "dist/index.d.ts",