@spree/docs 0.1.0 → 0.1.1

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

@@ -13,7 +13,7 @@ Markets → Countries → Zones → Tax Rates & Shipping Methods
                   ↘ Addresses
 ```
 
-- [**Markets**](/developer/core-concepts/markets) group countries into selling regions with their own currency and locale
+- [**Markets**](markets.md) group countries into selling regions with their own currency and locale
 - **Countries** and **States** provide the geographic data for addresses
 - **Zones** group countries or states together to define where tax rates and shipping methods apply
 - **Addresses** tie a customer to a specific location, determining which zones — and therefore which taxes and shipping options — apply to their order
@@ -156,7 +156,7 @@ curl -X PATCH 'https://api.mystore.com/api/v3/store/carts/cart_xxx' \
 
 ## Countries
 
-Countries are the foundation of Spree's geographic system. They connect to [Markets](/developer/core-concepts/markets), contain states, and belong to zones.
+Countries are the foundation of Spree's geographic system. They connect to [Markets](markets.md), contain states, and belong to zones.
 
 Each country includes metadata that drives address form behavior:
 
@@ -170,7 +170,7 @@ Each country includes metadata that drives address form behavior:
 
 ### Which Countries Are Available?
 
-Only countries assigned to a [Market](/developer/core-concepts/markets) are available during checkout. This lets you control exactly where you sell.
+Only countries assigned to a [Market](markets.md) are available during checkout. This lets you control exactly where you sell.
 
 
 ```typescript SDK
@@ -229,7 +229,7 @@ For countries without predefined states, addresses accept a free-text `state_nam
 
 ## Zones
 
-Zones group countries or states together for [tax](/developer/core-concepts/taxes) and [shipping](/developer/core-concepts/shipments) rules. A zone is either **country-based** or **state-based**.
+Zones group countries or states together for [tax](taxes.md) and [shipping](shipments.md) rules. A zone is either **country-based** or **state-based**.
 
 **Examples:**
 - **EU VAT** (country zone) — Germany, France, Italy, Spain, ... → applies EU VAT rates
@@ -237,14 +237,14 @@ Zones group countries or states together for [tax](/developer/core-concepts/taxe
 - **Domestic Shipping** (country zone) — US, CA → enables domestic shipping methods
 
 When a customer enters their address at checkout, Spree matches it against zones to determine:
-1. Which **tax rates** apply (see [Taxes](/developer/core-concepts/taxes))
-2. Which **shipping methods** are available (see [Shipments](/developer/core-concepts/shipments))
+1. Which **tax rates** apply (see [Taxes](taxes.md))
+2. Which **shipping methods** are available (see [Shipments](shipments.md))
 
 Zones are configured in the admin dashboard — storefront developers don't interact with them directly via the API.
 
 ### Tax Zones and Markets
 
-Each [Market](/developer/core-concepts/markets) resolves a tax zone from its default country. This means product prices display the correct tax treatment (inclusive or exclusive) before the customer enters an address — just from knowing their market.
+Each [Market](markets.md) resolves a tax zone from its default country. This means product prices display the correct tax treatment (inclusive or exclusive) before the customer enters an address — just from knowing their market.
 
 ## How It All Fits Together
 
@@ -259,7 +259,7 @@ Here's how geography flows through a typical checkout:
 
 ## Related Documentation
 
-- [Markets](/developer/core-concepts/markets) — Multi-region commerce with currency, locale, and country grouping
-- [Taxes](/developer/core-concepts/taxes) — How zones and addresses affect taxation
-- [Shipments](/developer/core-concepts/shipments) — How zones and addresses affect shipping availability
-- [Orders](/developer/core-concepts/orders) — Order billing and shipping addresses
+- [Markets](markets.md) — Multi-region commerce with currency, locale, and country grouping
+- [Taxes](taxes.md) — How zones and addresses affect taxation
+- [Shipments](shipments.md) — How zones and addresses affect shipping availability
+- [Orders](orders.md) — Order billing and shipping addresses

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

@@ -5,7 +5,7 @@ description: How taxes, promotions, and other price modifications are applied to
 
 ## Overview
 
-An Adjustment modifies the price of an [Order](/developer/core-concepts/orders), a [Line Item](/developer/core-concepts/orders#line-items), or a [Shipment](/developer/core-concepts/shipments). Adjustments can be positive (charges) or negative (credits).
+An Adjustment modifies the price of an [Order](orders.md), a [Line Item](orders.md#line-items), or a [Shipment](shipments.md). Adjustments can be positive (charges) or negative (credits).
 
 ```mermaid
 erDiagram
