@spree/docs 0.1.0 → 0.1.1

package/dist/developer/core-concepts/products.md

@@ -9,7 +9,7 @@ A product represents something you sell. Each product has one or more **variants
 
 Products are organized into **categories** — a flexible hierarchy for grouping products. Categories can be filtered, sorted, and searched via the Store API.
 
-> **INFO:** Product names, descriptions, slugs, and SEO fields are [translatable](/developer/core-concepts/translations#resource-translations).
+> **INFO:** Product names, descriptions, slugs, and SEO fields are [translatable](translations.md#resource-translations).
 
 ```mermaid
 erDiagram
@@ -117,7 +117,7 @@ curl 'https://api.mystore.com/api/v3/store/products?q[search]=tote+bag' \
 ```
 
 
-See [Querying](/api-reference/store-api/querying) for the full list of filtering, sorting, and pagination options.
+See [Querying](../../api-reference/store-api/querying.md) for the full list of filtering, sorting, and pagination options.
 
 ## Getting a Product
 
@@ -297,7 +297,7 @@ curl 'https://api.mystore.com/api/v3/store/products/spree-tote?expand=media,vari
 
 ## Prices
 
-Each variant can have multiple prices — one per currency, plus additional prices from [Price Lists](/developer/core-concepts/pricing) that apply conditionally based on market, geography, customer segment, or quantity.
+Each variant can have multiple prices — one per currency, plus additional prices from [Price Lists](pricing.md) that apply conditionally based on market, geography, customer segment, or quantity.
 
 The API automatically returns the correct price based on the current currency and market context:
 
@@ -306,7 +306,7 @@ The API automatically returns the correct price based on the current currency an
 | `price` | Current selling price |
 | `original_price` | Compare-at price (for showing strikethrough discounts) |
 
-See the [Pricing](/developer/core-concepts/pricing) guide for details on Price Lists, Price Rules, and market-specific pricing.
+See the [Pricing](pricing.md) guide for details on Price Lists, Price Rules, and market-specific pricing.
 
 ## Categories
 
@@ -352,9 +352,9 @@ curl 'https://api.mystore.com/api/v3/store/categories/clothing/shirts/products?l
 
 ## Related Documentation
 
-- [Pricing](/developer/core-concepts/pricing) — Price Lists, Price Rules, and market-specific pricing
-- [Inventory](/developer/core-concepts/inventory) — Stock management and backorders
-- [Media](/developer/core-concepts/media) — Image management
-- [Translations](/developer/core-concepts/translations) — Translating product content
-- [Search & Filtering](/developer/core-concepts/search-filtering) — Full-text search and Ransack filtering
-- [Querying](/api-reference/store-api/querying) — API filtering, sorting, and pagination
+- [Pricing](pricing.md) — Price Lists, Price Rules, and market-specific pricing
+- [Inventory](inventory.md) — Stock management and backorders
+- [Media](media.md) — Image management
+- [Translations](translations.md) — Translating product content
+- [Search & Filtering](search-filtering.md) — Full-text search and Ransack filtering
+- [Querying](../../api-reference/store-api/querying.md) — API filtering, sorting, and pagination

package/dist/developer/core-concepts/promotions.md

@@ -70,7 +70,7 @@ erDiagram
 - **Promotion Rules** determine eligibility conditions (FirstOrder, ItemTotal, Taxon, etc.)
 - **Promotion Actions** define what happens when applied (discount, free shipping, free items)
 - **Coupon Codes** track usage for code-based promotions
-- **[Adjustments](/developer/core-concepts/adjustments)** are created on orders/line items to apply discounts
+- **[Adjustments](adjustments.md)** are created on orders/line items to apply discounts
 
 Promotions can be activated in two ways:
 
@@ -316,7 +316,7 @@ How promotions are evaluated and applied:
 
 ## Related Documentation
 
-- [Build Custom Promotion Rules & Actions](/developer/how-to/custom-promotion) - Step-by-step guide to creating custom rules and actions
-- [Calculators](/developer/core-concepts/calculators) - Learn about promotion calculators
-- [Orders](/developer/core-concepts/orders) - Understanding order processing
-- [Customization Quickstart](/developer/customization/quickstart) - Overview of customization options
+- [Build Custom Promotion Rules & Actions](../how-to/custom-promotion.md) - Step-by-step guide to creating custom rules and actions
+- [Calculators](calculators.md) - Learn about promotion calculators
+- [Orders](orders.md) - Understanding order processing
+- [Customization Quickstart](../customization/quickstart.md) - Overview of customization options

package/dist/developer/core-concepts/reports.md

@@ -202,5 +202,5 @@ can :manage, Spree::Report
 
 ## Related Documentation
 
-- [Build a Custom Report](/developer/how-to/custom-report) - Step-by-step guide to creating custom reports
-- [Events](/developer/core-concepts/events) - How report generation uses the events system
+- [Build a Custom Report](../how-to/custom-report.md) - Step-by-step guide to creating custom reports
+- [Events](events.md) - How report generation uses the events system

package/dist/developer/core-concepts/search-filtering.md

@@ -214,11 +214,11 @@ curl 'https://api.mystore.com/api/v3/store/products?page=1&limit=24' \
 ```
 
 
-See [Querying](/api-reference/store-api/querying) for the full list of filtering, sorting, and pagination options.
+See [Querying](../../api-reference/store-api/querying.md) for the full list of filtering, sorting, and pagination options.
 
 ## Search Providers
 
-Spree uses a pluggable search provider architecture. The default provider uses SQL (ILIKE + Ransack). For production catalogs with 1,000+ products, we recommend switching to [Meilisearch](/integrations/search/meilisearch) for typo tolerance, relevance ranking, and faster faceted search.
+Spree uses a pluggable search provider architecture. The default provider uses SQL (ILIKE + Ransack). For production catalogs with 1,000+ products, we recommend switching to [Meilisearch](../../integrations/search/meilisearch.md) for typo tolerance, relevance ranking, and faster faceted search.
 
 ```ruby
 # config/initializers/spree.rb
@@ -227,11 +227,11 @@ Spree.search_provider = 'Spree::SearchProvider::Meilisearch'
 
 No client-side or API changes are needed — the same `q[search]`, filter params, and sort options work with any provider.
 
-See [Build a Custom Search Provider](/developer/how-to/custom-search-provider) for architecture details and how to build custom providers.
+See [Build a Custom Search Provider](../how-to/custom-search-provider.md) for architecture details and how to build custom providers.
 
 ## Related Documentation
 
-- [Products](/developer/core-concepts/products) — Product catalog and listing
-- [Querying](/api-reference/store-api/querying) — API filtering, sorting, and pagination reference
-- [Build a Custom Search Provider](/developer/how-to/custom-search-provider) — Step-by-step guide
-- [Meilisearch Integration](/integrations/search/meilisearch) — Setup guide
+- [Products](products.md) — Product catalog and listing
+- [Querying](../../api-reference/store-api/querying.md) — API filtering, sorting, and pagination reference
+- [Build a Custom Search Provider](../how-to/custom-search-provider.md) — Step-by-step guide
+- [Meilisearch Integration](../../integrations/search/meilisearch.md) — Setup guide

package/dist/developer/core-concepts/shipments.md

@@ -5,7 +5,7 @@ description: Shipping methods, rates, split shipments, and fulfillment
 
 ## Overview
 
-A shipment represents a package being sent to a customer from a [Stock Location](/developer/core-concepts/inventory#stock-locations). Each order can have one or more shipments — Spree automatically splits orders into multiple shipments when items need to ship from different locations or require different shipping methods.
+A shipment represents a package being sent to a customer from a [Stock Location](inventory.md#stock-locations). Each order can have one or more shipments — Spree automatically splits orders into multiple shipments when items need to ship from different locations or require different shipping methods.
 
 ```mermaid
 erDiagram
@@ -41,10 +41,10 @@ erDiagram
 ```
 
 **Key relationships:**
-- **Shipment** tracks delivery of items from a [Stock Location](/developer/core-concepts/inventory#stock-locations)
+- **Shipment** tracks delivery of items from a [Stock Location](inventory.md#stock-locations)
 - **Shipping Method** defines the carrier/service (UPS, FedEx, etc.)
 - **Shipping Rate** represents the calculated cost for a method
-- **[Zone](/developer/core-concepts/addresses#zones)** defines geographic regions for shipping availability
+- **[Zone](addresses.md#zones)** defines geographic regions for shipping availability
 - **Shipping Category** groups products with similar shipping requirements
 
 ## Shipment Attributes
@@ -120,9 +120,9 @@ curl -X PATCH 'https://api.mystore.com/api/v3/store/carts/cart_xxx/shipments/shp
 
 Shipping methods represent the carrier services available to customers (e.g., UPS Ground, FedEx Overnight, DHL International). Each shipping method is scoped to:
 
-- **[Zones](/developer/core-concepts/addresses#zones)** — geographic regions where the method is available
+- **[Zones](addresses.md#zones)** — geographic regions where the method is available
 - **Shipping Categories** — product groups the method handles
-- **[Stores](/developer/core-concepts/stores)** — which stores offer this method
+- **[Stores](stores.md)** — which stores offer this method
 
 Only methods whose zone matches the customer's shipping address are offered at checkout.
 
@@ -139,7 +139,7 @@ Each product is assigned a shipping category. Shipping methods can be restricted
 
 ### Calculators
 
-Each shipping method uses a [Calculator](/developer/core-concepts/calculators) to determine the cost. Spree includes these built-in calculators:
+Each shipping method uses a [Calculator](calculators.md) to determine the cost. Spree includes these built-in calculators:
 
 | Calculator | Description |
 |------------|-------------|
@@ -149,7 +149,7 @@ Each shipping method uses a [Calculator](/developer/core-concepts/calculators) t
 | Flexible rate | One rate for the first item, another for each additional |
 | Price sack | Tiered pricing based on order total |
 
-You can create custom calculators for more complex pricing. See the [Calculators guide](/developer/core-concepts/calculators).
+You can create custom calculators for more complex pricing. See the [Calculators guide](calculators.md).
 
 ## Split Shipments
 
@@ -175,7 +175,7 @@ flowchart TB
 
 By default, Spree also splits shipments when a package exceeds a weight threshold (default: 150 units). This prevents individual packages from being too heavy.
 
-> **INFO:** Split shipment behavior is customizable. See the [Customization Quickstart](/developer/customization/quickstart) for details on creating custom splitting rules.
+> **INFO:** Split shipment behavior is customizable. See the [Customization Quickstart](../customization/quickstart.md) for details on creating custom splitting rules.
 
 ## Examples
 
@@ -205,8 +205,8 @@ A store shipping from 2 locations (New York, Los Angeles) with 3 carriers and 3
 
 ## Related Documentation
 
-- [Orders](/developer/core-concepts/orders) — Checkout flow and shipping rate selection
-- [Inventory](/developer/core-concepts/inventory) — Stock locations and inventory management
-- [Calculators](/developer/core-concepts/calculators) — Shipping rate calculators
-- [Addresses](/developer/core-concepts/addresses) — Shipping address and zones
-- [Events](/developer/core-concepts/events) — Subscribe to shipment events (e.g., `shipment.shipped`)
+- [Orders](orders.md) — Checkout flow and shipping rate selection
+- [Inventory](inventory.md) — Stock locations and inventory management
+- [Calculators](calculators.md) — Shipping rate calculators
+- [Addresses](addresses.md) — Shipping address and zones
+- [Events](events.md) — Subscribe to shipment events (e.g., `shipment.shipped`)

package/dist/developer/core-concepts/slugs.md

@@ -106,6 +106,6 @@ Spree prevents certain words from being used as slugs to avoid route conflicts:
 
 ## Related Documentation
 
-- [Products](/developer/core-concepts/products) — Product catalog
-- [Translations](/developer/core-concepts/translations) — Multi-language content
-- [Querying](/api-reference/store-api/querying) — API resource lookup
+- [Products](products.md) — Product catalog
+- [Translations](translations.md) — Multi-language content
+- [Querying](../../api-reference/store-api/querying.md) — API resource lookup

package/dist/developer/core-concepts/staff-roles.md

@@ -45,7 +45,7 @@ Admin users can have different roles that control their permissions:
 |------|-------------|
 | `admin` | Full access to all Admin Panel features |
 
-> **INFO:** You can create custom roles with specific permissions. See the [Customize Permissions guide](/developer/customization/permissions) for details.
+> **INFO:** You can create custom roles with specific permissions. See the [Customize Permissions guide](../customization/permissions.md) for details.
 
 ## Creating Admin Users
 
@@ -101,7 +101,7 @@ flowchart TB
 
 ### Invitation Events
 
-The invitation system publishes [events](/developer/core-concepts/events) you can subscribe to:
+The invitation system publishes [events](events.md) you can subscribe to:
 
 | Event | Description |
 |-------|-------------|
@@ -113,11 +113,11 @@ The invitation system publishes [events](/developer/core-concepts/events) you ca
 
 Spree uses [CanCanCan](https://github.com/CanCanCommunity/cancancan) for authorization. Permissions apply to both customers (Store API access) and admins (Admin Panel access).
 
-See the [Customize Permissions guide](/developer/customization/permissions) for details on creating custom roles and permission sets.
+See the [Customize Permissions guide](../customization/permissions.md) for details on creating custom roles and permission sets.
 
 ## Related Documentation
 
-- [Customers](/developer/core-concepts/customers) — Customer accounts and authentication
-- [Stores](/developer/core-concepts/stores) — Multi-store setup
-- [Permissions](/developer/customization/permissions) — Roles and authorization
-- [Events](/developer/core-concepts/events) — Subscribe to invitation events
+- [Customers](customers.md) — Customer accounts and authentication
+- [Stores](stores.md) — Multi-store setup
+- [Permissions](../customization/permissions.md) — Roles and authorization
+- [Events](events.md) — Subscribe to invitation events

package/dist/developer/core-concepts/store-credits-gift-cards.md

@@ -311,7 +311,7 @@ When a registered customer has multiple store credits, they are applied in order
 
 ## Related Documentation
 
-- [Payments](/developer/core-concepts/payments) — Payment processing and methods
-- [Orders](/developer/core-concepts/orders) — Order management
-- [Customers](/developer/core-concepts/customers) — Customer management
-- [Events](/developer/core-concepts/events) — Event system and subscribers
+- [Payments](payments.md) — Payment processing and methods
+- [Orders](orders.md) — Order management
+- [Customers](customers.md) — Customer management
+- [Events](events.md) — Event system and subscribers

package/dist/developer/core-concepts/stores.md

@@ -5,7 +5,7 @@ description: The central model in Spree — every resource is scoped to a store
 
 ## Overview
 
-The Store is the central model in Spree. Every resource — products, orders, markets, payment methods, taxonomies — is scoped to a store. Most setups use a single store, but Spree supports [multi-store](/developer/multi-store/quickstart) configurations where each store operates independently with its own catalog, branding, and checkout.
+The Store is the central model in Spree. Every resource — products, orders, markets, payment methods, taxonomies — is scoped to a store. Most setups use a single store, but Spree supports [multi-store](../multi-store/quickstart.md) configurations where each store operates independently with its own catalog, branding, and checkout.
 
 ```mermaid
 erDiagram
@@ -83,13 +83,13 @@ curl 'https://api.mystore.com/api/v3/store/store' \
 
 ## Markets
 
-[Markets](/developer/core-concepts/markets) let you segment your store into geographic regions, each with its own currency, locale, and set of countries. For example, a single store can have:
+[Markets](markets.md) let you segment your store into geographic regions, each with its own currency, locale, and set of countries. For example, a single store can have:
 
 - **North America** — USD, English, ships to US and Canada
 - **Europe** — EUR, German, ships to DE, FR, AT, NL
 - **United Kingdom** — GBP, English, ships to GB
 
-See the [Markets](/developer/core-concepts/markets) guide for details.
+See the [Markets](markets.md) guide for details.
 
 ## Store Resources
 
@@ -97,21 +97,21 @@ Each store has its own set of resources. This means products, orders, and promot
 
 | Resource | Relationship |
 |----------|-------------|
-| [**Markets**](/developer/core-concepts/markets) | A store has many markets, each defining a geographic region with its own currency and locale |
-| [**Orders**](/developer/core-concepts/orders) | An order belongs to one store |
-| [**Products**](/developer/core-concepts/products) | A product can be available in multiple stores |
-| [**Payment Methods**](/developer/core-concepts/payments) | A payment method can be available in multiple stores |
-| [**Shipping Methods**](/developer/core-concepts/shipments) | A shipping method can be available in multiple stores |
-| [**Taxonomies**](/developer/core-concepts/products#taxons-and-taxonomies) | A taxonomy belongs to one store |
-| [**Promotions**](/developer/core-concepts/promotions) | A promotion can apply to multiple stores |
+| [**Markets**](markets.md) | A store has many markets, each defining a geographic region with its own currency and locale |
+| [**Orders**](orders.md) | An order belongs to one store |
+| [**Products**](products.md) | A product can be available in multiple stores |
+| [**Payment Methods**](payments.md) | A payment method can be available in multiple stores |
+| [**Shipping Methods**](shipments.md) | A shipping method can be available in multiple stores |
+| [**Taxonomies**](products.md#taxons-and-taxonomies) | A taxonomy belongs to one store |
+| [**Promotions**](promotions.md) | A promotion can apply to multiple stores |
 
 ## Multi-Store Setup
 
-To run multiple stores from a single Spree installation, see the [Multi-Store guide](/developer/multi-store/quickstart). Each store gets its own domain, branding, catalog, and checkout — while sharing the same admin dashboard and infrastructure.
+To run multiple stores from a single Spree installation, see the [Multi-Store guide](../multi-store/quickstart.md). Each store gets its own domain, branding, catalog, and checkout — while sharing the same admin dashboard and infrastructure.
 
 ## Related Documentation
 
-- [Markets](/developer/core-concepts/markets) — Multi-region commerce within a store
-- [Products](/developer/core-concepts/products) — Product catalog
-- [Orders](/developer/core-concepts/orders) — Order management and checkout
-- [Multi-Store](/developer/multi-store/quickstart) — Running multiple stores
+- [Markets](markets.md) — Multi-region commerce within a store
+- [Products](products.md) — Product catalog
+- [Orders](orders.md) — Order management and checkout
+- [Multi-Store](../multi-store/quickstart.md) — Running multiple stores

package/dist/developer/core-concepts/taxes.md

@@ -5,7 +5,7 @@ description: Tax categories, tax rates, zones, and how Spree calculates taxes at
 
 ## Overview
 
-Spree uses Tax Categories and Tax Rates to calculate taxes for orders. Products are assigned to tax categories, and tax rates define the percentage charged within specific geographic [Zones](/developer/core-concepts/addresses#zones).
+Spree uses Tax Categories and Tax Rates to calculate taxes for orders. Products are assigned to tax categories, and tax rates define the percentage charged within specific geographic [Zones](addresses.md#zones).
 
 ```mermaid
 erDiagram
@@ -35,9 +35,9 @@ erDiagram
 
 **Key relationships:**
 - **Tax Category** groups products for tax purposes (e.g., "Clothing", "Food", "Digital")
-- **Tax Rate** defines the percentage and rules for a Tax Category within a [Zone](/developer/core-concepts/addresses#zones)
+- **Tax Rate** defines the percentage and rules for a Tax Category within a [Zone](addresses.md#zones)
 - **Zone** defines geographic regions (countries or states) where taxes apply
-- **[Adjustments](/developer/core-concepts/adjustments)** are created on orders/line items to apply taxes
+- **[Adjustments](adjustments.md)** are created on orders/line items to apply taxes
 
 ## Tax Categories
 
@@ -86,7 +86,7 @@ Common in Europe and many other countries. The displayed price **already include
 - Displayed price: **£17.99** (includes £0.86 VAT)
 - If shipped outside VAT zone: price reduces to **£17.13**
 
-> **INFO:** The `tax_inclusive` setting on [Markets](/developer/core-concepts/markets) controls whether prices are displayed with or without tax for each geographic region.
+> **INFO:** The `tax_inclusive` setting on [Markets](markets.md) controls whether prices are displayed with or without tax for each geographic region.
 
 ## Default Tax Zone
 
@@ -98,12 +98,12 @@ If the customer's shipping address is outside the default tax zone, the assumed
 
 During checkout, taxes are calculated based on the shipping address:
 
-1. The customer's shipping address determines their [Zone](/developer/core-concepts/addresses#zones)
+1. The customer's shipping address determines their [Zone](addresses.md#zones)
 2. Spree finds matching tax rates for that zone and the product's tax category
-3. Tax [Adjustments](/developer/core-concepts/adjustments) are created on line items
+3. Tax [Adjustments](adjustments.md) are created on line items
 4. The order total is updated
 
-> **NOTE:** For complex tax requirements (interstate US sales, international VAT), consider using automated tax calculation. The [Stripe Tax integration](/integrations/payments/stripe) handles this automatically.
+> **NOTE:** For complex tax requirements (interstate US sales, international VAT), consider using automated tax calculation. The [Stripe Tax integration](../../integrations/payments/stripe.md) handles this automatically.
 
 ## Managing Taxes
 
@@ -129,7 +129,7 @@ Tax categories and rates are managed in the Admin Panel under **Settings → Tax
 
 ## Related Documentation
 
-- [Markets](/developer/core-concepts/markets) — Tax-inclusive pricing per market
-- [Addresses](/developer/core-concepts/addresses) — Zones and address-based taxation
-- [Adjustments](/developer/core-concepts/adjustments) — Tax adjustments
-- [Orders](/developer/core-concepts/orders) — How taxes affect order totals
+- [Markets](markets.md) — Tax-inclusive pricing per market
+- [Addresses](addresses.md) — Zones and address-based taxation
+- [Adjustments](adjustments.md) — Tax adjustments
+- [Orders](orders.md) — How taxes affect order totals

package/dist/developer/core-concepts/translations.md

@@ -10,7 +10,7 @@ Spree supports two types of translations:
 1. **Resource Translations** — translatable content fields on models like Products, Taxons, and Stores (e.g., product name, description, slug)
 2. **UI Translations** — interface strings used in the admin panel (e.g., button labels, flash messages)
 
-For configuring which locales and currencies are available in your store, see [Markets](/developer/core-concepts/markets). Markets control locale and currency assignment per geographic region.
+For configuring which locales and currencies are available in your store, see [Markets](markets.md). Markets control locale and currency assignment per geographic region.
 
 ## Resource Translations
 
@@ -90,7 +90,7 @@ curl 'https://api.mystore.com/api/v3/store/products/spree-tote' \
 ```
 
 
-Slugs are also localized — a product can have different slugs per locale. See [Slugs](/developer/core-concepts/slugs#internationalization) for details.
+Slugs are also localized — a product can have different slugs per locale. See [Slugs](slugs.md#internationalization) for details.
 
 ### Managing Translations
 
@@ -114,7 +114,7 @@ Once installed, all translation files are available automatically — no need to
 
 ## Related Documentation
 
-- [Markets](/developer/core-concepts/markets) — Locale and currency configuration per geographic region
-- [Slugs](/developer/core-concepts/slugs) — Localized slugs and URL identifiers
-- [Stores](/developer/core-concepts/stores) — Multi-store setup
-- [Products](/developer/core-concepts/products) — Product translations
+- [Markets](markets.md) — Locale and currency configuration per geographic region
+- [Slugs](slugs.md) — Localized slugs and URL identifiers
+- [Stores](stores.md) — Multi-store setup
+- [Products](products.md) — Product translations

package/dist/developer/core-concepts/users.md

@@ -15,7 +15,7 @@ Spree has two separate user types:
 | Customers | `Spree.user_class` | `Spree::User` |
 | Admins | `Spree.admin_user_class` | `Spree::AdminUser` |
 
-> **INFO:** You can use your own user classes. See the [Customize Authentication guide](/developer/customization/authentication) for details.
+> **INFO:** You can use your own user classes. See the [Customize Authentication guide](../customization/authentication.md) for details.
 
 ## Customers
 
@@ -166,8 +166,8 @@ Authenticated customers have access to these resources:
 
 | Resource | Description |
 |----------|-------------|
-| [**Addresses**](/developer/core-concepts/addresses#customer-address-book) | Billing and shipping addresses with default selection |
-| [**Orders**](/developer/core-concepts/orders#order-history) | Past order history |
+| [**Addresses**](addresses.md#customer-address-book) | Billing and shipping addresses with default selection |
+| [**Orders**](orders.md#order-history) | Past order history |
 | **Credit Cards** | Saved credit cards for checkout |
 | **Payment Sources** | Other saved payment methods (PayPal, Klarna, etc.) |
 | **Store Credits** | Balance assigned by the store, usable at checkout |
@@ -176,7 +176,7 @@ Authenticated customers have access to these resources:
 
 ### Guest Checkout
 
-Customers don't need to register to purchase. Guest checkout uses an order token (`X-Spree-Token`) to identify the cart. See [Orders — Cart](/developer/core-concepts/orders#cart) for details.
+Customers don't need to register to purchase. Guest checkout uses an order token (`X-Spree-Token`) to identify the cart. See [Orders — Cart](orders.md#cart) for details.
 
 ## Admin Users
 
@@ -220,7 +220,7 @@ Admin users can have different roles that control their permissions:
 |------|-------------|
 | `admin` | Full access to all Admin Panel features |
 
-> **INFO:** You can create custom roles with specific permissions. See the [Customize Permissions guide](/developer/customization/permissions) for details.
+> **INFO:** You can create custom roles with specific permissions. See the [Customize Permissions guide](../customization/permissions.md) for details.
 
 ### Creating Admin Users
 
@@ -276,7 +276,7 @@ flowchart TB
 
 #### Invitation Events
 
-The invitation system publishes [events](/developer/core-concepts/events) you can subscribe to:
+The invitation system publishes [events](events.md) you can subscribe to:
 
 | Event | Description |
 |-------|-------------|
@@ -288,12 +288,12 @@ The invitation system publishes [events](/developer/core-concepts/events) you ca
 
 Spree uses [CanCanCan](https://github.com/CanCanCommunity/cancancan) for authorization. Permissions apply to both customers (Store API access) and admins (Admin Panel access).
 
-See the [Customize Permissions guide](/developer/customization/permissions) for details on creating custom roles and permission sets.
+See the [Customize Permissions guide](../customization/permissions.md) for details on creating custom roles and permission sets.
 
 ## Related Documentation
 
-- [Addresses](/developer/core-concepts/addresses) — Customer address management
-- [Orders](/developer/core-concepts/orders) — Order history and checkout
-- [Authentication](/developer/customization/authentication) — Custom authentication setup
-- [Permissions](/developer/customization/permissions) — Roles and authorization
-- [Events](/developer/core-concepts/events) — Subscribe to user and invitation events
+- [Addresses](addresses.md) — Customer address management
+- [Orders](orders.md) — Order history and checkout
+- [Authentication](../customization/authentication.md) — Custom authentication setup
+- [Permissions](../customization/permissions.md) — Roles and authorization
+- [Events](events.md) — Subscribe to user and invitation events

package/dist/developer/core-concepts/webhooks.md

@@ -7,7 +7,7 @@ description: Send real-time HTTP notifications to external services when events
 
 Webhooks allow your Spree store to send real-time HTTP POST notifications to external services when events occur. When an order is completed, a product is updated, or inventory changes, Spree can automatically notify your CRM, fulfillment service, analytics platform, or any other system.
 
-Webhooks are built on top of Spree's [event system](/developer/core-concepts/events), providing:
+Webhooks are built on top of Spree's [event system](events.md), providing:
 
 - **Multi-store support** - Each store has its own webhook endpoints
 - **Event filtering** - Subscribe to specific events or patterns with wildcards
@@ -113,7 +113,7 @@ endpoint.subscriptions = ['*'] # All events (explicit)
 
 ## Webhook Payload
 
-Each webhook delivery sends a JSON payload with the following structure. The `data` object uses the same [Store API V3 serializers](/api-reference/introduction) as the REST API, so webhook payloads and API responses share the same schema:
+Each webhook delivery sends a JSON payload with the following structure. The `data` object uses the same [Store API V3 serializers](../../api-reference/introduction.md) as the REST API, so webhook payloads and API responses share the same schema:
 
 ```json
 {
@@ -143,10 +143,10 @@ Each webhook delivery sends a JSON payload with the following structure. The `da
 | `id` | Unique UUID for this event |
 | `name` | Event name (e.g., `order.completed`) |
 | `created_at` | ISO8601 timestamp when event occurred |
-| `data` | Serialized resource data (V3 API format with [prefixed IDs](/api-reference/introduction)) |
+| `data` | Serialized resource data (V3 API format with [prefixed IDs](../../api-reference/introduction.md)) |
 | `metadata` | Additional context including Spree version |
 
-For complete payload schemas for each event type, see [Webhook Events & Payloads](/api-reference/webhooks-events).
+For complete payload schemas for each event type, see [Webhook Events & Payloads](../../api-reference/webhooks-events.md).
 
 ## HTTP Request Details
 
@@ -276,7 +276,7 @@ Spree::Api::Config.webhooks_verify_ssl = false # Disable (not recommended for pr
 
 ## Available Events
 
-Webhooks can subscribe to any event in Spree's event system. See [Events](/developer/core-concepts/events#available-events) for a complete list.
+Webhooks can subscribe to any event in Spree's event system. See [Events](events.md#available-events) for a complete list.
 
 Common webhook events include:
 
@@ -373,6 +373,6 @@ delivery.response_body   # => Response from your endpoint
 
 ## Related Documentation
 
-- [Events](/developer/core-concepts/events) - Understanding Spree's event system
-- [Customization Quickstart](/developer/customization/quickstart) - Overview of all customization options
-- [Dependencies](/developer/customization/dependencies) - Customizing Spree services
+- [Events](events.md) - Understanding Spree's event system
+- [Customization Quickstart](../customization/quickstart.md) - Overview of all customization options
+- [Dependencies](../customization/dependencies.md) - Customizing Spree services

package/dist/developer/create-spree-app/quickstart.md

@@ -91,11 +91,11 @@ This replaces `docker-compose.yml` with a version that builds from `backend/`, r
 - **Configure Spree** in `backend/config/initializers/spree.rb`
 - **Add migrations** with `cd backend && bin/rails generate migration`
 
-See the [Customization Guide](/developer/customization) for more details.
+See the [Customization Guide](../customization.md) for more details.
 
 ### Spree CLI Commands
 
-The project includes [@spree/cli](/developer/cli/quickstart) for managing your Spree backend:
+The project includes [@spree/cli](../cli/quickstart.md) for managing your Spree backend:
 
 | Command | Description |
 |---------|-------------|
@@ -152,7 +152,7 @@ SPREE_VERSION_TAG=5.4
 ## Next Steps
 
 
-  - [Next.js Storefront](/developer/storefront/nextjs/quickstart) — Customize and extend the Storefront
-  - [Spree SDK](/developer/sdk/quickstart) — TypeScript SDK for the Store and Admin APIs
+  - [Next.js Storefront](../storefront/nextjs/quickstart.md) — Customize and extend the Storefront
+  - [Spree SDK](../sdk/quickstart.md) — TypeScript SDK for the Store and Admin APIs
   - [API Reference](/api-reference) — Explore the REST API endpoints
-  - [Core Concepts](/developer/core-concepts/architecture) — Learn about Spree's architecture
+  - [Core Concepts](../core-concepts/architecture.md) — Learn about Spree's architecture

package/dist/developer/customization/api.md

@@ -32,7 +32,7 @@ You can easily replace existing Spree serializers with your own thanks to [Spree
 
 ### Adding custom attributes
 
-> **NOTE:** As a rule of thumb it's recommended to use [Properties](/developer/core-concepts/products#product-properties) and [OptionTypes/Option Values](/developer/core-concepts/products#option-types-and-option-values) for custom attributes and not to modify the Spree database schema
+> **NOTE:** As a rule of thumb it's recommended to use [Properties](../core-concepts/products.md#product-properties) and [OptionTypes/Option Values](../core-concepts/products.md#option-types-and-option-values) for custom attributes and not to modify the Spree database schema
 
 Let's say you want to customize the Storefront API's [Product serializer](https://github.com/spree/spree/blob/main/api/app/serializers/spree/v2/storefront/product_serializer.rb) to include you custom database column `my_newcustom_attribute` that you've added to the `spree_products` database table.
 
@@ -58,7 +58,7 @@ Now let's tell Spree to use this new serializer, in `config/initializers/spree.r
 Spree::Api::Dependencies.storefront_product_serializer = 'MyProductSerializer'
 ```
 
-Restart the webserver and hit the [Products API](/api-reference/storefront/products/list-all-products) to notice that the payload now includes your new attribute.
+Restart the webserver and hit the [Products API](../../api-reference/storefront/products/list-all-products.md) to notice that the payload now includes your new attribute.
 
 ### Adding a new association
 

package/dist/developer/customization/authentication.md

@@ -4,7 +4,7 @@ description: Learn how to use a custom authentication setup with Spree
 version: v5
 ---
 
-If you installed Spree following the [Quickstart guide](/developer/quickstart), you can completely skip this step - you are all set and integrated with the [Devise](https://github.com/plataformatec/devise) gem.
+If you installed Spree following the [Quickstart guide](../quickstart.md), you can completely skip this step - you are all set and integrated with the [Devise](https://github.com/plataformatec/devise) gem.
 
 However if you're adding Spree to an existing application that has its own authentication system, you will need to follow these steps.
 
@@ -85,4 +85,4 @@ end
 
 ## Admin Panel authentication
 
-Please refer to the [Admin Panel Authentication](/developer/admin/authentication) page for more details.
+Please refer to the [Admin Panel Authentication](../admin/authentication.md) page for more details.