@spree/docs 0.1.0 → 0.1.2

package/dist/developer/tutorial/admin.md

@@ -83,7 +83,7 @@ Spree.admin.tables.brands.add :description,
   position: 15
 ```
 
-> **INFO:** For complete table customization options including column types, filtering, sorting, and bulk actions, see the [Admin Tables](/developer/admin/tables) guide.
+> **INFO:** For complete table customization options including column types, filtering, sorting, and bulk actions, see the [Admin Tables](../admin/tables.md) guide.
 
 ## Step 3: Customize Navigation
 
@@ -131,4 +131,4 @@ end
 
 After restarting your server, you'll see the new "Brands" navigation link in the admin sidebar!
 
-> **INFO:** For complete navigation API documentation including all available options, submenu creation, badges, and more, see the [Admin Navigation](/developer/admin/navigation) guide.
+> **INFO:** For complete navigation API documentation including all available options, submenu creation, badges, and more, see the [Admin Navigation](../admin/navigation.md) guide.

package/dist/developer/tutorial/extending-models.md

@@ -5,7 +5,7 @@ description: Learn how to extend Spree's core models to connect Brands with Prod
 
 In this tutorial, we'll connect our custom Brand model with Spree's core Product model. This is a common pattern when building features that need to integrate with existing Spree functionality.
 
-> **INFO:** This guide assumes you've completed the [Model](/developer/tutorial/model), [Admin](/developer/tutorial/admin), and [File Uploads](/developer/tutorial/file-uploads) tutorials.
+> **INFO:** This guide assumes you've completed the [Model](model.md), [Admin](admin.md), and [File Uploads](file-uploads.md) tutorials.
 
 ## What We're Building
 
@@ -24,12 +24,12 @@ Before extending Spree models, consider which approach fits your needs best:
 | Add association (belongs_to, has_many) | **Decorator** (this tutorial) |
 | Add validation or scope | **Decorator** |
 | Add new instance/class method | **Decorator** |
-| React to model changes (after save, etc.) | [Events subscriber](/developer/core-concepts/events) |
-| Sync with external service on changes | [Events](/developer/core-concepts/events) or [Webhooks](/developer/core-concepts/webhooks) |
-| Add searchable/filterable field | [Ransack configuration](/developer/core-concepts/search-filtering#extending-ransackable-configuration) |
-| Add admin UI elements | [Admin Partials](/developer/admin/extending-ui) |
+| React to model changes (after save, etc.) | [Events subscriber](../core-concepts/events.md) |
+| Sync with external service on changes | [Events](../core-concepts/events.md) or [Webhooks](../core-concepts/webhooks.md) |
+| Add searchable/filterable field | [Ransack configuration](../core-concepts/search-filtering.md#extending-ransackable-configuration) |
+| Add admin UI elements | [Admin Partials](../admin/extending-ui.md) |
 
-> **INFO:** This tutorial uses **decorators** because we're adding a structural association between models. For behavioral changes like callbacks, prefer [Events](/developer/core-concepts/events) instead - they're easier to test and maintain.
+> **INFO:** This tutorial uses **decorators** because we're adding a structural association between models. For behavioral changes like callbacks, prefer [Events](../core-concepts/events.md) instead - they're easier to test and maintain.
 
 ## Understanding Decorators
 
@@ -267,7 +267,7 @@ end
 
 #### Adding Callbacks
 
-> **WARNING:** For callbacks that trigger side effects (syncing to external services, sending notifications, etc.), use [Events subscribers](/developer/core-concepts/events) instead of decorator callbacks. Events are easier to test and won't break during Spree upgrades.
+> **WARNING:** For callbacks that trigger side effects (syncing to external services, sending notifications, etc.), use [Events subscribers](../core-concepts/events.md) instead of decorator callbacks. Events are easier to test and won't break during Spree upgrades.
 
 **Decorator approach** (use only for simple, internal logic):
 
@@ -343,7 +343,7 @@ module Spree
 end
 ```
 
-> **INFO:** SEO features like slugs, meta titles, and FriendlyId are covered in the [SEO](/developer/tutorial/seo) tutorial.
+> **INFO:** SEO features like slugs, meta titles, and FriendlyId are covered in the [Slugs](../core-concepts/slugs.md) documentation.
 
 ### Spree Initializer Additions
 
