@spree/docs 0.1.0 → 0.1.1

package/dist/api-reference/storefront/authentication.md

@@ -9,7 +9,7 @@ Storefront API requires authorization only for certain actions associated with u
 
 ### Using X-Spree-Order-Token header
 
-[Cart](/api-reference/storefront/cart) and [Checkout](/api-reference/storefront/checkout) endpoints paths also allow interactions without the bearer token to allow creating and managing guest checkouts.
+[Cart](cart.md) and [Checkout](checkout.md) endpoints paths also allow interactions without the bearer token to allow creating and managing guest checkouts.
 
 When you first create a cart via:
 
@@ -39,7 +39,7 @@ You can store this token in the frontend session (eg. Session Storage or a cooki
 
 ## For signed in users
 
-For users who have an account in your store, you will need to generate oAuth tokens to authenticate requests to endpoints such as [Account](/api-reference/storefront/account), [Cart](/api-reference/storefront/cart) and [Checkout](/api-reference/storefront/checkout).
+For users who have an account in your store, you will need to generate oAuth tokens to authenticate requests to endpoints such as [Account](account.md), [Cart](cart.md) and [Checkout](checkout.md).
 
 ### Generating OAuth token
 

package/dist/api-reference/tutorials/adyen-integration-guide-for-android.md

@@ -15,7 +15,7 @@ This doc will be referring to the library version as YOUR_VERSION.
 ## Resources
 
 - [Official Adyen Documentation for Android integration](https://docs.adyen.com/online-payments/build-your-integration/sessions-flow/?platform=Android&integration=Drop-in&version=5.13.1)
-- Spree Adyen API docs - [create payment_session](/api-reference/storefront/adyen/create-an-adyen-payment-session) and [get payment_session](/api-reference/storefront/adyen/get-adyen-payment-session)
+- Spree Adyen API docs - [create payment_session](../storefront/adyen/create-an-adyen-payment-session.md) and [get payment_session](../storefront/adyen/get-adyen-payment-session.md)
 - [Official Adyen example for Android integration](https://github.com/adyen-examples/adyen-android-online-payments)
 
 ## Overview
@@ -43,7 +43,7 @@ implementation "com.adyen.checkout:drop-in:YOUR_VERSION"
 
 ## Step 2: Create a checkout session
 
-Create session using [this endpoint](/api-reference/storefront/adyen/create-an-adyen-payment-session).
+Create session using [this endpoint](../storefront/adyen/create-an-adyen-payment-session.md).
 
 ```kotlin
 val sessionModel = SessionModel.SERIALIZER.deserialize(sessionsResponseJSON)

package/dist/api-reference/tutorials/adyen-integration-guide-for-ios.md

@@ -27,7 +27,7 @@ Current newest version available at the moment of writing the tutorial is 5.19.2
 ## Resources
 
 - [Official Adyen Documentation for iOS integration](https://docs.adyen.com/online-payments/build-your-integration/sessions-flow/?platform=iOS&integration=Drop-in&version=5.19.2)
-- Spree Adyen API docs - [create payment_session](/api-reference/storefront/adyen/create-an-adyen-payment-session) and [get payment_session](/api-reference/storefront/adyen/get-adyen-payment-session)
+- Spree Adyen API docs - [create payment_session](../storefront/adyen/create-an-adyen-payment-session.md) and [get payment_session](../storefront/adyen/get-adyen-payment-session.md)
 - [Official Adyen example for iOS integration](https://github.com/Adyen/adyen-ios/tree/develop/Demo)
 - Apple Developer documentation on [defining custom url scheme](https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app)
 
@@ -68,7 +68,7 @@ let adyenContext = AdyenContext(apiContext: apiContext, payment:payment)
 
 ## Step 3: Create and set up session
 
-Create a session using [payment_session endpoint](/api-reference/storefront/adyen/create-an-adyen-payment-session).
+Create a session using [payment_session endpoint](../storefront/adyen/create-an-adyen-payment-session.md).
 Then set a configuration using data from the response:
 
 ```swift

package/dist/api-reference/tutorials/quick-checkout-with-stripe.md

@@ -72,14 +72,14 @@ Here we need to send some basic information about the customer's shipping addres
 
     - **`bill_address_id`** (`string`) — Set it to `CLEAR` to clear the existing billing address (this prevents the order from accidentally advancing to the `payment` step).
 
-    [Full documentation](/api-reference/storefront/checkout/update-checkout)
+    [Full documentation](../storefront/checkout/update-checkout.md)
 
 </details>
 
 <details>
 <summary>Move the order to the delivery step</summary>
 
-[Endpoint documentation](/api-reference/storefront/checkout-state/advance-checkout)
+[Endpoint documentation](../storefront/checkout-state/advance-checkout.md)
 
 ```bash Advance order to the delivery step
 curl -X PATCH '<SHOP URL>/api/v2/storefront/checkout/advance?state=delivery&include=shipments.shipping_rates' \
@@ -104,7 +104,7 @@ This will return you an order response, and you can update the payment element w
 
 Here we need to send the selected shipping method to the backend and update the total in the payment element
 
-[Endpoint documentation](/api-reference/storefront/checkout-shipments/selects-shipping-method-for-shipments)
+[Endpoint documentation](../storefront/checkout-shipments/selects-shipping-method-for-shipments.md)
 
 ```bash Select shipping method
 curl -X PATCH '<SHOP URL>/api/v2/storefront/checkout/select_shipping_method' \
@@ -132,7 +132,7 @@ Now you should make several more calls to the backend
     ```
     > **INFO:** `200` response code means that the order is ready for the payment.
 
-    [Endpoint documentation](/api-reference/storefront/checkout/validate-order-payment)
+    [Endpoint documentation](../storefront/checkout/validate-order-payment.md)
 
 </details>
 
@@ -141,7 +141,7 @@ Now you should make several more calls to the backend
 
 You should have a lot more information about the customer (in previous events, Stripe probably will not provide you information such as customer address), so send them to the backend:
 
-  [Endpoint documentation](/api-reference/storefront/checkout/update-checkout)
+  [Endpoint documentation](../storefront/checkout/update-checkout.md)
 
   ```bash Update the order [expandable]
   curl -X PATCH <SHOP URL>/api/v2/storefront/checkout \
@@ -194,7 +194,7 @@ You should have a lot more information about the customer (in previous events, S
   <details>
 <summary>Move the order to the payment step</summary>
 
-[Endpoint documentation](/api-reference/storefront/checkout-state/advance-checkout)
+[Endpoint documentation](../storefront/checkout-state/advance-checkout.md)
   ```bash Move the order to the payment step
   curl -X PATCH '<SHOP URL>/api/v2/storefront/checkout/advance?state=payment' \
     -H 'Authorization: Bearer <Token>' \
@@ -221,7 +221,7 @@ curl -X POST <SHOP URL>/api/v2/storefront/stripe/payment_intents/<PAYMENT INTENT
   -H 'Authorization: Bearer <Token>'
 ```
 
-[Endpoint documentation](/api-reference/storefront/stripe/mark-the-payment-intent-as-confirmed-and-move-the-order-to-the-complete-state)
+[Endpoint documentation](../storefront/stripe/mark-the-payment-intent-as-confirmed-and-move-the-order-to-the-complete-state.md)
 
 This will also check if the payment intent is confirmed, and it will move the order to the complete state
 
@@ -241,7 +241,7 @@ curl -X PATCH <SHOP URL>/api/v2/storefront/checkout \
   }'
 ```
 
-[Endpoint documentation](/api-reference/storefront/checkout/update-checkout)
+[Endpoint documentation](../storefront/checkout/update-checkout.md)
 
 ### All Done!
 

package/dist/api-reference/v2/introduction.md

@@ -10,9 +10,9 @@ Spree Commerce open-source comes with a fully-featured Ecommerce API enabling a
 Currently Spree includes 2 modern REST APIs:
 
 
-  - [Storefront API](/api-reference/storefront/authentication) — Designed to allow customers to interact with the store via external applications (e.g. Next.js storefront or a dedicated mobile app)
+  - [Storefront API](../storefront/authentication.md) — Designed to allow customers to interact with the store via external applications (e.g. Next.js storefront or a dedicated mobile app)
 
-  - [Platform API](/api-reference/platform/authentication) — Provides management capabilities, allowing third party apps to perform actions otherwise available via the admin panel.
+  - [Platform API](../platform/authentication.md) — Provides management capabilities, allowing third party apps to perform actions otherwise available via the admin panel.
 
 
 ## Thank you!

package/dist/api-reference/webhooks-events.md

@@ -25,9 +25,9 @@ Every webhook delivery sends a JSON envelope with the event metadata and a `data
 | `data` | object | Serialized resource (see payloads below) |
 | `metadata` | object | Additional context including Spree version |
 
-Event payloads use the same [Store API V3 serializers](/api-reference/introduction) as the REST API. All `id` fields use [prefixed IDs](/api-reference/introduction) (e.g., `or_m3Rp9wXz`, `prod_86Rf07xd4z`). All monetary values are strings. All timestamps are ISO 8601.
+Event payloads use the same [Store API V3 serializers](introduction.md) as the REST API. All `id` fields use [prefixed IDs](introduction.md) (e.g., `or_m3Rp9wXz`, `prod_86Rf07xd4z`). All monetary values are strings. All timestamps are ISO 8601.
 
-For details on creating webhook endpoints and verifying signatures, see [Webhooks](/developer/core-concepts/webhooks). For the event system internals and subscriber pattern, see [Events](/developer/core-concepts/events).
+For details on creating webhook endpoints and verifying signatures, see [Webhooks](../developer/core-concepts/webhooks.md). For the event system internals and subscriber pattern, see [Events](../developer/core-concepts/events.md).
 
 > **INFO:** Event payloads include the same top-level attributes and unconditional associations as API responses. Conditional associations (like product variants, images, or metafields) are not included in event payloads.
 

package/dist/developer/admin/admin.md

@@ -24,10 +24,10 @@ The Admin Dashboard allows store administrators to manage:
 As a developer, you can fully customize the Admin Dashboard:
 
 
-  - [Add New Sections](/developer/tutorial/admin) — Create entirely new admin pages for custom features like Brands, Vendors, or any custom model
-  - [Extend Existing UI](/developer/admin/extending-ui) — Inject custom fields, buttons, and sections into existing admin pages
-  - [Custom Navigation](/developer/admin/navigation) — Add menu items to the sidebar or create custom navigation structures
-  - [Custom Styling](/developer/admin/custom-css) — Add your own CSS to match your brand or modify the look and feel
+  - [Add New Sections](../tutorial/admin.md) — Create entirely new admin pages for custom features like Brands, Vendors, or any custom model
+  - [Extend Existing UI](extending-ui.md) — Inject custom fields, buttons, and sections into existing admin pages
+  - [Custom Navigation](navigation.md) — Add menu items to the sidebar or create custom navigation structures
+  - [Custom Styling](custom-css.md) — Add your own CSS to match your brand or modify the look and feel
 
 
 ## Architecture Overview
@@ -79,11 +79,11 @@ module Spree
 end
 ```
 
-> **INFO:** Learn more about creating admin sections in the [Admin Dashboard Tutorial](/developer/tutorial/admin).
+> **INFO:** Learn more about creating admin sections in the [Admin Dashboard Tutorial](../tutorial/admin.md).
 
 ### Views & Templates
 
-Views use standard Rails ERB templates with Spree's [Form Builder](/developer/admin/form-builder) and [Components](/developer/admin/components):
+Views use standard Rails ERB templates with Spree's [Form Builder](form-builder.md) and [Components](components.md):
 
 ```erb
 <%# app/views/spree/admin/brands/_form.html.erb %>
@@ -117,7 +117,7 @@ Spree Admin uses [Hotwire](https://hotwire.dev/) (Turbo + Stimulus) for interact
 </div>
 ```
 
-> **INFO:** Add custom JavaScript using [Stimulus controllers](/developer/admin/custom-javascript).
+> **INFO:** Add custom JavaScript using [Stimulus controllers](custom-javascript.md).
 
 ### Styling
 
@@ -135,7 +135,7 @@ The Admin Dashboard uses [Tailwind CSS v4](https://tailwindcss.com/) for styling
 </div>
 ```
 
-> **INFO:** Learn how to customize styles in [Custom CSS](/developer/admin/custom-css).
+> **INFO:** Learn how to customize styles in [Custom CSS](custom-css.md).
 
 ## Quick Reference
 
@@ -143,10 +143,10 @@ The Admin Dashboard uses [Tailwind CSS v4](https://tailwindcss.com/) for styling
 
 | Tool | Purpose | Documentation |
 |------|---------|---------------|
-| Form Builder | Create consistent forms with validation | [Form Builder](/developer/admin/form-builder) |
-| Components | Dropdowns, dialogs, icons, badges, etc. | [Components](/developer/admin/components) |
-| Helper Methods | Navigation, links, utilities | [Helper Methods](/developer/admin/helper-methods) |
-| UI Extensions | Inject content into existing pages | [Extending UI](/developer/admin/extending-ui) |
+| Form Builder | Create consistent forms with validation | [Form Builder](form-builder.md) |
+| Components | Dropdowns, dialogs, icons, badges, etc. | [Components](components.md) |
+| Helper Methods | Navigation, links, utilities | [Helper Methods](helper-methods.md) |
+| UI Extensions | Inject content into existing pages | [Extending UI](extending-ui.md) |
 
 ### Common Tasks
 
@@ -178,7 +178,7 @@ Admin users must be authenticated to access the dashboard. Spree supports:
 - Custom authentication adapters
 - SSO integration
 
-> **INFO:** See [Authentication](/developer/admin/authentication) for setup details.
+> **INFO:** See [Authentication](authentication.md) for setup details.
 
 ### Authorization
 
@@ -194,12 +194,12 @@ authorize! :update, @product
 <% end %>
 ```
 
-> **INFO:** See [Permissions](/developer/customization/permissions) for defining custom abilities.
+> **INFO:** See [Permissions](../customization/permissions.md) for defining custom abilities.
 
 ## Next Steps
 
 
-  - [Tutorial: Build Admin UI](/developer/tutorial/admin) — Step-by-step guide to creating a complete admin section
-  - [Form Builder](/developer/admin/form-builder) — Learn all available form field helpers
-  - [Components](/developer/admin/components) — Explore UI components like dropdowns, dialogs, and icons
-  - [Extending UI](/developer/admin/extending-ui) — Add custom content to existing admin pages
+  - [Tutorial: Build Admin UI](../tutorial/admin.md) — Step-by-step guide to creating a complete admin section
+  - [Form Builder](form-builder.md) — Learn all available form field helpers
+  - [Components](components.md) — Explore UI components like dropdowns, dialogs, and icons
+  - [Extending UI](extending-ui.md) — Add custom content to existing admin pages

package/dist/developer/admin/components.md

@@ -400,7 +400,7 @@ Displays optimized images with automatic WebP conversion and retina support.
 <% end %>
 ```
 
-> **INFO:** For comprehensive documentation on image handling, storage configuration, and best practices, see the [Media](/developer/core-concepts/media) guide.
+> **INFO:** For comprehensive documentation on image handling, storage configuration, and best practices, see the [Media](../core-concepts/media.md) guide.
 
 ## Tooltip
 

package/dist/developer/admin/extending-ui.md

@@ -235,7 +235,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the orders list filters, to add custom filters.
     This partial has access to the `f` variable, which is the form builder for the filters, eg.
@@ -244,7 +244,7 @@ Here's a list of all places you can inject your custom code:
     <%= f.spree_text_field :q_number_cont, data: { filters_target: :input } %>
     ```
 
-    > **TIP:** * `q_number_cont` - The name of the filter field. For filtering we're using [ransack](/developer/core-concepts/search-filtering) gem, so the name of the filter field is the name of the attribute we're filtering by.
+    > **TIP:** * `q_number_cont` - The name of the filter field. For filtering we're using [ransack](../core-concepts/search-filtering.md) gem, so the name of the filter field is the name of the attribute we're filtering by.
 >     * `data: { filters_target: :input }` - Needed for the [Stimulus Filters controller](https://github.com/spree/spree/blob/main/admin/app/javascript/spree/admin/controllers/filters_controller.js) to work.
 
 </details>
@@ -414,7 +414,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`ActionView::Helpers::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`ActionView::Helpers::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the customers list filters. This partial has access to the `f` variable, which is the form builder for the filters.
 
@@ -422,7 +422,7 @@ Here's a list of all places you can inject your custom code:
     <%= f.spree_select :custom_field_eq, [["VIP", "vip"], ["Regular", "regular"]], { include_blank: true }, { data: { filters_target: :input } } %>
     ```
 
-    > **TIP:** * Use [ransack](/developer/core-concepts/search-filtering) search syntax for filter field names
+    > **TIP:** * Use [ransack](../core-concepts/search-filtering.md) search syntax for filter field names
 >     * Include `data: { filters_target: :input }` for proper integration with the Stimulus Filters controller
 
 </details>
@@ -467,7 +467,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the stock items list filters.
 
@@ -477,7 +477,7 @@ Here's a list of all places you can inject your custom code:
         data: { filters_target: :input } %>
     ```
 
-    > **TIP:** Use [ransack](/developer/core-concepts/search-filtering) search syntax for filter field names (e.g., `_lt` for "less than").
+    > **TIP:** Use [ransack](../core-concepts/search-filtering.md) search syntax for filter field names (e.g., `_lt` for "less than").
 
 </details>
 
@@ -649,7 +649,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the customer returns list filters.
 
@@ -660,7 +660,7 @@ Here's a list of all places you can inject your custom code:
         { data: { filters_target: :input } } %>
     ```
 
-    > **TIP:** Use [ransack](/developer/core-concepts/search-filtering) search syntax for filter field names (e.g., `_eq` for "equals").
+    > **TIP:** Use [ransack](../core-concepts/search-filtering.md) search syntax for filter field names (e.g., `_eq` for "equals").
 
 </details>
 
@@ -768,7 +768,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the gift cards list filters.
 
@@ -779,7 +779,7 @@ Here's a list of all places you can inject your custom code:
         data: { filters_target: :input } %>
     ```
 
-    > **TIP:** Use [ransack](/developer/core-concepts/search-filtering) search syntax for filter field names (e.g., `_gt` for "greater than").
+    > **TIP:** Use [ransack](../core-concepts/search-filtering.md) search syntax for filter field names (e.g., `_gt` for "greater than").
 
 </details>
 
@@ -1015,7 +1015,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the posts list filters.
 
@@ -1026,7 +1026,7 @@ Here's a list of all places you can inject your custom code:
         { data: { filters_target: :input } } %>
     ```
 
-    > **TIP:** Use [ransack](/developer/core-concepts/search-filtering) search syntax for filter field names.
+    > **TIP:** Use [ransack](../core-concepts/search-filtering.md) search syntax for filter field names.
 
 </details>
 
@@ -1070,7 +1070,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the promotions list filters.
 
@@ -1081,7 +1081,7 @@ Here's a list of all places you can inject your custom code:
         { data: { filters_target: :input } } %>
     ```
 
-    > **TIP:** Use [ransack](/developer/core-concepts/search-filtering) search syntax for filter field names.
+    > **TIP:** Use [ransack](../core-concepts/search-filtering.md) search syntax for filter field names.
 
 </details>
 
@@ -1445,7 +1445,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the stock transfers list filters.
 
@@ -1456,7 +1456,7 @@ Here's a list of all places you can inject your custom code:
         { data: { filters_target: :input } } %>
     ```
 
-    > **TIP:** Use [ransack](/developer/core-concepts/search-filtering) search syntax for filter field names.
+    > **TIP:** Use [ransack](../core-concepts/search-filtering.md) search syntax for filter field names.
 
 </details>
 
@@ -1758,7 +1758,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     Injects code into the products list filters. This partial has access to the `f` variable, which is the form builder for the filters.
 
@@ -1768,7 +1768,7 @@ Here's a list of all places you can inject your custom code:
     <%= f.spree_text_field :q_name_cont, data: { filters_target: :input } %>
     ```
 
-    > **TIP:** * `q_name_cont` is the name of the filter field. For filtering we're using [ransack](/developer/core-concepts/search-filtering) gem, so the name of the filter field is the name of the attribute we're filtering by.
+    > **TIP:** * `q_name_cont` is the name of the filter field. For filtering we're using [ransack](../core-concepts/search-filtering.md) gem, so the name of the filter field is the name of the attribute we're filtering by.
 >     * `data: { filters_target: :input }` is needed for the [Stimulus Filters controller](https://github.com/spree/spree/blob/main/admin/app/javascript/spree/admin/controllers/filters_controller.js) to work.
 
 </details>
@@ -1803,7 +1803,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     - **`product`** (`Spree::Product`) — The [Spree::Product](https://github.com/spree/spree/blob/main/core/app/models/spree/product.rb) object.
 
@@ -1852,7 +1852,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     - **`product`** (`Spree::Product`) — The [Spree::Product](https://github.com/spree/spree/blob/main/core/app/models/spree/product.rb) object.
 
@@ -1901,7 +1901,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     - **`shipping_method`** (`Spree::ShippingMethod`) — The [Spree::ShippingMethod](https://github.com/spree/spree/blob/main/core/app/models/spree/shipping_method.rb) object.
 
@@ -1934,7 +1934,7 @@ Here's a list of all places you can inject your custom code:
 
     #### Variables
 
-    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](/developer/admin/form-builder) object.
+    - **`f`** (`Spree::Admin::FormBuilder`) — The [Spree::Admin::FormBuilder](form-builder.md) object.
 
     - **`store`** (`Spree::Store`) — The [Spree::Store](https://github.com/spree/spree/blob/main/core/app/models/spree/store.rb) object.
 
@@ -1958,7 +1958,7 @@ Here's a list of all places you can inject your custom code:
 
 ## Related Documentation
 
-- [Admin Navigation](/developer/admin/navigation) - Add custom menu items to the admin
-- [Admin Tables](/developer/admin/tables) - Customize admin list views
-- [Form Builder](/developer/admin/form-builder) - Build admin forms with Spree's form helpers
-- [Customization Quickstart](/developer/customization/quickstart) - Overview of all customization options
+- [Admin Navigation](navigation.md) - Add custom menu items to the admin
+- [Admin Tables](tables.md) - Customize admin list views
+- [Form Builder](form-builder.md) - Build admin forms with Spree's form helpers
+- [Customization Quickstart](../customization/quickstart.md) - Overview of all customization options

package/dist/developer/admin/helper-methods.md

@@ -5,7 +5,7 @@ sidebarTitle: Helper Methods
 
 Helper methods available in the Admin Dashboard for navigation, links, and utility functions.
 
-> **INFO:** For UI components that render HTML elements (Dropdowns, Dialogs, Icons, etc.), see the [Components](/developer/admin/components) documentation.
+> **INFO:** For UI components that render HTML elements (Dropdowns, Dialogs, Icons, etc.), see the [Components](components.md) documentation.
 
 ## Navigation Helpers
 
@@ -488,7 +488,7 @@ Renders all registered partials for an injection point.
 <%= render_admin_partials(:order_page_sidebar, order: @order) %>
 ```
 
-See [Extending UI](/developer/admin/extending-ui) for more information about injection points.
+See [Extending UI](extending-ui.md) for more information about injection points.
 
 ## Preference Helpers
 

package/dist/developer/admin/navigation.md

@@ -798,8 +798,8 @@ Register with:
 
 ### Related Documentation
 
-- [Extending Admin UI](/developer/admin/extending-ui) - Learn about other UI injection points
-- [Admin Tables](/developer/admin/tables) - Customize admin list views
-- [Helper Methods](/developer/admin/helper-methods) - Explore other admin helper methods
-- [Permissions](/developer/customization/permissions) - Understand the authorization system
-- [Customization Quickstart](/developer/customization/quickstart) - Overview of all customization options
+- [Extending Admin UI](extending-ui.md) - Learn about other UI injection points
+- [Admin Tables](tables.md) - Customize admin list views
+- [Helper Methods](helper-methods.md) - Explore other admin helper methods
+- [Permissions](../customization/permissions.md) - Understand the authorization system
+- [Customization Quickstart](../customization/quickstart.md) - Overview of all customization options

package/dist/developer/admin/tables.md

@@ -485,7 +485,7 @@ Spree.admin.tables.products
 
 ## Related Documentation
 
-- [Admin Navigation](/developer/admin/navigation) - Add custom menu items to the admin
-- [Extending Admin UI](/developer/admin/extending-ui) - Inject partials into admin pages
-- [Search & Filtering](/developer/core-concepts/search-filtering) - Add searchable/filterable fields
-- [Customization Quickstart](/developer/customization/quickstart) - Overview of all customization options
+- [Admin Navigation](navigation.md) - Add custom menu items to the admin
+- [Extending Admin UI](extending-ui.md) - Inject partials into admin pages
+- [Search & Filtering](../core-concepts/search-filtering.md) - Add searchable/filterable fields
+- [Customization Quickstart](../customization/quickstart.md) - Overview of all customization options

package/dist/developer/cli/quickstart.md

@@ -4,7 +4,7 @@ sidebarTitle: Overview
 description: Manage your Spree Commerce project from the command line.
 ---
 
-The Spree CLI (`@spree/cli`) manages Docker-based Spree projects created with [create-spree-app](/developer/create-spree-app/quickstart).
+The Spree CLI (`@spree/cli`) manages Docker-based Spree projects created with [create-spree-app](../create-spree-app/quickstart.md).
 
 ## Installation
 
@@ -72,7 +72,7 @@ spree eject
 
 After ejecting, the Docker image is built from `backend/Dockerfile`. Edit files in `backend/` and run `spree dev` to rebuild and restart with your changes.
 
-See [Customizing the Backend](/developer/create-spree-app/quickstart#customizing-the-backend) for details on what you can customize.
+See [Customizing the Backend](../create-spree-app/quickstart.md#customizing-the-backend) for details on what you can customize.
 
 ### `spree logs`
 

package/dist/developer/contributing/creating-an-extension.md

@@ -5,9 +5,9 @@ description: Learn how to create a Spree extension.
 
 ## Overview
 
-[Spree Extensions](/developer/customization/extensions) are a way to add new functionality to your Spree store. They are a great way to extend the functionality of Spree and add new features. You can share them with Spree community on Github so anyone can use them, contribute back and share your improvements.
+[Spree Extensions](../customization/extensions.md) are a way to add new functionality to your Spree store. They are a great way to extend the functionality of Spree and add new features. You can share them with Spree community on Github so anyone can use them, contribute back and share your improvements.
 
-> **INFO:** This tutorial uses decorators for extending Spree models. For extensions that need to react to events (sync with external services, send notifications, etc.), consider using [Events subscribers](/developer/core-concepts/events) instead - they're easier to test and maintain. See [Customization Quickstart](/developer/customization/quickstart) for guidance on choosing the right approach.
+> **INFO:** This tutorial uses decorators for extending Spree models. For extensions that need to react to events (sync with external services, send notifications, etc.), consider using [Events subscribers](../core-concepts/events.md) instead - they're easier to test and maintain. See [Customization Quickstart](../customization/quickstart.md) for guidance on choosing the right approach.
 
 ## Getting Started
 
@@ -27,7 +27,7 @@ cd spree_simple_sales
 
 ## Adding a Sale Price to Variants
 
-The first thing we need to do is create a migration that adds a sale_price column to [variants](/developer/core-concepts/products#variants).
+The first thing we need to do is create a migration that adds a sale_price column to [variants](../core-concepts/products.md#variants).
 
 We can do this with the following command:
 
@@ -227,11 +227,11 @@ While this tutorial uses decorators to extend Spree's core behavior, modern Spre
 | Use Case | Recommended Approach |
 |----------|---------------------|
 | Structural changes (associations, validations) | Decorators (as shown in this tutorial) |
-| React to model changes | [Events subscribers](/developer/core-concepts/events) |
-| External service integration | [Webhooks](/developer/core-concepts/webhooks) |
-| Replace core services | [Dependencies injection](/developer/customization/dependencies) |
-| Add admin UI elements | [Admin Partials](/developer/admin/extending-ui) |
-| Add admin menu items | [Admin Navigation](/developer/admin/navigation) |
+| React to model changes | [Events subscribers](../core-concepts/events.md) |
+| External service integration | [Webhooks](../core-concepts/webhooks.md) |
+| Replace core services | [Dependencies injection](../customization/dependencies.md) |
+| Add admin UI elements | [Admin Partials](../admin/extending-ui.md) |
+| Add admin menu items | [Admin Navigation](../admin/navigation.md) |
 
 For example, if your extension needs to sync data with an external service when products are updated, use an Events subscriber instead of a decorator callback:
 
@@ -252,7 +252,7 @@ end
 
 ## Related Documentation
 
-- [Events](/developer/core-concepts/events) - Subscribe to Spree events
-- [Webhooks](/developer/core-concepts/webhooks) - HTTP callbacks for external integrations
-- [Dependencies](/developer/customization/dependencies) - Replace core services
-- [Customization Quickstart](/developer/customization/quickstart) - Choose the right approach
+- [Events](../core-concepts/events.md) - Subscribe to Spree events
+- [Webhooks](../core-concepts/webhooks.md) - HTTP callbacks for external integrations
+- [Dependencies](../customization/dependencies.md) - Replace core services
+- [Customization Quickstart](../customization/quickstart.md) - Choose the right approach

package/dist/developer/contributing/quickstart.md

@@ -21,7 +21,7 @@ To find issues you can tackle on we recommend visiting [Spree Contribute page](h
 
 ## Creating a Spree extension
 
-Extensions provide additional features and integrations for your Spree store. You can create your own and share with the rest of the community. Before doing so please check our [Extension directory](/developer/customization/extensions) if your desired extension does not exist already. If not [follow Extensions tutorial](../contributing/extensions_tutorial) to learn how to create one.
+Extensions provide additional features and integrations for your Spree store. You can create your own and share with the rest of the community. Before doing so please check our [Extension directory](../customization/extensions.md) if your desired extension does not exist already. If not [follow Extensions tutorial](../contributing/extensions_tutorial) to learn how to create one.
 
 ## Helping others on Spree slack