@@ -31,7 +31,7 @@ erDiagram
 
 **Key relationships:**
 - **Adjustment** modifies prices on orders, line items, or shipments
-- **Source** is where the adjustment comes from ([Tax Rate](/developer/core-concepts/taxes) or [Promotion Action](/developer/core-concepts/promotions))
+- **Source** is where the adjustment comes from ([Tax Rate](taxes.md) or [Promotion Action](promotions.md))
 - **Adjustable** is what's being adjusted (Order, LineItem, or Shipment)
 - Positive amounts are charges, negative amounts are credits
 
@@ -48,8 +48,8 @@ Adjustments are created by two sources:
 
 | Source | Example | Typical Amount |
 |--------|---------|----------------|
-| [Tax Rate](/developer/core-concepts/taxes) | Sales tax, VAT | Positive (charge) |
-| [Promotion Action](/developer/core-concepts/promotions) | Coupon discount, free shipping | Negative (credit) |
+| [Tax Rate](taxes.md) | Sales tax, VAT | Positive (charge) |
+| [Promotion Action](promotions.md) | Coupon discount, free shipping | Negative (credit) |
 
 ## Adjustment Attributes
 
@@ -101,7 +101,7 @@ curl 'https://api.mystore.com/api/v3/store/orders/or_abc123?expand=items,shipmen
 
 ## Related Documentation
 
-- [Promotions](/developer/core-concepts/promotions) — Promotion-based adjustments
-- [Taxes](/developer/core-concepts/taxes) — Tax adjustments
-- [Shipments](/developer/core-concepts/shipments) — Shipping adjustments
-- [Orders](/developer/core-concepts/orders) — How adjustments affect order totals
+- [Promotions](promotions.md) — Promotion-based adjustments
+- [Taxes](taxes.md) — Tax adjustments
+- [Shipments](shipments.md) — Shipping adjustments
+- [Orders](orders.md) — How adjustments affect order totals

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

@@ -7,7 +7,7 @@ description: How Spree's core models, APIs, and packages work together
 
 Spree is a commerce engine built around interconnected models that represent the core concepts of commerce: products, orders, payments, and shipments. It adapts to your stack — use it as a headless API for any frontend, embed it into an existing application, or scale it from a single storefront to a global multi-vendor marketplace.
 
-> **INFO:** Spree supports PostgreSQL, MySQL, and SQLite. PostgreSQL is recommended for production. [Learn more about database configuration](/developer/deployment/database).
+> **INFO:** Spree supports PostgreSQL, MySQL, and SQLite. PostgreSQL is recommended for production. [Learn more about database configuration](../deployment/database.md).
 
 ## Core Commerce Flow
 
@@ -53,15 +53,15 @@ flowchart TB
 
 **How it works:**
 
