@spree/docs 0.1.0 → 0.1.2

package/dist/developer/customization/checkout.md

@@ -40,7 +40,7 @@ If you want a list of all the currently available states for the checkout, use t
 
 ## Default Checkout Steps
 
-The Spree checkout process consists of the following steps. With the exception of the Registration step, each of these steps corresponds to a state of the [Order object](/developer/core-concepts/orders):
+The Spree checkout process consists of the following steps. With the exception of the Registration step, each of these steps corresponds to a state of the [Order object](../core-concepts/orders.md):
 
 * Shipping Address and Contact Information
 * Delivery Options Shipping Method
@@ -55,7 +55,7 @@ This step allows the customer to add shipping information and contact informatio
 
 The address fields include a select box for choosing state/province. If there are no states configured for a particular country, the select box will be replaced by a text field instead.
 
-The list of countries that appear in the country select box can also be configured. Spree will list all countries by default, but you can configure exactly which countries you would like to appear. The list can be limited to a specific set of countries by [setting the Store's checkout zone](/developer/core-concepts/stores#checkout-configuration).
+The list of countries that appear in the country select box can also be configured. Spree will list all countries by default, but you can configure exactly which countries you would like to appear. The list can be limited to a specific set of countries by [setting the Store's checkout zone](../core-concepts/stores.md#checkout-configuration).
 
 ### Delivery Options
 
@@ -67,7 +67,7 @@ This step is where the customer provides payment and billing information. Spree
 
 Besides Credit Card, Wallets and other 3rd party payment methods, Spree also supports Store Credit and Gift Cards (Spree 5.1+ only) which can be used to pay for the entire order or part of the order.
 
-For more information about payments, please see the [Payments guide](/developer/core-concepts/payments).
+For more information about payments, please see the [Payments guide](../core-concepts/payments.md).
 
 ### Confirmation
 
@@ -81,7 +81,7 @@ This step is disabled by default, but can be enabled by two ways:
     Spree::Config[:always_include_confirm_step] = true
     ```
 
-2. conditionally for specific orders by overriding the `confirmation_required?` method in `Spree::Order` with a [decorator](/developer/customization/decorators), eg.
+2. conditionally for specific orders by overriding the `confirmation_required?` method in `Spree::Order` with a [decorator](decorators.md), eg.
 
     ```ruby app/models/spree/order_decorator.rb
     module Spree
@@ -100,7 +100,7 @@ There are two approaches for adding logic around checkout state transitions:
 
 ### Approach 1: Events Subscribers (Recommended for side effects)
 
-For actions that should happen **after** a checkout step completes (syncing with external services, sending notifications, logging, etc.), use [Events subscribers](/developer/core-concepts/events). This is the recommended approach because it keeps your code decoupled from Spree internals.
+For actions that should happen **after** a checkout step completes (syncing with external services, sending notifications, logging, etc.), use [Events subscribers](../core-concepts/events.md). This is the recommended approach because it keeps your code decoupled from Spree internals.
 
 ```ruby app/subscribers/my_app/order_completed_subscriber.rb
 module MyApp
@@ -119,7 +119,7 @@ module MyApp
 end
 ```
 
-> **INFO:** Events are fired automatically when orders change state. See [Events documentation](/developer/core-concepts/events#order-events) for all available order events.
+> **INFO:** Events are fired automatically when orders change state. See [Events documentation](../core-concepts/events.md#order-events) for all available order events.
 
 ### Approach 2: State Machine Callbacks (For validation/blocking logic)
 
@@ -146,7 +146,7 @@ end
 
 This callback would prevent transitioning to the `delivery` step if `valid_zip_code?` returns false.
 
-> **WARNING:** Avoid using state machine callbacks for side effects like API calls or notifications. These can slow down checkout and may fail silently. Use [Events subscribers](/developer/core-concepts/events) instead.
+> **WARNING:** Avoid using state machine callbacks for side effects like API calls or notifications. These can slow down checkout and may fail silently. Use [Events subscribers](../core-concepts/events.md) instead.
 
 ## Modifying the checkout flow
 

package/dist/developer/customization/decorators.md

@@ -5,13 +5,13 @@ description: Decorators allow you to add or modify behavior of Spree classes in
 
 > **WARNING:** **Decorators should be a last resort.** They tightly couple your code to Spree internals and can break during upgrades. Before using decorators, consider these modern alternatives that are safer and easier to maintain:
 > 
->   - **[Events & Subscribers](/developer/core-concepts/events)** - For reacting to model changes (after save, create, update, delete)
->   - **[Webhooks](/developer/core-concepts/webhooks)** - For notifying external services when events occur
->   - **[Dependencies](/developer/customization/dependencies)** - For swapping out services, serializers, and abilities
->   - **[Admin Navigation](/developer/admin/navigation)** - For adding menu items without controller decorators
->   - **[Admin Partials](/developer/admin/extending-ui)** - For extending admin UI without view decorators
->   - **[Admin Tables](/developer/admin/tables)** - For customizing admin list views
->   - **[Ransack Configuration](/developer/core-concepts/search-filtering#extending-ransackable-configuration)** - For adding searchable/sortable fields without model decorators
+>   - **[Events & Subscribers](../core-concepts/events.md)** - For reacting to model changes (after save, create, update, delete)
+>   - **[Webhooks](../core-concepts/webhooks.md)** - For notifying external services when events occur
+>   - **[Dependencies](dependencies.md)** - For swapping out services, serializers, and abilities
+>   - **[Admin Navigation](../admin/navigation.md)** - For adding menu items without controller decorators
+>   - **[Admin Partials](../admin/extending-ui.md)** - For extending admin UI without view decorators
+>   - **[Admin Tables](../admin/tables.md)** - For customizing admin list views
+>   - **[Ransack Configuration](../core-concepts/search-filtering.md#extending-ransackable-configuration)** - For adding searchable/sortable fields without model decorators
 
 ## When to Use Decorators vs Modern Alternatives
 
@@ -19,13 +19,13 @@ Before reaching for a decorator, check if your use case is better served by a mo
 
 | Use Case | Instead of Decorator | Use This |
 |----------|---------------------|----------|
-| After-save hooks (sync to external service) | Model decorator with `after_save` | [Events subscriber](/developer/core-concepts/events) |
-| Notify external service on changes | Model decorator with callbacks | [Webhooks](/developer/core-concepts/webhooks) |
-| Custom add-to-cart logic | Service decorator | [Dependencies injection](/developer/customization/dependencies) |
-| Custom API responses | Serializer decorator | [Dependencies injection](/developer/customization/dependencies) |
-| Add admin menu item | Controller decorator | [Admin Navigation API](/developer/admin/navigation) |
-| Add section to admin form | View decorator/override | [Admin Partials injection](/developer/admin/extending-ui) |
-| Add searchable/filterable field | Model decorator with `ransackable_attributes` | [Ransack configuration](/developer/core-concepts/search-filtering#extending-ransackable-configuration) |
+| After-save hooks (sync to external service) | Model decorator with `after_save` | [Events subscriber](../core-concepts/events.md) |
+| Notify external service on changes | Model decorator with callbacks | [Webhooks](../core-concepts/webhooks.md) |
+| Custom add-to-cart logic | Service decorator | [Dependencies injection](dependencies.md) |
+| Custom API responses | Serializer decorator | [Dependencies injection](dependencies.md) |
+| Add admin menu item | Controller decorator | [Admin Navigation API](../admin/navigation.md) |
+| Add section to admin form | View decorator/override | [Admin Partials injection](../admin/extending-ui.md) |
+| Add searchable/filterable field | Model decorator with `ransackable_attributes` | [Ransack configuration](../core-concepts/search-filtering.md#extending-ransackable-configuration) |
 | Add association to core model | - | Decorator (still appropriate) |
 | Add validation to core model | - | Decorator (still appropriate) |
 | Add new method to core model | - | Decorator (still appropriate) |
@@ -316,7 +316,7 @@ end
 
 ### Modifying Existing Actions
 
-> **WARNING:** **High risk of breaking during upgrades.** When you override an existing Spree action, your code depends on Spree's internal implementation details. If Spree changes the action's behavior, instance variables, or method signatures in a future version, your decorator may silently break or cause unexpected bugs. Use [Events](/developer/core-concepts/events) for post-action side effects instead.
+> **WARNING:** **High risk of breaking during upgrades.** When you override an existing Spree action, your code depends on Spree's internal implementation details. If Spree changes the action's behavior, instance variables, or method signatures in a future version, your decorator may silently break or cause unexpected bugs. Use [Events](../core-concepts/events.md) for post-action side effects instead.
 
 ```ruby app/controllers/spree/admin/products_controller_decorator.rb
 module Spree
@@ -349,7 +349,7 @@ module Spree
 end
 ```
 
-> **INFO:** **Better alternative:** For post-action side effects like notifications, use [Events subscribers](/developer/core-concepts/events) instead. Subscribe to `product.created` to be notified when products are created, without coupling to controller internals.
+> **INFO:** **Better alternative:** For post-action side effects like notifications, use [Events subscribers](../core-concepts/events.md) instead. Subscribe to `product.created` to be notified when products are created, without coupling to controller internals.
 
 ### Adding Before Actions
 
@@ -513,11 +513,11 @@ end
 
 ## Related Documentation
 
-- [Events](/developer/core-concepts/events) - Learn about Spree's event system
-- [Webhooks](/developer/core-concepts/webhooks) - HTTP callbacks for external integrations
-- [Dependencies](/developer/customization/dependencies) - Swap core services with your own
-- [Admin Navigation](/developer/admin/navigation) - Extend admin menu without decorators
-- [Admin Partials](/developer/admin/extending-ui) - Extend admin UI without view decorators
-- [Extending Core Models Tutorial](/developer/tutorial/extending-models) - Step-by-step guide to connecting custom models with Spree core
-- [Customization Overview](/developer/customization/quickstart) - General customization patterns
-- [Logic Customization](/developer/customization/logic) - Customizing business logic
+- [Events](../core-concepts/events.md) - Learn about Spree's event system
+- [Webhooks](../core-concepts/webhooks.md) - HTTP callbacks for external integrations
+- [Dependencies](dependencies.md) - Swap core services with your own
+- [Admin Navigation](../admin/navigation.md) - Extend admin menu without decorators
+- [Admin Partials](../admin/extending-ui.md) - Extend admin UI without view decorators
+- [Extending Core Models Tutorial](../tutorial/extending-models.md) - Step-by-step guide to connecting custom models with Spree core
+- [Customization Overview](quickstart.md) - General customization patterns
+- [Logic Customization](logic.md) - Customizing business logic

package/dist/developer/customization/dependencies.md

@@ -73,7 +73,7 @@ Spree.api.storefront_cart_serializer.new(order).serializable_hash
 
 ## Controller level customization
 
-If you need to replace [serializers](https://github.com/jsonapi-serializer/jsonapi-serializer) or Services in a specific API endpoint you can create a [code decorator](/developer/customization/decorators):
+If you need to replace [serializers](https://github.com/jsonapi-serializer/jsonapi-serializer) or Services in a specific API endpoint you can create a [code decorator](decorators.md):
 
 ```bash
 mkdir -p app/controllers/spree && touch app/controllers/spree/cart_controller_decorator.rb

package/dist/developer/customization/metadata.md

@@ -8,7 +8,7 @@ Metadata provides simple, unstructured key-value storage on Spree resources —
 
 Metadata is **write-only** in the Store API — you can set it when creating or updating resources, but it is never returned in Store API responses. It is visible in Admin API responses for administrative use.
 
-> **INFO:** For structured, type-safe custom attributes with admin UI support, use [Metafields](/developer/core-concepts/metafields) instead.
+> **INFO:** For structured, type-safe custom attributes with admin UI support, use [Metafields](../core-concepts/metafields.md) instead.
 
 ## Store API
 
@@ -188,7 +188,7 @@ Metadata updates use **merge semantics** — existing keys are preserved, new ke
 
 ## Metadata vs Metafields
 
-| | Metadata | [Metafields](/developer/core-concepts/metafields) |
+| | Metadata | [Metafields](../core-concepts/metafields.md) |
 |---|---|---|
 | **Use case** | Integration data, tracking, simple key-value | Structured custom attributes with admin UI |
 | **Validation** | None | Type-specific (text, number, boolean, JSON) |
@@ -222,7 +222,7 @@ The Store API currently supports writing metadata on:
 
 ## Migration from public_metadata
 
-The `public_metadata` column is deprecated. Metadata is no longer returned in Store API responses. If you were using `public_metadata` for data that needs to be visible to customers, migrate to [Metafields](/developer/core-concepts/metafields) with `display_on: 'both'`.
+The `public_metadata` column is deprecated. Metadata is no longer returned in Store API responses. If you were using `public_metadata` for data that needs to be visible to customers, migrate to [Metafields](../core-concepts/metafields.md) with `display_on: 'both'`.
 
 ```ruby
 # Before (deprecated)

package/dist/developer/customization/permissions.md

@@ -206,7 +206,7 @@ end
 
 ### Replacing the Ability Class
 
-You can replace the entire ability class via [Dependencies](/developer/customization/dependencies):
+You can replace the entire ability class via [Dependencies](dependencies.md):
 
 ```ruby
 # config/initializers/spree.rb

package/dist/developer/customization/quickstart.md

@@ -42,7 +42,7 @@ Spree is a flexible platform allowing you to customize every part of it to suit
     end
     ```
 
-    Please see [Configuration](/developer/customization/configuration) section for more information.
+    Please see [Configuration](configuration.md) section for more information.
 
 </details>
 
@@ -77,7 +77,7 @@ Spree is a flexible platform allowing you to customize every part of it to suit
     - Async by default - keeps requests fast
     - Easier testing and upgrades
 
-    Please see [Events](/developer/core-concepts/events) section for more information.
+    Please see [Events](../core-concepts/events.md) section for more information.
 
 </details>
 
@@ -95,7 +95,7 @@ Spree is a flexible platform allowing you to customize every part of it to suit
 
     Configure webhooks in **Admin > Developers > Webhooks** or via the API.
 
-    Please see [Webhooks](/developer/core-concepts/webhooks) section for more information.
+    Please see [Webhooks](../core-concepts/webhooks.md) section for more information.
 
 </details>
 
@@ -143,9 +143,9 @@ Spree is a flexible platform allowing you to customize every part of it to suit
     ```
 
     Please see:
-    - [Admin Navigation](/developer/admin/navigation) - For adding menu items
-    - [Admin Partials](/developer/admin/extending-ui) - For extending UI
-    - [Admin Tables](/developer/admin/tables) - For customizing list views
+    - [Admin Navigation](../admin/navigation.md) - For adding menu items
+    - [Admin Partials](../admin/extending-ui.md) - For extending UI
+    - [Admin Tables](../admin/tables.md) - For customizing list views
 
 </details>
 
@@ -162,7 +162,7 @@ Spree is a flexible platform allowing you to customize every part of it to suit
     Spree.ransack.add_association :product, :brand
     ```
 
-    Please see [Search & Filtering](/developer/core-concepts/search-filtering#extending-ransackable-configuration) section for more information.
+    Please see [Search & Filtering](../core-concepts/search-filtering.md#extending-ransackable-configuration) section for more information.
 
 </details>
 
@@ -199,8 +199,8 @@ Spree is a flexible platform allowing you to customize every part of it to suit
     > **WARNING:** Decorators should be used **only when no other option works**. They tightly couple your code to Spree internals and can break during upgrades.
 > 
 >       **Do NOT use decorators for:**
->       - After-save callbacks → Use [Events](/developer/core-concepts/events) instead
->       - External service sync → Use [Webhooks](/developer/core-concepts/webhooks) instead
+>       - After-save callbacks → Use [Events](../core-concepts/events.md) instead
+>       - External service sync → Use [Webhooks](../core-concepts/webhooks.md) instead
 >       - Custom service logic → Use [Dependencies](dependencies) instead
 >       - Admin UI changes → Use [Admin Extensions](#admin-extensions) instead
 

package/dist/developer/customization/v4/checkout.md

@@ -40,7 +40,7 @@ If you want a list of all the currently available states for the checkout, use t
 
 ## Default Checkout Steps
 
-The Spree checkout process consists of the following steps. With the exception of the Registration step, each of these steps corresponds to a state of the [Order object](/developer/core-concepts/orders):
+The Spree checkout process consists of the following steps. With the exception of the Registration step, each of these steps corresponds to a state of the [Order object](../../core-concepts/orders.md):
 
 * Registration Optional - only if using [spree_auth_devise](https://github.com/spree/spree_auth_devise) extension, can be toggled through the `Spree::Auth::Config[:registration_step]` configuration setting
 * Address Information
@@ -87,7 +87,7 @@ This step allows the customer to add both their billing and shipping information
 
 The address fields include a select box for choosing state/province. If there are no states configured for a particular country, the select box will be replaced by a text field instead.
 
-The list of countries that appear in the country select box can also be configured. Spree will list all countries by default, but you can configure exactly which countries you would like to appear. The list can be limited to a specific set of countries by [setting the Store's checkout zone](/developer/core-concepts/stores#checkout-configuration). Spree assumes that the list of billing and shipping countries will be the same. You can always change this logic via class decorator if this does not suit your needs.
+The list of countries that appear in the country select box can also be configured. Spree will list all countries by default, but you can configure exactly which countries you would like to appear. The list can be limited to a specific set of countries by [setting the Store's checkout zone](../../core-concepts/stores.md#checkout-configuration). Spree assumes that the list of billing and shipping countries will be the same. You can always change this logic via class decorator if this does not suit your needs.
 
 ### Delivery Options
 
@@ -105,7 +105,7 @@ If you do not want to use a gateway with payment profiles then you will need to
 
  Spree discards the credit card number after this step is processed. If you do not have a gateway with payment profiles enabled then your card information will be lost before it's time to authorize the card.
 
-For more information about payments, please see the [Payments guide](/developer/core-concepts/payments).
+For more information about payments, please see the [Payments guide](../../core-concepts/payments.md).
 
 ### Confirmation
 

package/dist/developer/customization/v4/deface.md

@@ -67,7 +67,7 @@ module Spree
 end
 ```
 
-Now, when we head to `http://localhost:3000/admin/products` and edit a product, we should be able to set a sale price for the product and be able to view it on our sale page, `http://localhost:3000/sale`. Note that you will likely need to restart our example Spree application created in the [Getting Started tutorial](/developer/getting-started/quickstart).
+Now, when we head to `http://localhost:3000/admin/products` and edit a product, we should be able to set a sale price for the product and be able to view it on our sale page, `http://localhost:3000/sale`. Note that you will likely need to restart our example Spree application created in the [Getting Started tutorial](../../getting-started/quickstart.md).
 
 ### Available actions
 

package/dist/developer/deployment/assets.md

@@ -4,7 +4,7 @@ title: Assets
 
 By default, files are stored on the local filesystem. For production, use a cloud storage service.
 
-Spree auto-detects the storage provider based on which environment variables are set — no code changes needed. See [Environment Variables](/developer/deployment/environment_variables#file-storage-s3--cloudflare-r2) for the full list.
+Spree auto-detects the storage provider based on which environment variables are set — no code changes needed. See [Environment Variables](environment_variables.md#file-storage-s3--cloudflare-r2) for the full list.
 
 ## AWS S3
 

package/dist/developer/deployment/aws.md

@@ -5,7 +5,7 @@ description: Learn how to deploy your Spree application on Amazon Web Services (
 
 Amazon Web Services offers reliable, scalable, and inexpensive cloud computing services. AWS is also one of the most popular choices for hosting a Spree application. 
 
-We recommend using AWS ECS Fargate to host your Spree application via [Docker image](/developer/deployment/docker).
+We recommend using AWS ECS Fargate to host your Spree application via [Docker image](docker.md).
 
 ## Required AWS services
 
@@ -15,8 +15,8 @@ To fully run your Spree application on AWS, you will need the following services
 |---------|-------------|
 | [AWS ECS Fargate](https://aws.amazon.com/fargate/) | Amazon Elastic Container Service (ECS) is a fully managed container orchestration service that allows you to run and scale containerized applications without managing the underlying infrastructure. |
 | [AWS RDS](https://aws.amazon.com/rds/) | Amazon Relational Database Service makes it easy to set up, operate, and scale a relational database in the cloud. Spree works great with multiple databases: [Amazon Aurora both MySQL and PostgreSQL variants](https://aws.amazon.com/rds/aurora/), [RDS PostgreSQL](https://aws.amazon.com/rds/postgresql/), [RDS MySQL](https://aws.amazon.com/rds/mysql/) and [RDS MariaDB](https://aws.amazon.com/rds/mariadb/) |
-| [AWS ElastiCache](https://aws.amazon.com/elasticache/redis/?nc=sn&loc=2&dn=1) | Valkey or Redis instance for background jobs (Sidekiq), [caching](/developer/deployment/caching), and Action Cable. |
-| [AWS S3](https://aws.amazon.com/s3/) | Object storage service to store and read your uploaded files such as Product images, etc. [More information](/developer/deployment/assets#aws-s3). |
+| [AWS ElastiCache](https://aws.amazon.com/elasticache/redis/?nc=sn&loc=2&dn=1) | Valkey or Redis instance for background jobs (Sidekiq), [caching](caching.md), and Action Cable. |
+| [AWS S3](https://aws.amazon.com/s3/) | Object storage service to store and read your uploaded files such as Product images, etc. [More information](assets.md#aws-s3). |
 | [AWS CloudFront](https://aws.amazon.com/cloudfront/) | Fast content delivery network CDN to speed up your asset images/stylesheets/javascript delivery. This will greatly enhance your application responsiveness. |
 | [AWS Route 53](https://aws.amazon.com/route53/) | Domain name system (DNS) service to manage your domain names and DNS records. |
 | [AWS Certificate Manager](https://aws.amazon.com/certificate-manager/) | AWS Certificate Manager is a service that provides you with SSL/TLS certificates that you can use to secure your application. Spree in production works only with HTTPS. |
@@ -24,7 +24,7 @@ To fully run your Spree application on AWS, you will need the following services
 
 ## Docker Image
 
-You can use the [official Docker image](/developer/deployment/docker) (`ghcr.io/spree/spree`) directly, or build your own from your Rails application's Dockerfile.
+You can use the [official Docker image](docker.md) (`ghcr.io/spree/spree`) directly, or build your own from your Rails application's Dockerfile.
 
 To build and deploy a custom image to AWS ECR via GitHub Actions:
 
@@ -205,7 +205,7 @@ This action requires secrets to be set in your GitHub repository. You can find t
 
 ## Environment variables
 
-For a full list of Docker environment variables, please refer to the [Environment variables](/developer/deployment/environment_variables) page.
+For a full list of Docker environment variables, please refer to the [Environment variables](environment_variables.md) page.
 
 ## ECS tasks
 

package/dist/developer/deployment/docker.md

@@ -95,7 +95,7 @@ docker compose up -d
 
 The database is automatically created and migrated on first boot. The app is available at [http://localhost:3000](http://localhost:3000).
 
-> **TIP:** Use [create-spree-app](/developer/create-spree-app/quickstart) for a fully scaffolded Docker setup with `.env` files, health checks, and optional Next.js storefront — all configured automatically.
+> **TIP:** Use [create-spree-app](../create-spree-app/quickstart.md) for a fully scaffolded Docker setup with `.env` files, health checks, and optional Next.js storefront — all configured automatically.
 
 ### Required Environment Variables
 
@@ -105,7 +105,7 @@ The database is automatically created and migrated on first boot. The app is ava
 | `REDIS_URL` | Redis URL for jobs, caching, and Action Cable | `redis://redis:6379/0` |
 | `SECRET_KEY_BASE` | Secret key for session encryption | Generate with `bin/rails secret` |
 
-See [Environment Variables](/developer/deployment/environment_variables) for the full list.
+See [Environment Variables](environment_variables.md) for the full list.
 
 ## Building Your Own Image
 

package/dist/developer/deployment/environment_variables.md

@@ -67,7 +67,7 @@ By default, uploaded files (product images, assets) are stored on the local file
 
 ## Search (Meilisearch)
 
-Optional. When configured, Spree uses [Meilisearch](/integrations/search/meilisearch) for product search, filtering, and faceted navigation instead of SQL.
+Optional. When configured, Spree uses [Meilisearch](../../integrations/search/meilisearch.md) for product search, filtering, and faceted navigation instead of SQL.
 
 | Variable | Default | Description |
 | --- | --- | --- |

package/dist/developer/deployment/render.md

@@ -55,7 +55,7 @@ Default credentials are created during `db:seed`. Change them immediately after
 
 ### Environment Variables
 
-Render sets `DATABASE_URL`, `REDIS_URL`, and `SECRET_KEY_BASE` automatically from the blueprint. For additional configuration (SMTP, file storage, Sentry, etc.), see [Environment Variables](/developer/deployment/environment_variables).
+Render sets `DATABASE_URL`, `REDIS_URL`, and `SECRET_KEY_BASE` automatically from the blueprint. For additional configuration (SMTP, file storage, Sentry, etc.), see [Environment Variables](environment_variables.md).
 
 ## Production Sizing
 
@@ -86,10 +86,10 @@ To enable auto-scaling, add this to the web service in your `render.yaml`:
 
 Render provides ephemeral storage — uploaded files (product images, etc.) won't persist across deploys. Set up cloud storage:
 
-- [Asset Storage](/developer/deployment/assets) (Amazon S3 / Cloudflare R2)
+- [Asset Storage](assets.md) (Amazon S3 / Cloudflare R2)
 
 Before going to production:
 
-- [Set environment variables](/developer/deployment/environment_variables) (SMTP, SSL, etc.)
-- [Configure CDN](/developer/deployment/cdn)
-- [Configure caching](/developer/deployment/caching)
+- [Set environment variables](environment_variables.md) (SMTP, SSL, etc.)
+- [Configure CDN](cdn.md)
+- [Configure caching](caching.md)

package/dist/developer/getting-started/quickstart.md

@@ -23,7 +23,7 @@ The quickest way to get started. Scaffolds a full Spree project with Next.js Sto
 
     Once complete, your store should be running at [http://localhost:3000/admin](http://localhost:3000/admin). The port can be different if `3000` is already used on your system.
 
-    See the full [create-spree-app documentation](/developer/create-spree-app/quickstart) for all CLI flags and options.
+    See the full [create-spree-app documentation](../create-spree-app/quickstart.md) for all CLI flags and options.
 
   **Manual Installation:**
 
@@ -57,7 +57,7 @@ For developers who prefer full control over the setup, or want to add Spree to a
         bin/rails spree_sample:load
         ```
 
-    > **INFO:** Spree works with **PostgreSQL**, **MySQL**, and **SQLite** databases. The Rails template defaults to SQLite for quick setup. You can switch to PostgreSQL or MySQL at any time. [Learn more about database configuration](/developer/deployment/database).
+    > **INFO:** Spree works with **PostgreSQL**, **MySQL**, and **SQLite** databases. The Rails template defaults to SQLite for quick setup. You can switch to PostgreSQL or MySQL at any time. [Learn more about database configuration](../deployment/database.md).
 
 
 ## Accessing Admin Panel

package/dist/developer/how-to/custom-payment-method.md

@@ -13,7 +13,7 @@ This guide walks you through building a custom payment method integration for Sp
 - Handles webhooks for reliable payment confirmation
 - Optionally supports saving payment methods for future use (Payment Setup Sessions)
 
-Before starting, make sure you understand [how payments work in Spree](/developer/core-concepts/payments).
+Before starting, make sure you understand [how payments work in Spree](../core-concepts/payments.md).
 
 ## Step 1: Create the Payment Method Model
 
@@ -367,8 +367,8 @@ For every gateway action (authorize, purchase, capture, void, credit), Spree pas
 
 ## Related Documentation
 
-- [Payments](/developer/core-concepts/payments) - Payment architecture and core concepts
-- [Checkout Customization](/developer/customization/checkout) - Customizing the checkout flow
-- [Events](/developer/core-concepts/events) - Subscribe to payment events
-- [Stripe Integration](/integrations/payments/stripe) - Reference implementation using Stripe
-- [Adyen Integration](/integrations/payments/adyen) - Reference implementation using Adyen
+- [Payments](../core-concepts/payments.md) - Payment architecture and core concepts
+- [Checkout Customization](../customization/checkout.md) - Customizing the checkout flow
+- [Events](../core-concepts/events.md) - Subscribe to payment events
+- [Stripe Integration](../../integrations/payments/stripe.md) - Reference implementation using Stripe
+- [Adyen Integration](../../integrations/payments/adyen.md) - Reference implementation using Adyen

package/dist/developer/how-to/custom-promotion.md

@@ -5,14 +5,14 @@ description: Step-by-step guide to creating custom promotion rules and actions f
 
 ## Overview
 
-Spree's promotion system is built around two extension points: **Rules** (eligibility conditions) and **Actions** (what happens when a promotion applies). While Spree ships with a comprehensive set of [built-in rules and actions](/developer/core-concepts/promotions#rules), you can create custom ones for business-specific logic.
+Spree's promotion system is built around two extension points: **Rules** (eligibility conditions) and **Actions** (what happens when a promotion applies). While Spree ships with a comprehensive set of [built-in rules and actions](../core-concepts/promotions.md#rules), you can create custom ones for business-specific logic.
 
 This guide covers:
 - Creating a custom promotion rule with admin UI
 - Creating a custom promotion action with a calculator
 - Understanding the `eligible?`, `actionable?`, and `perform` contracts
 
-Before starting, make sure you understand [how promotions work in Spree](/developer/core-concepts/promotions).
+Before starting, make sure you understand [how promotions work in Spree](../core-concepts/promotions.md).
 
 ## Custom Promotion Rules
 
@@ -153,7 +153,7 @@ end
 
 ## Custom Promotion Actions
 
-Actions define what happens when a promotion is applied. Most actions create [adjustments](/developer/core-concepts/adjustments) on orders or line items.
+Actions define what happens when a promotion is applied. Most actions create [adjustments](../core-concepts/adjustments.md) on orders or line items.
 
 ### Step 1: Create the Action Class
 
@@ -367,7 +367,7 @@ end
 
 ## Related Documentation
 
-- [Promotions](/developer/core-concepts/promotions) - Promotion architecture and built-in rules/actions
-- [Calculators](/developer/core-concepts/calculators) - Available calculator types for promotion actions
-- [Adjustments](/developer/core-concepts/adjustments) - How adjustments work on orders and line items
-- [Events](/developer/core-concepts/events) - Subscribe to promotion events
+- [Promotions](../core-concepts/promotions.md) - Promotion architecture and built-in rules/actions
+- [Calculators](../core-concepts/calculators.md) - Available calculator types for promotion actions
+- [Adjustments](../core-concepts/adjustments.md) - How adjustments work on orders and line items
+- [Events](../core-concepts/events.md) - Subscribe to promotion events

package/dist/developer/how-to/custom-report.md

@@ -9,7 +9,7 @@ Spree's reporting system is designed for extension. Each report is a pair of cla
 
 This guide walks you through building a custom report from scratch, including advanced patterns for SQL aggregations and multi-vendor support.
 
-Before starting, make sure you understand [how the reporting system works](/developer/core-concepts/reports).
+Before starting, make sure you understand [how the reporting system works](../core-concepts/reports.md).
 
 ## Creating a Custom Report
 
@@ -383,5 +383,5 @@ end
 
 ## Related Documentation
 
-- [Reports](/developer/core-concepts/reports) - Report architecture and built-in reports
-- [Events](/developer/core-concepts/events) - How report generation uses the events system
+- [Reports](../core-concepts/reports.md) - Report architecture and built-in reports
+- [Events](../core-concepts/events.md) - How report generation uses the events system

package/dist/developer/how-to/custom-search-provider.md

@@ -12,9 +12,9 @@ This guide walks you through building a custom search provider for Spree. By the
 - Integrates with the Store API without any frontend changes
 - Supports background indexing and bulk reindex
 
-Before starting, make sure you understand [how search and filtering works in Spree](/developer/core-concepts/search-filtering).
+Before starting, make sure you understand [how search and filtering works in Spree](../core-concepts/search-filtering.md).
 
-> **INFO:** Spree ships with a built-in [Meilisearch provider](/integrations/search/meilisearch). If Meilisearch fits your needs, you don't need to build a custom provider — just configure it.
+> **INFO:** Spree ships with a built-in [Meilisearch provider](../../integrations/search/meilisearch.md). If Meilisearch fits your needs, you don't need to build a custom provider — just configure it.
 
 ## Architecture
 
@@ -131,7 +131,7 @@ The `ProductPresenter` returns an array of documents. For a store with US (USD/E
 
 ## Step 4: Implement Bulk Reindex
 
-Use `ProductPresenter::REQUIRED_PRELOADS` to avoid N+1 queries:
+Use `preload_associations_lazily` to avoid N+1 queries:
 
 ```ruby app/models/my_app/search_provider/typesense.rb
 def reindex(scope = nil)
@@ -139,9 +139,9 @@ def reindex(scope = nil)
   ensure_index_settings!
 
   scope.reorder(id: :asc)
-       .preload(*Spree::SearchProvider::ProductPresenter::REQUIRED_PRELOADS)
+       .preload_associations_lazily
        .find_in_batches(batch_size: 500) do |batch|
-    documents = batch.flat_map { |p| Spree::SearchProvider::ProductPresenter.new(p, store).call }
+    documents = batch.flat_map { |p| presenter_class.new(p, store).call }
     index_batch(documents)
   end
 end
@@ -226,5 +226,5 @@ Always use prefixed IDs (`ctg_abc`, `prod_xyz`, `optval_abc`) when indexing. Nev
 
 ## Related Documentation
 
-- [Search & Filtering](/developer/core-concepts/search-filtering) — Store API search reference
-- [Meilisearch Integration](/integrations/search/meilisearch) — Built-in Meilisearch provider setup
+- [Search & Filtering](../core-concepts/search-filtering.md) — Store API search reference
+- [Meilisearch Integration](../../integrations/search/meilisearch.md) — Built-in Meilisearch provider setup

package/dist/developer/multi-store/quickstart.md

@@ -68,4 +68,4 @@ Spree supports managing custom domains for Stores. In the Admin Panel, you can m
 
 ## Setup multi-store application
 
-[Follow the setup guide](/developer/multi-store/setup) to get started.
+[Follow the setup guide](setup.md) to get started.

package/dist/developer/multi-tenant/quickstart.md

@@ -17,4 +17,4 @@ To sum it up:
 
 ## Setup SaaS application
 
-[Follow the installation instructions](/developer/multi-tenant/installation) to setup a multi-tenant Spree application.
+[Follow the installation instructions](installation.md) to setup a multi-tenant Spree application.

package/dist/developer/sdk/authentication.md

@@ -3,7 +3,7 @@ title: Authentication
 description: Authentication modes and guest checkout with the Spree SDK
 ---
 
-The SDK supports multiple authentication modes depending on your use case. For a full overview of the API authentication methods, see the [Store API Authentication](/api-reference/store-api/authentication) reference.
+The SDK supports multiple authentication modes depending on your use case. For a full overview of the API authentication methods, see the [Store API Authentication](../../api-reference/store-api/authentication.md) reference.
 
 ## Publishable Key Only (Guest/Public Access)
 

package/dist/developer/sdk/configuration.md

@@ -5,7 +5,7 @@ description: Localization, error handling, TypeScript types, and custom fetch
 
 ## Localization & Currency
 
-Pass locale and currency headers with any request. For full details, see the [Localization](/api-reference/store-api/localization) reference.
+Pass locale and currency headers with any request. For full details, see the [Localization](../../api-reference/store-api/localization.md) reference.
 
 ```typescript
 // Set locale and currency per request

package/dist/developer/sdk/store/markets.md

@@ -146,6 +146,6 @@ curl 'https://api.mystore.com/api/v3/store/markets/mkt_gbHJdmfrXB/countries/US?e
 
 ## Related Documentation
 
-- [Markets](/developer/core-concepts/markets) — Market concepts, zones, and configuration
-- [Localization](/api-reference/store-api/localization) — Locale and currency headers
-- [Geography](/developer/sdk/store/products#geography) — Global country endpoints
+- [Markets](../../core-concepts/markets.md) — Market concepts, zones, and configuration
+- [Localization](../../../api-reference/store-api/localization.md) — Locale and currency headers
+- [Geography](products.md#geography) — Global country endpoints

package/dist/developer/storefront/nextjs/customization.md

@@ -138,4 +138,4 @@ export default async function YourNewPage() {
 
 ## Building a Custom Storefront
 
-If you prefer to build from scratch instead of forking the starter, you can use the `@spree/next` and `@spree/sdk` packages directly in any Next.js application. See the [@spree/next Package](/developer/storefront/nextjs/spree-next-package) documentation for the complete API reference.
+If you prefer to build from scratch instead of forking the starter, you can use the `@spree/next` and `@spree/sdk` packages directly in any Next.js application. See the [@spree/next Package](spree-next-package.md) documentation for the complete API reference.

package/dist/developer/storefront/nextjs/quickstart.md

@@ -72,7 +72,7 @@ SPREE_PUBLISHABLE_KEY=your_publishable_api_key_here
 
 > **NOTE:** These are server-side only variables — no `NEXT_PUBLIC_` prefix needed since all API calls happen in Server Actions.
 
-See [Deployment](/developer/storefront/nextjs/deployment) for all optional environment variables (Sentry, GTM, etc.).
+See [Deployment](deployment.md) for all optional environment variables (Sentry, GTM, etc.).
 
 ## Development
 
@@ -89,4 +89,4 @@ npm run build
 npm start
 ```
 
-See the [Deployment](/developer/storefront/nextjs/deployment) guide for Vercel, Docker, and other hosting options.
+See the [Deployment](deployment.md) guide for Vercel, Docker, and other hosting options.