@@ -371,10 +371,10 @@ Spree::PermittedAttributes.product_attributes << :brand_id
 
 ## Related Documentation
 
-- [Model Tutorial](/developer/tutorial/model) - Creating the Brand model
-- [Admin Tutorial](/developer/tutorial/admin) - Building the admin interface
-- [Events](/developer/core-concepts/events) - Subscribe to model changes without decorators
-- [Webhooks](/developer/core-concepts/webhooks) - HTTP callbacks for external integrations
-- [Decorators](/developer/customization/decorators) - Full decorator reference
-- [Customization Overview](/developer/customization/quickstart) - More customization patterns
-- [Products](/developer/core-concepts/products) - Product model documentation
+- [Model Tutorial](model.md) - Creating the Brand model
+- [Admin Tutorial](admin.md) - Building the admin interface
+- [Events](../core-concepts/events.md) - Subscribe to model changes without decorators
+- [Webhooks](../core-concepts/webhooks.md) - HTTP callbacks for external integrations
+- [Decorators](../customization/decorators.md) - Full decorator reference
+- [Customization Overview](../customization/quickstart.md) - More customization patterns
+- [Products](../core-concepts/products.md) - Product model documentation

package/dist/developer/tutorial/file-uploads.md

@@ -3,7 +3,7 @@ title: File Uploads
 description: Learn how to add file uploads to the Brands feature
 ---
 
-> **INFO:** This guide assumes you've completed the [Model](/developer/tutorial/model), [Admin](/developer/tutorial/admin), and [Rich Text](/developer/tutorial/rich-text) tutorials.
+> **INFO:** This guide assumes you've completed the [Model](model.md), [Admin](admin.md), and [Rich Text](rich-text.md) tutorials.
 
 In this tutorial, we'll add a logo image upload to our Brand model. Spree uses [Rails Active Storage](https://guides.rubyonrails.org/active_storage_overview.html) for handling file attachments, image processing, and storage.
 

package/dist/developer/tutorial/introduction.md

@@ -20,14 +20,14 @@ To fully implement a new feature, you will typically create the following compon
 ## Tutorial Sections
 
 
-  - [1. Model](/developer/tutorial/model) — Create the Brand model with migrations, validations, and associations
-  - [2. Admin Dashboard](/developer/tutorial/admin) — Build admin interface for managing brands
-  - [3. Rich Text](/developer/tutorial/rich-text) — Add rich text descriptions using Action Text
-  - [4. File Uploads](/developer/tutorial/file-uploads) — Add logo images with Active Storage
-  - [5. Extending Core Models](/developer/tutorial/extending-models) — Connect Brands to Products using associations
-  - [7. Testing](/developer/tutorial/testing) — Write automated tests for your feature
+  - [1. Model](model.md) — Create the Brand model with migrations, validations, and associations
+  - [2. Admin Dashboard](admin.md) — Build admin interface for managing brands
+  - [3. Rich Text](rich-text.md) — Add rich text descriptions using Action Text
+  - [4. File Uploads](file-uploads.md) — Add logo images with Active Storage
+  - [5. Extending Core Models](extending-models.md) — Connect Brands to Products using associations
+  - [7. Testing](testing.md) — Write automated tests for your feature
 
 
 ## Example: Building a Brands Feature
 
-In this guide we will create a complete "Brands" feature that allows admins to manage [Product](/developer/core-concepts/products) brands.
+In this guide we will create a complete "Brands" feature that allows admins to manage [Product](../core-concepts/products.md) brands.

package/dist/developer/tutorial/rich-text.md

@@ -3,7 +3,7 @@ title: Rich Text
 description: Learn how to add rich text content to the Brands feature using Action Text
 ---
 
-> **INFO:** This guide assumes you've completed the [Model](/developer/tutorial/model) and [Admin](/developer/tutorial/admin) tutorials.
+> **INFO:** This guide assumes you've completed the [Model](model.md) and [Admin](admin.md) tutorials.
 
 Our Brand model has a `name` attribute to store the brand name. However it's missing a description. That's because we're going to use [Action Text](https://guides.rubyonrails.org/action_text_overview.html) to handle the rich text content.
 

package/dist/developer/tutorial/testing.md