-1. **Catalog** — [Products](/developer/core-concepts/products) have [Variants](/developer/core-concepts/products#variants) (SKUs) with prices and inventory tracked at [Stock Locations](/developer/core-concepts/inventory#stock-locations)
+1. **Catalog** — [Products](products.md) have [Variants](products.md#variants) (SKUs) with prices and inventory tracked at [Stock Locations](inventory.md#stock-locations)
 
-2. **Shopping** — Customers add Variants to their cart, creating an [Order](/developer/core-concepts/orders) with Line Items
+2. **Shopping** — Customers add Variants to their cart, creating an [Order](orders.md) with Line Items
 
-3. **Checkout** — The Order collects [Addresses](/developer/core-concepts/addresses), calculates [Shipping](/developer/core-concepts/shipments) options, and processes [Payments](/developer/core-concepts/payments)
+3. **Checkout** — The Order collects [Addresses](addresses.md), calculates [Shipping](shipments.md) options, and processes [Payments](payments.md)
 
-4. **Fulfillment** — [Shipments](/developer/core-concepts/shipments) are created from Stock Locations, tracking individual [Inventory Units](/developer/core-concepts/inventory#inventory-units)
+4. **Fulfillment** — [Shipments](shipments.md) are created from Stock Locations, tracking individual [Inventory Units](inventory.md#inventory-units)
 
-5. **Pricing & Adjustments** — [Taxes](/developer/core-concepts/taxes) and [Promotions](/developer/core-concepts/promotions) create [Adjustments](/developer/core-concepts/adjustments) that modify order totals
+5. **Pricing & Adjustments** — [Taxes](taxes.md) and [Promotions](promotions.md) create [Adjustments](adjustments.md) that modify order totals
 
 ## Core Model Relationships
 
@@ -110,16 +110,16 @@ Spree exposes two REST APIs, both under API v3:
 
 | API | Purpose | Authentication |
 |-----|---------|----------------|
-| [**Store API**](/api-reference/introduction) | Customer-facing — cart, checkout, products, account | Publishable API key + JWT |
+| [**Store API**](../../api-reference/introduction.md) | Customer-facing — cart, checkout, products, account | Publishable API key + JWT |
 | **Admin API** | Operational — manage products, orders, customers, settings | Secret API key |
 
-Both APIs use [prefixed IDs](/api-reference/introduction) (e.g., `prod_86Rf07xd4z`, `or_m3Rp9wXz`), flat JSON request/response structures, and full TypeScript types via the [@spree/sdk](/developer/sdk/quickstart).
+Both APIs use [prefixed IDs](../../api-reference/introduction.md) (e.g., `prod_86Rf07xd4z`, `or_m3Rp9wXz`), flat JSON request/response structures, and full TypeScript types via the [@spree/sdk](../sdk/quickstart.md).
 
-Events from both APIs can trigger [Webhooks](/developer/core-concepts/webhooks) to notify external systems in real time.
+Events from both APIs can trigger [Webhooks](webhooks.md) to notify external systems in real time.
 
 ## Multi-Store Architecture
 
-Spree supports [multiple stores](/developer/multi-store/quickstart) from a single installation. Each Store can have:
+Spree supports [multiple stores](../multi-store/quickstart.md) from a single installation. Each Store can have:
 
 - Its own domain and branding
 - Different currencies and locales
@@ -135,10 +135,10 @@ Spree is designed to be customized without modifying core code. The main extensi
 
 | Mechanism | Use Case | Documentation |
 |-----------|----------|---------------|
-| **Events & Subscribers** | React to order completion, payment, shipment events | [Events Guide](/developer/core-concepts/events) |
-| **Webhooks** | Notify external systems of changes | [Webhooks Guide](/developer/core-concepts/webhooks) |
-| **Dependencies** | Swap out services (tax calculation, shipping estimation) | [Dependencies Guide](/developer/customization/dependencies) |
-| **Decorators** | Modify existing model/controller behavior (use sparingly) | [Decorators Guide](/developer/customization/decorators) |
+| **Events & Subscribers** | React to order completion, payment, shipment events | [Events Guide](events.md) |
+| **Webhooks** | Notify external systems of changes | [Webhooks Guide](webhooks.md) |
+| **Dependencies** | Swap out services (tax calculation, shipping estimation) | [Dependencies Guide](../customization/dependencies.md) |
+| **Decorators** | Modify existing model/controller behavior (use sparingly) | [Decorators Guide](../customization/decorators.md) |
 
 > **INFO:** For most customizations, prefer **Events** and **Dependencies** over Decorators. They're easier to maintain and won't break during upgrades.
 
@@ -163,15 +163,15 @@ Spree is distributed as a set of packages:
 
 | Package | Purpose |
 |---------|---------|
-| [`@spree/sdk`](/developer/sdk/quickstart) | TypeScript SDK for Store API and Admin API |
-| [`@spree/next`](/developer/storefront/nextjs/spree-next-package) | Next.js integration — server actions, caching, cookie-based auth |
+| [`@spree/sdk`](../sdk/quickstart.md) | TypeScript SDK for Store API and Admin API |
+| [`@spree/next`](../storefront/nextjs/spree-next-package.md) | Next.js integration — server actions, caching, cookie-based auth |
 
 > **INFO:** For headless commerce, you only need the `spree` package. Build your customer-facing frontend with any technology (Next.js, Nuxt, mobile apps) using the Store API and SDK.
 
 ## Related Documentation
 
-- [Products](/developer/core-concepts/products) — Product catalog and variants
-- [Orders](/developer/core-concepts/orders) — Order lifecycle and state machine
-- [Payments](/developer/core-concepts/payments) — Payment processing
-- [Shipments](/developer/core-concepts/shipments) — Shipping and fulfillment
-- [Customization Quickstart](/developer/customization/quickstart) — How to extend Spree
+- [Products](products.md) — Product catalog and variants
+- [Orders](orders.md) — Order lifecycle and state machine
+- [Payments](payments.md) — Payment processing
+- [Shipments](shipments.md) — Shipping and fulfillment
+- [Customization Quickstart](../customization/quickstart.md) — How to extend Spree

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

@@ -44,9 +44,9 @@ erDiagram
 
 **Key relationships:**
 - **Calculator** computes amounts for various features
-- Used by **[Tax Rates](/developer/core-concepts/taxes)** to calculate tax amounts
-- Used by **[Shipping Methods](/developer/core-concepts/shipments)** to calculate shipping costs
-- Used by **[Promotion Actions](/developer/core-concepts/promotions)** to calculate discounts
+- Used by **[Tax Rates](taxes.md)** to calculate tax amounts
+- Used by **[Shipping Methods](shipments.md)** to calculate shipping costs
+- Used by **[Promotion Actions](promotions.md)** to calculate discounts
 - Calculators store preferences (rates, percentages, etc.) for their calculations
 
 Spree makes extensive use of the `Spree::Calculator` model and there are several subclasses provided to deal with various types of calculations flat rate, percentage discount, sales tax, VAT, etc. All calculators extend the `Spree::Calculator` class and must provide the following methods:
@@ -69,7 +69,7 @@ The following are descriptions of the currently available calculators in Spree.
 
 ### Default Tax
 
-For information about this calculator, please read the [Taxes](/developer/core-concepts/taxes) guide.
+For information about this calculator, please read the [Taxes](taxes.md) guide.
 
 ### Flat Percent Per Item Total
 

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

@@ -137,9 +137,9 @@ curl -X POST 'https://api.mystore.com/api/v3/store/customer/password_resets' \
 ```
 
 
-The optional `redirect_url` parameter specifies where the password reset link in the email should point to. The token will be appended as a query parameter (e.g., `https://myshop.com/reset-password?token=...`). If the store has [Allowed Origins](/developer/core-concepts/allowed-origins) configured, the `redirect_url` must match one of them.
+The optional `redirect_url` parameter specifies where the password reset link in the email should point to. The token will be appended as a query parameter (e.g., `https://myshop.com/reset-password?token=...`). If the store has [Allowed Origins](allowed-origins.md) configured, the `redirect_url` must match one of them.
 
-This fires a `customer.password_reset_requested` event with the reset token in the payload. If you're using the `spree_emails` package, the email is sent automatically. Otherwise, subscribe to this event to send the reset email yourself (see [Events](/developer/core-concepts/events)).
+This fires a `customer.password_reset_requested` event with the reset token in the payload. If you're using the `spree_emails` package, the email is sent automatically. Otherwise, subscribe to this event to send the reset email yourself (see [Events](events.md)).
 
 ### Step 2: Reset Password
 
@@ -210,8 +210,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 |
@@ -220,11 +220,11 @@ 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.
 
 ## 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
-- [Staff & Roles](/developer/core-concepts/staff-roles) — Admin users and permissions
+- [Addresses](addresses.md) — Customer address management
+- [Orders](orders.md) — Order history and checkout
+- [Authentication](../customization/authentication.md) — Custom authentication setup
+- [Staff & Roles](staff-roles.md) — Admin users and permissions

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

@@ -279,7 +279,7 @@ Spree::Events.publish(
 
 ## Event Serializers
 
-Event payloads are generated using the same [Store API V3 serializers](/api-reference/introduction) used by the REST API. This means webhook payloads and API responses share the same schema, making it easy to reuse types in your integrations.
+Event payloads are generated using the same [Store API V3 serializers](../../api-reference/introduction.md) used by the REST API. This means webhook payloads and API responses share the same schema, making it easy to reuse types in your integrations.
 
 ### How Serializers Work
 
@@ -618,7 +618,7 @@ The base class also provides helper methods:
 
 ## Related Documentation
 
-- [Webhooks](/developer/core-concepts/webhooks) - HTTP callbacks for external integrations
-- [Customization Quickstart](/developer/customization/quickstart) - Overview of all customization options
-- [Decorators](/developer/customization/decorators) - When to use decorators vs events
-- [Checkout Flow](/developer/customization/checkout) - Using events in checkout customization
+- [Webhooks](webhooks.md) - HTTP callbacks for external integrations
+- [Customization Quickstart](../customization/quickstart.md) - Overview of all customization options
+- [Decorators](../customization/decorators.md) - When to use decorators vs events
+- [Checkout Flow](../customization/checkout.md) - Using events in checkout customization

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

@@ -5,7 +5,7 @@ description: Stock locations, stock items, stock movements, and inventory tracki
 
 ## Overview
 
-Each [Variant](/developer/core-concepts/products#variants) has a `StockItem` that tracks its inventory at a specific location. A variant can have multiple stock items if it's available at multiple stock locations.
+Each [Variant](products.md#variants) has a `StockItem` that tracks its inventory at a specific location. A variant can have multiple stock items if it's available at multiple stock locations.
 
 When products are sold or returned, individual `InventoryUnit` records track each unit through the fulfillment process.
 
@@ -68,7 +68,7 @@ erDiagram
 - **Stock Item** → Tracks quantity (`count_on_hand`) for a specific Variant at a specific Stock Location
 - **Stock Movement** → Records changes to Stock Item quantities (purchases, returns, transfers)
 - **Stock Transfer** → Moves inventory between Stock Locations, creating Stock Movements at source and destination
-- **Inventory Unit** → Represents individual units in [Orders](/developer/core-concepts/orders) and [Shipments](/developer/core-concepts/shipments)
+- **Inventory Unit** → Represents individual units in [Orders](orders.md) and [Shipments](shipments.md)
 
 ## Inventory Management
 
@@ -186,6 +186,6 @@ If you don't need to track inventory, you can disable it:
 
 ## Related Documentation
 
-- [Products](/developer/core-concepts/products) - Product and variant management
-- [Shipments](/developer/core-concepts/shipments) - How inventory relates to shipments
-- [Orders](/developer/core-concepts/orders) - How inventory is allocated to orders
+- [Products](products.md) - Product and variant management
+- [Shipments](shipments.md) - How inventory relates to shipments
+- [Orders](orders.md) - How inventory is allocated to orders

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

@@ -5,7 +5,7 @@ description: Multi-region commerce with Markets — bundle geography, currency,
 
 ## Overview
 
-Markets let you segment a single [Store](/developer/core-concepts/stores) into distinct geographic regions, each with its own currency, locale, and set of countries. For example, an international store might define:
+Markets let you segment a single [Store](stores.md) into distinct geographic regions, each with its own currency, locale, and set of countries. For example, an international store might define:
 
 - **North America** — USD, English, ships to US and Canada
 - **Europe** — EUR, German, ships to DE, FR, AT, NL
@@ -193,7 +193,7 @@ curl 'https://api.mystore.com/api/v3/store/locales' \
 ```
 
 
-See [Localization](/api-reference/store-api/localization) for details on how to pass locale, currency, and country headers in API requests.
+See [Localization](../../api-reference/store-api/localization.md) for details on how to pass locale, currency, and country headers in API requests.
 
 ## Tax Behavior
 
@@ -204,15 +204,15 @@ The `tax_inclusive` flag on a market controls how prices are displayed and calcu
 
 Each market also resolves a **tax zone** from its default country. This zone determines which tax rates apply when browsing products — before the customer enters a shipping address. Once the customer provides an address at checkout, the actual shipping address takes over for tax calculation.
 
-See [Taxes](/developer/core-concepts/taxes) for details on tax zones and rates.
+See [Taxes](taxes.md) for details on tax zones and rates.
 
 ## Pricing Integration
 
-Markets integrate with the [Pricing](/developer/core-concepts/pricing) system, enabling market-specific pricing through **Price Lists** with a **Market Rule**. This lets you set different prices for the same product in different markets — beyond just currency conversion.
+Markets integrate with the [Pricing](pricing.md) system, enabling market-specific pricing through **Price Lists** with a **Market Rule**. This lets you set different prices for the same product in different markets — beyond just currency conversion.
 
 For example, you could price a product at $29.99 in North America and €24.99 in Europe, rather than relying on exchange rate conversion.
 
-See [Pricing — Price Rules](/developer/core-concepts/pricing#price-rules) for details on configuring market-specific price lists.
+See [Pricing — Price Rules](pricing.md#price-rules) for details on configuring market-specific price lists.
 
 ## Setting Up Markets
 
@@ -243,8 +243,8 @@ current_store.markets.create!(
 
 ## Related Documentation
 
-- [Stores](/developer/core-concepts/stores) — Multi-store setup and configuration
-- [Pricing](/developer/core-concepts/pricing) — Price Lists, Price Rules, and the Pricing Context
-- [Addresses](/developer/core-concepts/addresses) — Countries, States, and Zones
-- [Localization](/api-reference/store-api/localization) — Locale, currency, and country headers in API requests
-- [Translations](/developer/core-concepts/translations) — Resource and UI translations
+- [Stores](stores.md) — Multi-store setup and configuration
+- [Pricing](pricing.md) — Price Lists, Price Rules, and the Pricing Context
+- [Addresses](addresses.md) — Countries, States, and Zones
+- [Localization](../../api-reference/store-api/localization.md) — Locale, currency, and country headers in API requests
+- [Translations](translations.md) — Resource and UI translations

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

@@ -152,7 +152,7 @@ Spree supports two storage service types:
 | Public storage | Product images, logos, taxon images | S3 public bucket, CDN |
 | Private storage | CSV exports, digital downloads | S3 private bucket |
 
-> **INFO:** For production deployments, use cloud storage (S3, GCS, Azure) instead of local disk storage. See [Asset Deployment](/developer/deployment/assets) for configuration details.
+> **INFO:** For production deployments, use cloud storage (S3, GCS, Azure) instead of local disk storage. See [Asset Deployment](../deployment/assets.md) for configuration details.
 
 ## Best Practices
 
@@ -163,5 +163,5 @@ Spree supports two storage service types:
 
 ## Related Documentation
 
-- [Products](/developer/core-concepts/products) — Product catalog and media
-- [Deployment — Assets](/developer/deployment/assets) — Storage and CDN configuration
+- [Products](products.md) — Product catalog and media
+- [Deployment — Assets](../deployment/assets.md) — Storage and CDN configuration

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

@@ -5,7 +5,7 @@ description: Add custom structured data to products, orders, and other resources
 
 ## Overview
 
-Metafields provide a flexible, type-safe system for adding custom structured data to Spree resources. Unlike [metadata](/developer/customization/metadata) which is simple JSON storage, metafields are schema-defined with strong typing, validation, and visibility controls.
+Metafields provide a flexible, type-safe system for adding custom structured data to Spree resources. Unlike [metadata](../customization/metadata.md) which is simple JSON storage, metafields are schema-defined with strong typing, validation, and visibility controls.
 
 Use metafields for:
 
@@ -87,7 +87,7 @@ Metafields support three visibility levels via the `display_on` attribute:
 
 Metafields can be attached to most Spree resources including Products, Variants, Orders, Line Items, Taxons, Payments, Shipments, Gift Cards, Store Credits, and more.
 
-> **INFO:** Custom resources can also support metafields. See the [Customization Quickstart](/developer/customization/quickstart) for details.
+> **INFO:** Custom resources can also support metafields. See the [Customization Quickstart](../customization/quickstart.md) for details.
 
 ## Namespaces
 
@@ -178,10 +178,10 @@ When editing a resource (e.g., a product), metafields appear in a dedicated sect
 
 **Use Metadata** for external system IDs, tracking attribution, or simple write-and-forget data.
 
-> **WARNING:** Product Properties are deprecated and will be removed in Spree 6.0. For new projects, always use Metafields. For existing projects, plan to migrate using the [migration guide](/developer/upgrades/5.1-to-5.2#3-migrate-to-metafields-or-keep-using-properties).
+> **WARNING:** Product Properties are deprecated and will be removed in Spree 6.0. For new projects, always use Metafields. For existing projects, plan to migrate using the [migration guide](../upgrades/5.1-to-5.2.md#3-migrate-to-metafields-or-keep-using-properties).
 
 ## Related Documentation
 
-- [Metadata](/developer/customization/metadata) — Simple key-value metadata
-- [Products](/developer/core-concepts/products) — Product catalog
-- [Events](/developer/core-concepts/events) — Subscribe to metafield events
+- [Metadata](../customization/metadata.md) — Simple key-value metadata
+- [Products](products.md) — Product catalog
+- [Events](events.md) — Subscribe to metafield events

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

@@ -49,11 +49,11 @@ erDiagram
 ```
 
 **Key relationships:**
-- **Line Items** link orders to [Variants](/developer/core-concepts/products#variants) (what was purchased)
-- **[Shipments](/developer/core-concepts/shipments)** handle fulfillment from stock locations
-- **[Payments](/developer/core-concepts/payments)** track payment attempts and their states
-- **[Adjustments](/developer/core-concepts/adjustments)** apply taxes, promotions, and shipping costs
-- **[Addresses](/developer/core-concepts/addresses)** store billing and shipping information
+- **Line Items** link orders to [Variants](products.md#variants) (what was purchased)
+- **[Shipments](shipments.md)** handle fulfillment from stock locations
+- **[Payments](payments.md)** track payment attempts and their states
+- **[Adjustments](adjustments.md)** apply taxes, promotions, and shipping costs
+- **[Addresses](addresses.md)** store billing and shipping information
 
 ## Order Attributes
 
@@ -288,13 +288,13 @@ curl 'https://api.mystore.com/api/v3/store/orders/or_xxx?expand=items,shipments,
 
 ## Line Items
 
-Line items represent individual products in an order. Each line item links to a [Variant](/developer/core-concepts/products#variants) and tracks the quantity and price at the time of purchase.
+Line items represent individual products in an order. Each line item links to a [Variant](products.md#variants) and tracks the quantity and price at the time of purchase.
 
 When a variant is added to an order, the price is locked on the line item. If the variant's price changes later, existing orders are unaffected.
 
 ## Adjustments
 
-[Adjustments](/developer/core-concepts/adjustments) modify an order's total — promotions decrease it, taxes and shipping increase it. Adjustments can be applied at the order level, the line item level, or the shipment level.
+[Adjustments](adjustments.md) modify an order's total — promotions decrease it, taxes and shipping increase it. Adjustments can be applied at the order level, the line item level, or the shipment level.
 
 ## Payment States
 
@@ -316,13 +316,13 @@ When a variant is added to an order, the price is locked on the line item. If th
 | `shipped` | All shipments have been shipped |
 | `backorder` | Some inventory is on backorder |
 
-For more details, see [Shipments](/developer/core-concepts/shipments) and [Payments](/developer/core-concepts/payments).
+For more details, see [Shipments](shipments.md) and [Payments](payments.md).
 
 ## Related Documentation
 
-- [Payments](/developer/core-concepts/payments) — Payment processing and payment sessions
-- [Shipments](/developer/core-concepts/shipments) — Fulfillment and shipping rates
-- [Addresses](/developer/core-concepts/addresses) — Billing and shipping addresses
-- [Promotions](/developer/core-concepts/promotions) — Discounts and coupon codes
-- [Checkout Customization](/developer/customization/checkout) — Customizing the checkout flow
-- [Events](/developer/core-concepts/events) — Subscribe to order events (e.g., `order.completed`)
+- [Payments](payments.md) — Payment processing and payment sessions
+- [Shipments](shipments.md) — Fulfillment and shipping rates
+- [Addresses](addresses.md) — Billing and shipping addresses
+- [Promotions](promotions.md) — Discounts and coupon codes
+- [Checkout Customization](../customization/checkout.md) — Customizing the checkout flow
+- [Events](events.md) — Subscribe to order events (e.g., `order.completed`)

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

@@ -107,7 +107,7 @@ erDiagram
 ```
 
 **Key relationships:**
-- **Payment** tracks each payment attempt against an [Order](/developer/core-concepts/orders)
+- **Payment** tracks each payment attempt against an [Order](orders.md)
 - **Payment Method** defines how payments are processed (Stripe, Adyen, PayPal, Check, etc.)
 - **Payment Session** manages the gateway-side payment lifecycle (e.g., Stripe PaymentIntent, Adyen Session)
 - **Payment Setup Session** manages saving payment methods for future use without an immediate charge (e.g., Stripe SetupIntent)
@@ -652,11 +652,11 @@ Spree will verify the result with the provider and create a saved payment source
 
 Spree team maintains several payment gateway integrations. All of these gateways are **fully PCI compliant**, using native gateway SDKs, meaning no sensitive payment data is stored or processed through Spree.
 
-- [Stripe](/integrations/payments/stripe) — Stripe integration, supports all Stripe payment methods, including credit cards, bank transfers, Apple Pay, Google Pay, Klarna, Afterpay, and more. Also supports quick checkout.
+- [Stripe](../../integrations/payments/stripe.md) — Stripe integration, supports all Stripe payment methods, including credit cards, bank transfers, Apple Pay, Google Pay, Klarna, Afterpay, and more. Also supports quick checkout.
 
-- [Adyen](/integrations/payments/adyen) — Adyen integration, supports all Adyen payment methods, including credit cards, bank transfers, Apple Pay, Google Pay, Klarna, and more.
+- [Adyen](../../integrations/payments/adyen.md) — Adyen integration, supports all Adyen payment methods, including credit cards, bank transfers, Apple Pay, Google Pay, Klarna, and more.
 
-- [PayPal](/integrations/payments/paypal) — Native PayPal integration, supports PayPal, PayPal Credit, and PayPal Pay Later.
+- [PayPal](../../integrations/payments/paypal.md) — Native PayPal integration, supports PayPal, PayPal Credit, and PayPal Pay Later.
 
 ## Payment Events
 
@@ -684,14 +684,14 @@ Spree publishes events throughout the payment lifecycle that you can subscribe t
 | `payment_setup_session.failed` | Setup failed |
 | `payment_setup_session.canceled` | Setup was canceled |
 
-See [Events](/developer/core-concepts/events) for more details on subscribing to events.
+See [Events](events.md) for more details on subscribing to events.
 
 ## Related Documentation
 
-- [Build a Custom Payment Method](/developer/how-to/custom-payment-method) - Step-by-step guide to creating your own payment gateway integration
-- [Orders](/developer/core-concepts/orders) - Order management and state machine
-- [Checkout Customization](/developer/customization/checkout) - Customizing the checkout flow
-- [Events](/developer/core-concepts/events) - Subscribe to payment events
+- [Build a Custom Payment Method](../how-to/custom-payment-method.md) - Step-by-step guide to creating your own payment gateway integration
+- [Orders](orders.md) - Order management and state machine
+- [Checkout Customization](../customization/checkout.md) - Customizing the checkout flow
+- [Events](events.md) - Subscribe to payment events
 
 ## Key Services
 

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

@@ -5,11 +5,11 @@ description: Prices, Price Lists, Price Rules, and the Pricing Context — Spree
 
 ## Overview
 
-Spree's pricing system supports both simple single-currency pricing and advanced multi-currency, rule-based pricing through Price Lists. Every [Variant](/developer/core-concepts/products#variants) can have multiple prices — a base price per currency, plus additional prices from Price Lists that apply conditionally based on rules like geography, customer segment, or quantity.
+Spree's pricing system supports both simple single-currency pricing and advanced multi-currency, rule-based pricing through Price Lists. Every [Variant](products.md#variants) can have multiple prices — a base price per currency, plus additional prices from Price Lists that apply conditionally based on rules like geography, customer segment, or quantity.
 
 ## Prices
 
-Each variant has one or more `Price` records — one per currency. The API automatically returns the correct price based on the current currency and [Market](/developer/core-concepts/markets) context.
+Each variant has one or more `Price` records — one per currency. The API automatically returns the correct price based on the current currency and [Market](markets.md) context.
 
 | Attribute | Description | Example |
 |-----------|-------------|---------|
@@ -55,7 +55,7 @@ curl 'https://api.mystore.com/api/v3/store/products/spree-tote?expand=variants'
 
 Price Lists allow you to create different pricing strategies based on various conditions. This enables advanced pricing scenarios like:
 
-- **Market-based pricing** — different prices for different [Markets](/developer/core-concepts/markets) (e.g., North America vs Europe)
+- **Market-based pricing** — different prices for different [Markets](markets.md) (e.g., North America vs Europe)
 - **Regional pricing** — different prices for different geographic zones
 - **Wholesale/B2B pricing** — special prices for business customers
 - **Volume discounts** — tiered pricing based on quantity purchased
@@ -90,7 +90,7 @@ Price Rules define conditions that must be met for a Price List to apply. Spree
 
 | Rule | Description | Use Case |
 |------|-------------|----------|
-| **Market Rule** | Matches based on the current [Market](/developer/core-concepts/markets) | Regional pricing across markets |
+| **Market Rule** | Matches based on the current [Market](markets.md) | Regional pricing across markets |
 | **Zone Rule** | Matches based on the customer's geographic zone | Country or state-level pricing |
 | **User Rule** | Matches specific customer accounts | VIP customers, wholesale accounts |
 | **Customer Group Rule** | Matches members of customer groups | Loyalty tiers, membership pricing |
@@ -124,7 +124,7 @@ Applies based on quantity purchased. Supports `min_quantity` and `max_quantity`
 | Bulk Tier 1 | 10–49 | $8.50 |
 | Bulk Tier 2 | 50+ | $7.00 |
 
-> **INFO:** Custom Price Rules can be created for specialized pricing logic. See the [Customization Quickstart](/developer/customization/quickstart) for details.
+> **INFO:** Custom Price Rules can be created for specialized pricing logic. See the [Customization Quickstart](../customization/quickstart.md) for details.
 
 ## Pricing Context
 
@@ -133,7 +133,7 @@ When resolving prices, Spree considers the full context of the request:
 | Context | Source | Description |
 |---------|--------|-------------|
 | Currency | Market or request header | The currency to price in |
-| Market | Customer's country | The [Market](/developer/core-concepts/markets) for market-based rules |
+| Market | Customer's country | The [Market](markets.md) for market-based rules |
 | Zone | Customer's address | The geographic zone for zone-based rules |
 | Customer | JWT authentication | The logged-in customer for user-based rules |
 | Quantity | Cart line item | The quantity for volume-based rules |
@@ -157,7 +157,7 @@ Each Price List contains prices for specific variants and currencies. Products c
 
 ## Related Documentation
 
-- [Products](/developer/core-concepts/products) — Products, Variants, and base prices
-- [Markets](/developer/core-concepts/markets) — Geographic regions with currency and locale
-- [Taxes](/developer/core-concepts/taxes) — Tax categories, tax rates, and zones
-- [Promotions](/developer/core-concepts/promotions) — Discount-based pricing via promotion rules
+- [Products](products.md) — Products, Variants, and base prices
+- [Markets](markets.md) — Geographic regions with currency and locale
+- [Taxes](taxes.md) — Tax categories, tax rates, and zones
+- [Promotions](promotions.md) — Discount-based pricing via promotion rules