@@ -4,7 +4,7 @@ Automated testing is a crucial part of the development process. It helps you ens
 Spree uses [RSpec](https://rspec.info), [Factory Bot](https://github.com/thoughtbot/factory_bot_rails), and [Capybara](https://github.com/teamcapybara/capybara) for testing.
 We also provide the `spree_dev_tools` gem that helps you write Spree-specific tests.
 
-> **INFO:** This guide assumes you've completed all previous tutorials through [Page Builder](/developer/tutorial/page-builder). You should have a complete `Spree::Brand` model with admin, storefront, and SEO features.
+> **INFO:** This guide assumes you've completed all previous tutorials through [Extending Models](extending-models.md). You should have a complete `Spree::Brand` model with admin features.
 
 ## Setup
 
@@ -163,7 +163,7 @@ end
 
 ### Testing Decorators
 
-When you extend core Spree models with decorators (see [Extending Core Models](/developer/tutorial/extending-models)), test the added functionality:
+When you extend core Spree models with decorators (see [Extending Core Models](extending-models.md)), test the added functionality:
 
 ```ruby spec/models/spree/product_decorator_spec.rb
 require 'rails_helper'
@@ -318,61 +318,6 @@ RSpec.describe Spree::Admin::BrandsController, type: :controller do
 end
 ```
 
-### Storefront Controller Tests
-
-```ruby spec/controllers/spree/brands_controller_spec.rb
-require 'rails_helper'
-
-RSpec.describe Spree::Brand, type: :model do
-  describe 'associations' do
-    it 'has many products' do
-      association = described_class.reflect_on_association(:products)
-      expect(association.macro).to eq(:has_many)
-      expect(association.class_name).to eq('Spree::Product')
-    end
-  end
-
-  describe 'validations' do
-    it 'validates presence of name' do
-      brand = build(:brand, name: nil)
-      expect(brand).not_to be_valid
-      expect(brand.errors[:name]).to include("can't be blank")
-    end
-
-    describe 'slug uniqueness' do
-      let!(:existing_brand) { create(:brand, slug: 'nike') }
-
-      it 'validates uniqueness of slug' do
-        brand = build(:brand, slug: 'nike')
-        expect(brand).not_to be_valid
-        expect(brand.errors[:slug]).to include('has already been taken')
-      end
-    end
-  end
-
-  describe 'FriendlyId' do
-    it 'generates slug from name' do
-      brand = create(:brand, name: 'Nike Sportswear', slug: nil)
-      expect(brand.slug).to eq('nike-sportswear')
-    end
-
-    it 'handles duplicate names by appending UUID' do
-      create(:brand, name: 'Nike', slug: 'nike')
-      brand = create(:brand, name: 'Nike', slug: nil)
-      expect(brand.slug).to match(/nike-[a-f0-9-]+/)
-    end
-  end
-
-  describe '#image' do
-    let(:brand) { create(:brand, :with_logo) }
-
-    it 'returns logo as image for Open Graph' do
-      expect(brand.image).to eq(brand.logo)
-    end
-  end
-end
-```
-
 ## Writing Feature Tests
 
 Feature tests (also called system tests) simulate real user interactions using Capybara.
@@ -547,10 +492,9 @@ spec/
 
 ## Related Documentation
 
-* [Model Tutorial](/developer/tutorial/model) - Creating the Brand model
-* [Admin Tutorial](/developer/tutorial/admin) - Building the admin interface
-* [Extending Core Models](/developer/tutorial/extending-models) - Connecting Brands to Products
-* [Storefront Tutorial](/developer/tutorial/storefront) - Creating storefront pages
+* [Model Tutorial](model.md) - Creating the Brand model
+* [Admin Tutorial](admin.md) - Building the admin interface
+* [Extending Core Models](extending-models.md) - Connecting Brands to Products
 * [RSpec Documentation](https://rspec.info/documentation/) - Official RSpec docs
 * [Factory Bot Documentation](https://github.com/thoughtbot/factory_bot/blob/main/GETTING_STARTED.md) - Factory Bot guide
 

package/dist/developer/upgrades/3.7-to-4.0.md

@@ -112,7 +112,7 @@ end
 Spree::Base.singleton_class.send :prepend, Spree::BaseDecorator
 ```
 
-Please also consider other options for [Logic Customization](/developer/customization).
+Please also consider other options for [Logic Customization](../customization.md).
 
 We recommend also reading through [Ruby modules: Include vs Prepend vs Extend](https://medium.com/@leo_hetsch/ruby-modules-include-vs-prepend-vs-extend-f09837a5b073)
 

package/dist/developer/upgrades/4.0-to-4.1.md

@@ -55,7 +55,7 @@ To replace your current frontend with the new Spree UI follow these steps:
 3. Next, you will need to copy over two files:
    * [spree_storefront.rb](https://raw.githubusercontent.com/spree/spree/main/core/lib/generators/spree/install/templates/config/initializers/spree_storefront.rb) to `config/initializers/spree_storefront.rb`
    * [spree_storefront.yml](https://raw.githubusercontent.com/spree/spree/main/core/lib/generators/spree/install/templates/config/spree_storefront.yml) to `config/spree_storefront.yml`
-4. If you overwrote any `spree_frontend` [controllers](https://github.com/spree/spree/tree/master/frontend/app/controllers) you will need to either remove your local copies or move your custom logic to [decorators](/developer/customization#extending-controllers)
+4. If you overwrote any `spree_frontend` [controllers](https://github.com/spree/spree/tree/master/frontend/app/controllers) you will need to either remove your local copies or move your custom logic to [decorators](../customization.md#extending-controllers)
 5. The same goes for [helpers](https://github.com/spree/spree/tree/master/frontend/app/helpers/spree)
 6. You will also need to remove this line:
 

package/dist/developer/upgrades/4.10-to-5.0.md

@@ -3,7 +3,7 @@ title: Upgrading to Spree 5.0
 description: This guide covers upgrading a Spree 4.10 application to Spree 5.0.
 ---
 
-> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 4.10](/developer/upgrades/4.9-to-4.10)
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 4.10](4.9-to-4.10.md)
 
 Spree 5.0 is a major upgrade that introduces many breaking changes. The major changes are:
 

package/dist/developer/upgrades/4.5-to-4.6.md

@@ -26,7 +26,7 @@ If your application used the spree_globalize extension, you can remove it from y
 
 We've configured Mobility to use [a strategy that uses a separate table to store translations](https://dejimata.com/2017/3/3/translating-with-mobility#strategy-2), just like how spree_globalize did. This means, you won't need to make any changes to the database structure or migrate data.
 
-During the upgrade process, you may need to review your custom queries that rely on translations, as there are minor differences in how Mobility handles them. Spree 4.6 includes a few [built-in concerns](/developer/core-concepts/translations#resource-translations-implementation) to make it easier to work with translatable models.
+During the upgrade process, you may need to review your custom queries that rely on translations, as there are minor differences in how Mobility handles them. Spree 4.6 includes a few [built-in concerns](../core-concepts/translations.md#resource-translations-implementation) to make it easier to work with translatable models.
 
 Run the following command to remove spree_globalize from your Gemfile:
 
@@ -68,7 +68,7 @@ bin/rails g spree:frontend:install
 
 ### Update migrations for translation tables with additional columns
 
-If you want to translate more fields in [translated resources](/developer/core-concepts/translations#resource-translations), you have to alter copied migrations or add new ones.
+If you want to translate more fields in [translated resources](../core-concepts/translations.md#resource-translations), you have to alter copied migrations or add new ones.
 We're using the [Spree::TranslationMigrations](https://github.com/spree/spree/blob/main/core/lib/spree/translation_migrations.rb) to help with migrating data.
 
 ### Add or update the behavior of the translated model
@@ -80,7 +80,7 @@ If you overwrote Spree models in your application, you have to define this block
 - `Spree::TranslatableResource` - required for all translated models
 - `Spree::TranslatableResourceSlug` - required for translated models with slugs/permalinks
 
-[Read more](/developer/core-concepts/translations#resource-translations-implementation) how Spree handles resource translations.
+[Read more](../core-concepts/translations.md#resource-translations-implementation) how Spree handles resource translations.
 
 ### Generating slugs with `friendly_id`
 
@@ -92,7 +92,7 @@ Currently, it's not possible to translate encrypted data. If you're already encr
 
 ### Full text search with pg_search scopes
 
-If you use the [pg_search](https://github.com/Casecommons/pg_search) for the full text search in [translated resources](/developer/core-concepts/translations#resource-translations), you need to move your scopes to the translated model, eg. from the `Spree::Product` to the `Spree::Product::Translation`. 
+If you use the [pg_search](https://github.com/Casecommons/pg_search) for the full text search in [translated resources](../core-concepts/translations.md#resource-translations), you need to move your scopes to the translated model, eg. from the `Spree::Product` to the `Spree::Product::Translation`. 
 
 If you still want to have the original scope, you need to rewrite it, from:
 

package/dist/developer/upgrades/4.8-to-4.9.md

@@ -3,7 +3,7 @@ title: Upgrading to Spree 4.9
 description: This guide covers upgrading a Spree 4.8 application to Spree 4.9.
 ---
 
-> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 4.8](/developer/upgrades/4.x-to-4.8)
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 4.8](4.x-to-4.8.md)
 
 ## Upgrade steps
 

package/dist/developer/upgrades/4.9-to-4.10.md

@@ -3,7 +3,7 @@ title: Upgrading to Spree 4.10
 description: This guide covers upgrading a Spree 4.9 application to Spree 4.10.
 ---
 
-> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 4.9](/developer/upgrades/4.8-to-4.9)
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 4.9](4.8-to-4.9.md)
 
 ## Upgrade steps
 

package/dist/developer/upgrades/5.0-to-5.1.md

@@ -3,7 +3,7 @@ title: Upgrading to Spree 5.1
 description: This guide covers upgrading a Spree 5.0 application to Spree 5.1.
 ---
 
-> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.0](/developer/upgrades/4.10-to-5.0)
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.0](4.10-to-5.0.md)
 
 ## Upgrade steps
 

package/dist/developer/upgrades/5.1-to-5.2.md

@@ -3,7 +3,7 @@ title: Upgrading to Spree 5.2
 description: This guide covers upgrading a Spree 5.1 application to Spree 5.2.
 ---
 
-> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.1](/developer/upgrades/5.0-to-5.1)
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.1](5.0-to-5.1.md)
 
 ## Upgrade steps
 
@@ -33,7 +33,7 @@ bin/rake spree:install:migrations && bin/rails db:migrate
 
 ### Migrate to Metafields or keep using Product Properties
 
-Spree 5.2 introduces [Metafields](/developer/core-concepts/metafields), which are a new way to store additional information about an object. Previously, we used Product Properties to enrich products. Metafields are more powerful, more flexible and can be attached to any object not just products.
+Spree 5.2 introduces [Metafields](../core-concepts/metafields.md), which are a new way to store additional information about an object. Previously, we used Product Properties to enrich products. Metafields are more powerful, more flexible and can be attached to any object not just products.
 
 However we now that properties were available in Spree since it's beginning. So we decided to keep them for backward compatibility until Spree 6.0 to give you time to migrate to metafields.
 

package/dist/developer/upgrades/5.2-to-5.3.md

@@ -3,7 +3,7 @@ title: Upgrading to Spree 5.3
 description: This guide covers upgrading a Spree 5.2 application to Spree 5.3.
 ---
 
-> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.2](/developer/upgrades/5.1-to-5.2)
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.2](5.1-to-5.2.md)
 
 ## Upgrade steps
 
@@ -263,7 +263,7 @@ Spree.admin.tables.orders.add :vendor,
   partial: 'spree/admin/orders/table/vendor_column'
 ```
 
-See the [Admin Tables documentation](/developer/admin/tables) for more details.
+See the [Admin Tables documentation](../admin/tables.md) for more details.
 
 ### Tailwind CSS v4 Migration
 

package/dist/developer/upgrades/5.3-to-5.4.md

@@ -3,7 +3,7 @@ title: Upgrading to Spree 5.4
 description: This guide covers upgrading a Spree 5.3 application to Spree 5.4.
 ---
 
-> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.3](/developer/upgrades/5.2-to-5.3)
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.3](5.2-to-5.3.md)
 
 ## Upgrade steps
 
@@ -93,7 +93,7 @@ Prefix length isn't limited by default, but we recommend to keep it short.
 
 ### Migrate Checkout Zones to Markets
 
-Spree 5.4 introduces [Markets](/developer/core-concepts/markets) as the primary way to manage which countries are available for checkout, along with their currencies and locales. The legacy `checkout_zone` field on the Store model is now deprecated and will be removed in Spree 5.5.
+Spree 5.4 introduces [Markets](../core-concepts/markets.md) as the primary way to manage which countries are available for checkout, along with their currencies and locales. The legacy `checkout_zone` field on the Store model is now deprecated and will be removed in Spree 5.5.
 
 New stores automatically get a default market created from their `default_country` — no manual setup needed. For existing stores that used `checkout_zone`, run the migration rake task:
 
@@ -114,8 +114,8 @@ The following Store methods now emit deprecation warnings and will be removed in
 
 | Deprecated method | Replacement |
 |---|---|
-| `store.checkout_zone` | Use [Markets](/developer/core-concepts/markets) to manage countries |
-| `store.checkout_zone=` | Use [Markets](/developer/core-concepts/markets) to manage countries |
+| `store.checkout_zone` | Use [Markets](../core-concepts/markets.md) to manage countries |
+| `store.checkout_zone=` | Use [Markets](../core-concepts/markets.md) to manage countries |
 
 The `store.default_country` reader now returns the first country (by name) from the store's default market. The `store.default_country_iso=` setter still works and is used to set the country when creating a store — a default market is automatically created from it.
 
@@ -235,7 +235,7 @@ If you rely on these features please run:
 
 ### (Optional) Install Legacy Product Properties
 
-Product Properties have been extracted from Spree core to a separate gem `spree_legacy_product_properties`. Product Properties were already deprecated in favor of [Metafields](/developer/core-concepts/metafields) and disabled by default since Spree 5.1.
+Product Properties have been extracted from Spree core to a separate gem `spree_legacy_product_properties`. Product Properties were already deprecated in favor of [Metafields](../core-concepts/metafields.md) and disabled by default since Spree 5.1.
 
 If you have `product_properties_enabled: true` in your Spree configuration or rely on Product Properties in any way, install the extension:
 

package/dist/developer/upgrades/quickstart.md

@@ -31,6 +31,6 @@ New features, will likely contain API changes. The difference between Spree mino
 
 ## Security
 
-Our Security policy is [described here](/developer/security).
+Our Security policy is [described here](../security.md).
 
 When a release series is no longer supported, it's your own responsibility to deal with bugs and security issues. We may provide backports of some critical security fixes.

package/dist/integrations/integrations.md

@@ -7,33 +7,33 @@ description: "Learn how to connect your Spree application to third-party service
 ## Payments
 
 
-  - [Stripe](/integrations/payments/stripe) — Stripe is a popular payment gateway that allows you to accept payments from your customers. Credit cards, wallets, buy-now-pay-later, installment payments and more.
-  - [Adyen](/integrations/payments/adyen) — Adyen is a global payment platform that enables businesses to accept payments across multiple channels and markets. Credit cards, digital wallets, BNPL, local payment methods, and more across 150+ currencies.
-  - [PayPal](/integrations/payments/paypal) — PayPal is an online payment system that allows you to send and receive money around the world. You can link your credit card, debit card, or bank account. You can also set up a PayPal Balance account.
-  - [RazorPay](/integrations/payments/razorpay) — Razorpay is a secure payment gateway that enables businesses to accept online payments via cards, UPI, net banking, and wallets. It also supports international transactions across multiple currencies.
+  - [Stripe](payments/stripe.md) — Stripe is a popular payment gateway that allows you to accept payments from your customers. Credit cards, wallets, buy-now-pay-later, installment payments and more.
+  - [Adyen](payments/adyen.md) — Adyen is a global payment platform that enables businesses to accept payments across multiple channels and markets. Credit cards, digital wallets, BNPL, local payment methods, and more across 150+ currencies.
+  - [PayPal](payments/paypal.md) — PayPal is an online payment system that allows you to send and receive money around the world. You can link your credit card, debit card, or bank account. You can also set up a PayPal Balance account.
+  - [RazorPay](payments/razorpay.md) — Razorpay is a secure payment gateway that enables businesses to accept online payments via cards, UPI, net banking, and wallets. It also supports international transactions across multiple currencies.
 
 
 ## Search
 
 
-  - [Meilisearch](/integrations/search/meilisearch) — One platform to build, scale, and unify search and AI retrieval. Search-as-you-type returns answers in less than 50 milliseconds. That's faster than the blink of an eye!
+  - [Meilisearch](search/meilisearch.md) — One platform to build, scale, and unify search and AI retrieval. Search-as-you-type returns answers in less than 50 milliseconds. That's faster than the blink of an eye!
 
 
 ## Analytics
 
 
-  - [Google Analytics 4](/integrations/analytics/google-analytics) — Google Analytics 4 is a powerful analytics tool that allows you to track user behavior, sales performance, and marketing effectiveness across your store.
-   - [Google Tag Manager](/integrations/analytics/google-tag-manager) — Google Tag Manager is a flexible tag management tool that lets you deploy and control marketing, analytics, and tracking scripts across your store.
+  - [Google Analytics 4](analytics/google-analytics.md) — Google Analytics 4 is a powerful analytics tool that allows you to track user behavior, sales performance, and marketing effectiveness across your store.
+   - [Google Tag Manager](analytics/google-tag-manager.md) — Google Tag Manager is a flexible tag management tool that lets you deploy and control marketing, analytics, and tracking scripts across your store.
 
 
 ## Marketing
 
 
-  - [Klaviyo](/integrations/marketing/klaviyo) — Klaviyo is a marketing automation platform that allows you to send email campaigns to your customers.
+  - [Klaviyo](marketing/klaviyo.md) — Klaviyo is a marketing automation platform that allows you to send email campaigns to your customers.
 
 
 ## SSO, MFA & Social Login
 
 
-  - [Admin Panel SSO & MFA](/integrations/sso-mfa-social-login/admin-dashboard) — Learn how to secure your Spree admin panel with SSO and MFA integration, using Microsoft Entra ID as an example.
-  - [Storefront SSO & Social Login](/integrations/sso-mfa-social-login/storefront) — Enable customer-facing SSO and social login on your Spree storefront, using Microsoft Entra External ID as an example.
+  - [Admin Panel SSO & MFA](sso-mfa-social-login/admin-dashboard.md) — Learn how to secure your Spree admin panel with SSO and MFA integration, using Microsoft Entra ID as an example.
+  - [Storefront SSO & Social Login](sso-mfa-social-login/storefront.md) — Enable customer-facing SSO and social login on your Spree storefront, using Microsoft Entra External ID as an example.

package/dist/integrations/payments/adyen.md

@@ -65,7 +65,7 @@ Spree's native Adyen integration supports a comprehensive range of features and
 
 - Support for 3D Secure and other security standards
 - Support for off-session payments
-- Support for Storefront API integration (see the API docs [here](/api-reference/storefront/adyen/create-an-adyen-payment-session))
+- Support for Storefront API integration (see the API docs [here](../../api-reference/storefront/adyen/create-an-adyen-payment-session.md))
 - Accept payments in over 150 currencies
 - Accept Credit Cards, Debit Cards, and Digital Wallets
 - Accept Buy Now, Pay Later (BNPL) payments

package/dist/integrations/search/meilisearch.md

@@ -232,5 +232,5 @@ For production deployments, consider [Meilisearch Cloud](https://www.meilisearch
 
 ## Related Documentation
 
-- [Search & Filtering](/developer/core-concepts/search-filtering) — Store API search reference
-- [Search Providers](/developer/how-to/custom-search-provider) — Architecture and custom providers
+- [Search & Filtering](../../developer/core-concepts/search-filtering.md) — Store API search reference
+- [Search Providers](../../developer/how-to/custom-search-provider.md) — Architecture and custom providers

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spree/docs",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Spree Commerce developer documentation for AI agents and local reference",
   "type": "module",
   "license": "CC-BY-4.0",
@@ -15,12 +15,17 @@
     "url": "https://github.com/spree/spree/issues"
   },
   "files": [
-    "dist/**/*.md"
+    "dist/**/*.md",
+    "dist/**/*.yaml"
   ],
   "scripts": {
     "build": "node scripts/build.js",
+    "test": "vitest run",
     "clean": "rm -rf dist"
   },
+  "devDependencies": {
+    "vitest": "^4.0.18"
+  },
   "engines": {
     "node": ">=18.0.0"
   }