@spree/docs 0.1.0

package/dist/integrations/payments/paypal.md

@@ -0,0 +1,41 @@
+---
+title: "Connect PayPal payments to Spree Commerce"
+sidebarTitle: PayPal
+description: "Learn how to set up and manage Spree's native PayPal integration."
+---
+
+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.
+
+## Installation
+
+Before you can enable PayPal, it must be installed. To do so, you need to run the following command:
+
+```bash
+bundle add spree_paypal_checkout && bundle exec rails g spree_paypal_checkout:install
+```
+
+After that, you need to make sure to restart the server.
+
+## Connect PayPal
+
+Sign in to your Spree admin dashboard and navigate to **Settings → Payments**.
+
+![](/images/integrations/paypal/paypal_payment_method_list.png)
+
+Find PayPal under Available Payment Methods and click **Add**.
+
+This will redirect you to the PayPal setup form.
+
+![](/images/integrations/paypal/paypal_form.png)
+
+You will need Client ID and Client Secret from your [PayPal dashboard credentials page](https://www.paypal.com/mep/merchantapps/setup/checkout/apicredentials). 
+
+> **TIP:** To get your credentials, go to `Business Tools`, select `Online Checkout`, click `Get Started`, select `Have a custom-built site? -> Get Started`, `PayPal Checkout -> Get Started`.
+
+![](/images/integrations/paypal/paypal_credentials.png)
+
+You should see your live and sandbox credentials. Copy API key into `Client ID` and Secret into `Client Secret`.
+
+If you wish to test the PayPal payments before going live, copy sandbox credentials and select `Test Mode` option in Spree.
+
+Click **Create** to enable PayPal as a payment method on your store.

package/dist/integrations/payments/razorpay.md

@@ -0,0 +1,45 @@
+---
+title: "Connect Razorpay payments to Spree Commerce"
+sidebarTitle: Razorpay
+description: "Configuring Razorpay in Your Spree Store: A Setup & Management Walkthrough."
+---
+
+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.
+
+> **INFO:** Razorpay integration is maintained and developed by [Umesh Ravani](https://github.com/umeshravani).
+> 
+>   To support this development, please star the [GitHub repository](https://github.com/umeshravani/spree_razorpay) ❤️
+
+## Installation
+
+Before you can enable Razorpay, it must be installed. To do so, you need to add this line in Gemfile:
+
+```bash
+bundle add spree_razorpay_checkout && bundle exec rails g spree_razorpay_checkout:install
+```
+
+After that, you need to make sure to restart the server.
+
+## Connect Razorpay
+
+Sign in to your Spree admin dashboard and navigate to **Settings → Payments**.
+
+![](/images/integrations/razorpay/razorpay_payment_method_list.png)
+
+Find Razorpay under Available Payment Methods and click **Add**.
+
+This will redirect you to the Razorpay setup form.
+
+![](/images/integrations/razorpay/razorpay_form.png)
+
+You will need Key and Key Secret from your [Razorpay dashboard credentials page](https://dashboard.razorpay.com/app/website-app-settings/api-keys). 
+
+> **TIP:** To get your credentials, Navigate to Account & Settings → API Keys (under Website and app settings) → Generate new key to generate key for the selected mode.
+
+![](/images/integrations/razorpay/razorpay_credentials.png)
+
+You should see your live and test credentials. Copy both API key into `Key` and Secret into `Key Secret`, also Test API key into `Test Key` and Test Key Secret into `Test Key Secret`
+
+If you wish to test the Razorpay payments before going live, just select `Test Mode` option in Spree.
+
+Click **Create** to enable Razorpay as a payment method on your store.

package/dist/integrations/payments/stripe.md

@@ -0,0 +1,109 @@
+---
+title: "Connect Stripe payments to Spree Commerce"
+sidebarTitle: Stripe
+description: "Learn how to set up and manage Spree's native Stripe integration."
+---
+
+Stripe is a widely used payment processor that enables secure and seamless transactions for online businesses. It supports multiple payment methods, automates payouts, and ensures a smooth checkout experience for customers.
+
+> **TIP:** In [Spree Enterprise Edition](https://spreecommerce.org/pricing/), Stripe can also be used to power marketplace payments, enabling automated vendor payouts, split payments, and secure transaction handling.
+
+## Installation
+
+Before you can enable Stripe, it must be installed. To do so, you need to run the following command:
+
+```bash
+bundle add spree_stripe && bundle exec rails g spree_stripe:install
+```
+
+After that, you need to make sure to restart the server.
+
+## Connect Stripe
+
+Sign in to your Spree admin dashboard and navigate to **Settings → Payments**.
+
+![](/images/integrations/stripe/1.get_started.png)
+
+Find Stripe under Available Payment Methods and click **Add**.
+
+This will redirect you to the Stripe setup form.
+
+![](/images/integrations/stripe/2.setup_form.png)
+
+Simply copy and paste the **Publishable Key** and **Secret Key** from your Stripe dashboard into their respective fields and click **Create** to enable Stripe as a payment method on your store.
+
+> **NOTE:** The **Publishable Key** and **Secret Key** can be found in the Get Started section of the Home screen in your Stripe dashboard. Alternatively, they can be found out in **Developers → API Keys**.
+
+![](/images/integrations/stripe/3.stripe_enabled.png)
+
+### Additional Settings
+
+![](/images/integrations/stripe/4.additional_settings.png)
+
+You can optionally configure the following settings for your Stripe payment method:
+
+- **Name**: Customize the display name shown for this payment method on the storefront.
+- **Display**: Choose where Stripe should be available:
+  - Storefront only
+  - Admin panel only
+  - Both (recommended)
+- **Auto Capture**: Decide whether payments should be automatically captured at the time of authorization (recommended), or manually captured later.
+- **Active Status**: Enable or disable the payment method. Inactive methods are hidden from checkout but not removed.
+
+### Enable Apple Pay
+
+To enable Apple Pay (including Apple Pay quick checkout) as a payment method, follow these steps:
+
+1. Find ‘payment method domains’ in your Stripe dashboard
+2. Click ‘Add new domain’ and enter your store’s domain
+3. Click ‘Download file’ and attach it using the ‘Choose file’ button in Spree
+4. Click ‘Update’ at the bottom of the page
+5. Click ‘Verify’ to verify the file was uploaded correctly
+
+### Test Mode
+
+If you'd like to test your checkout flow without processing real payments, Stripe's test mode is a safe and effective way to simulate transactions. To enable it, simply switch your Stripe dashboard to **Test mode** and paste the corresponding **test API keys** into the payment method settings in Spree.
+
+## Features
+
+Spree’s native Stripe integration supports a wide range of features and payment methods to help you offer a fast, secure, and flexible checkout experience:
+
+- Support for quick checkout using Apple Pay, Google Pay, Stripe Link
+- Support for 3D Secure and other security standards
+- Support for off-session payments
+- Support for Storefront API integration (see the API docs here).
+- Accept payments in over 130 currencies
+- Accept Credit Cards, Apple Pay, Google Pay, and more
+- Accept SEPA Direct Debit payments
+- Accept iDEAL payments
+- Accept SOFORT payments
+- Accept Bancontact payments
+- Accept Alipay payments
+- Accept WeChat Pay payments
+- Accept Afterpay, Klarna, Affirm, and more
+
+### Storefront Display
+
+Spree’s Stripe integration enhances the customer experience with dynamic, context-aware payment options across the storefront:
+
+- Installment (BNPL) payments indicator on PDP (Product Detail Page)
+  ![Spree_x_Stripe\_-\_BNPL_Installment_payments_Product_Card_PDP_Product_Detail_Page](https://vendo-production-res.cloudinary.com/image/upload/w_2000/q_auto/v1742983146/docs/github/Spree_x_Stripe_-_BNPL_Installment_payments_Product_Card_PDP_Product_Detail_Page_amhfkw.jpg)
+- Quick payment options on the cart (Apple Pay, Google Pay, Link)
+  ![Apple_Pay_Google_Pay_Link\_-\_Quick_payment_options_on_the_cart](https://vendo-production-res.cloudinary.com/image/upload/w_2000/q_auto/v1742930027/docs/github/Spree_x_Stripe_-_Apple_Pay_Google_Pay_Link_-_Quick_payment_options_on_the_cart_aw45x9.jpg)
+- Quick payments bypassing checkout 1st step (Apple Pay, Google Pay, Link)
+  ![Apple_Pay_Google_Pay_Link\_-\_Quick_payments_bypassing_checkout](https://vendo-production-res.cloudinary.com/image/upload/w_2000/q_auto/v1742930027/docs/github/Spree_x_Stripe_-_Apple_Pay_Google_Pay_Link_-_Quick_payments_bypassing_checkout_on_Cart_n6gbh6.jpg)
+- Various payment options on the payment step (cards, BNPL, Apple Pay, Google Pay, Link)
+  ![Quick payments bypassing checkout 1st step (Apple Pay, Google_Pay, Link)](https://vendo-production-res.cloudinary.com/image/upload/w_2000/q_auto/v1742930027/docs/github/Spree_x_Stripe_-_Apple_Pay_Google_Pay_Link_-_Checkout_payment_step_rxxnr9.jpg)
+
+## Stripe Connect for Marketplaces
+
+Spree Commerce [Enterprise Edition](https://spreecommerce.org/spree-commerce-version-comparison-community-edition-vs-enterprise-edition/) comes with a fully automated Stripe Connect integration for [multi-vendor marketplace use cases](https://spreecommerce.org/marketplace-ecommerce/):
+
+- Automated split payments between marketplace and vendors
+- Support for multiple payment methods including cards and digital wallets
+- Configurable marketplace fees and commission structures
+- Automated payouts to vendors
+- Comprehensive transaction reporting
+- Built-in fraud prevention tools
+
+Feel free to [reach out](https://spreecommerce.org/get-started/) to learn more.

package/dist/integrations/search/meilisearch.md

@@ -0,0 +1,236 @@
+---
+title: Meilisearch
+description: "Set up Meilisearch for fast, typo-tolerant product search with faceted filtering"
+---
+
+## Overview
+
+[Meilisearch](https://www.meilisearch.com/) is a fast, open-source search engine that provides typo tolerance, relevance ranking, faceted filtering, and sub-50ms search responses. Spree includes a built-in Meilisearch search provider that replaces the default SQL-based search.
+
+**When to use Meilisearch:**
+- Catalogs with 1,000+ products
+- Need typo tolerance and relevance ranking
+- Want faceted filtering with adjusted counts
+- Require sub-second search responses
+- Multi-locale / multi-currency storefronts
+
+**When the default Database provider is sufficient:**
+- Development environments
+- Small catalogs (< 1,000 products)
+- Simple search requirements
+
+## Setup
+
+### 1. Install Meilisearch
+
+
+```bash macOS (Homebrew)
+brew install meilisearch
+meilisearch
+# Running at http://localhost:7700 — no API key needed for development
+```
+
+```bash Docker
+docker run -d --name meilisearch \
+  -p 7700:7700 \
+  -v $(pwd)/meili_data:/meili_data \
+  getmeili/meilisearch:latest
+```
+
+```bash Meilisearch Cloud
+# Sign up at https://www.meilisearch.com/cloud
+# Get your URL and API key from the dashboard
+```
+
+
+> **INFO:** For local development, Meilisearch runs without authentication by default — no API key is needed. For production, set a master key (minimum 16 bytes) via `MEILI_MASTER_KEY` when starting Meilisearch. Use this master key as your `MEILISEARCH_API_KEY`.
+
+### 2. Add the gem to your Gemfile
+
+```ruby
+gem 'meilisearch', '>= 0.28'
+```
+
+```bash
+bundle install
+```
+
+### 3. Configure environment variables
+
+```bash
+# .env
+
+# Local development — no API key needed
+MEILISEARCH_URL=http://localhost:7700
+
+# Production — use the master key you set when starting Meilisearch
+# MEILISEARCH_API_KEY=your-master-key-min-16-bytes
+```
+
+### 4. Set the search provider
+
+```ruby
+# config/initializers/spree.rb
+Spree.search_provider = 'Spree::SearchProvider::Meilisearch'
+```
+
+### 5. Index your products
+
+```bash
+rake spree:search:reindex
+```
+
+That's it. Your Store API now uses Meilisearch for all product search, filtering, and faceted navigation.
+
+## How It Works
+
+### Indexing
+
+Products are indexed as **one document per market × locale** combination. Each document contains the product's name and description in that locale, the price in that market's currency, and all non-translated fields (categories, options, stock, tags).
+
+For example, a store with a US market (USD, English) and an EU market (EUR, German/French) creates 3 index documents per product:
+
+| Document ID | Name | Price | Locale | Currency |
+|---|---|---|---|---|
+| `prod_abc_en_USD` | Blue Shirt | 29.99 | en | USD |
+| `prod_abc_de_EUR` | Blaues Hemd | 27.50 | de | EUR |
+| `prod_abc_fr_EUR` | Chemise Bleue | 27.50 | fr | EUR |
+
+Products are **only indexed for markets where they have a price**. If a product has no EUR price, no EUR documents are created.
+
+Translations use **Mobility with fallback** — if a product has no German translation, the default locale (English) is used.
+
+Each document includes:
+- Translated name, description, slug
+- Price and compare-at price in the market's currency
+- Category IDs, option type/value IDs (all prefixed)
+- Stock status, tags, timestamps
+- Store IDs, locale, currency (for filtering)
+
+Preview what gets indexed:
+
+```ruby
+# Rails console
+product = Spree::Product.first
+product.search_presentation
+# Returns an array of documents — one per market × locale
+```
+
+### Search Flow
+
+```curl
+GET /api/v3/store/products?q[search]=shirt&q[price_gte]=20&sort=price
+```
+
+1. Controller builds AR scope for security: `store.products.active(currency).accessible_by(ability)`
+2. Meilisearch provider adds base filters: `locale='en' AND currency='USD' AND status='active' AND store_ids='{id}' AND not_discontinued`
+3. Provider sends **one Meilisearch API call**: search + user filters + facets + sort + pagination
+4. Provider intersects Meilisearch product IDs with AR scope (safety net)
+5. Returns products + facets with adjusted counts + pagination
+
+The base filters ensure Meilisearch only returns products visible in the current locale and currency. The AR scope is a safety net — it should not filter out any additional products.
+
+### Index Name
+
+Each store gets its own Meilisearch index: `{store_code}_products`. For a store with code `"my-store"`, the index name is `my_store_products`.
+
+## Manual Operations
+
+### Reindex all products
+
+```bash
+rake spree:search:reindex
+```
+
+### Index a single product
+
+```ruby
+product.add_to_search_index
+```
+
+### Remove a product from the index
+
+```ruby
+product.remove_from_search_index
+```
+
+### Preview indexed data
+
+```ruby
+product.search_presentation
+```
+
+## Configuration
+
+| Environment Variable | Default | Description |
+|---|---|---|
+| `MEILISEARCH_URL` | `http://localhost:7700` | Meilisearch server URL |
+| `MEILISEARCH_API_KEY` | `nil` | Meilisearch master key. Not needed for local development — only required when Meilisearch is started with `MEILI_MASTER_KEY`. |
+
+The index is automatically configured with the correct filterable, sortable, and searchable attributes when you run `rake spree:search:reindex`.
+
+## Filterable Attributes
+
+The Meilisearch provider automatically configures these filterable attributes:
+
+- `product_id` — prefixed product ID (for bulk deletion of locale/currency variants)
+- `status` — product status (always filtered to `active` for Store API)
+- `in_stock` — boolean stock availability
+- `store_ids` — which stores the product belongs to
+- `locale` — document locale (filtered per request)
+- `currency` — document currency (filtered per request)
+- `discontinue_on` — Unix timestamp for discontinuation filtering
+- `price` — price in the document's currency
+- `category_ids` — prefixed category IDs
+- `tags` — product tags
+- `option_value_ids` — prefixed option value IDs
+
+## Sortable Attributes
+
+- `name` — sort alphabetically (locale-aware via per-locale documents)
+- `price` — sort by price (currency-aware via per-currency documents)
+- `created_at` — sort by creation date
+- `available_on` — sort by availability date
+- `units_sold_count` — sort by best selling
+
+## Searchable Attributes
+
+- `name` — product name (in document locale)
+- `description` — product description (in document locale)
+- `sku` — variant SKU
+- `option_values` — option value presentations (e.g., "Red", "Small")
+- `category_names` — category names
+- `tags` — product tags
+
+## Store API Compatibility
+
+The Meilisearch provider is fully compatible with the existing Store API. No client-side changes are needed:
+
+```typescript
+// Same SDK calls work with both Database and Meilisearch providers
+const products = await client.products.list({
+  search: 'blue shirt',
+  price_gte: 20,
+  price_lte: 100,
+  in_stock: true,
+  sort: 'price',
+  limit: 12,
+})
+```
+
+Locale and currency are automatically resolved from request headers (`x-spree-locale`, `x-spree-currency`) — no need to pass them as filter params.
+
+## Production Recommendations
+
+### Separate search and admin keys
+
+Meilisearch supports [tenant tokens](https://www.meilisearch.com/docs/learn/security/tenant_tokens) for fine-grained access control. Use an admin key for indexing and a search key for queries.
+
+### Meilisearch Cloud
+
+For production deployments, consider [Meilisearch Cloud](https://www.meilisearch.com/cloud) for managed hosting, automatic scaling, and monitoring.
+
+## 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

package/dist/integrations/sso-mfa-social-login/admin-dashboard.md

@@ -0,0 +1,57 @@
+---
+title: "SSO and MFA for the Admin Panel"
+sidebarTitle: "Admin SSO & MFA"
+description: "Learn how to secure your Spree admin panel with SSO and MFA integration, using Microsoft Entra ID as an example."
+---
+
+Enterprise businesses require **Single Sign-On (SSO)** and **Multi-Factor Authentication (MFA)** to secure sensitive operations, maintain compliance, and simplify IT administration. For Spree Commerce, the **admin panel** is the heart of your business operations, which means securing access here is critical.
+
+## SSO providers
+
+There are many popular SSO providers, such as **Microsoft Entra ID**, **Okta**, **Ping Identity**, and **OneLogin**. Each provider may also offer multiple services under its ecosystem.
+
+For example, Microsoft’s SSO ecosystem includes:
+
+- **Entra ID (previously Azure Active Directory)** → secures your **Spree Commerce admin panel** for workforce users.
+- **Entra External ID (previously Active Directory B2C)** → secures your **Spree storefront** for customer-facing apps, with support for social logins like Google and Facebook.
+
+> **NOTE:** For the purposes of this article, we are using **Microsoft** as the example provider.
+
+## Why integrate SSO with MFA for the Admin Panel
+
+- **Used by staff, merchants, and operators**
+- **Integration with Entra ID** ensures employees can log in using their corporate credentials
+- Benefits include:
+  - Higher security
+  - Regulatory compliance (SOC2, HIPAA, GDPR)
+  - Simplified IT administration
+  - Better user experience with SSO
+- With Microsoft solutions, you can also enable **Multi-Factor Authentication (MFA)** or **passwordless options** (Windows Hello, FIDO2 keys) to further strengthen access security
+
+## Get Started with SSO and MFA
+
+Each SSO integration needs to be scoped individually. The integration plan depends on multiple factors, such as:
+
+- **Required SSO provider**
+  - Decide whether you’ll use Microsoft Entra ID, Okta, Ping Identity, OneLogin, or another vendor. Each provider offers different features, protocols, and integration options.
+- **SSO provider settings**
+  - Each provider has unique configuration details, such as OAuth endpoints, certificates, tenant IDs, and federation settings. You’ll need to gather these to complete integration.
+- **Existing or planned Spree customizations**
+  - Custom authentication flows, extended user models, or unique admin permissions may affect how SSO is integrated. These should be reviewed before implementation.
+- **Spree and Ruby on Rails versions**
+  - Compatibility matters. Integration strategies can differ depending on whether you’re on the latest Spree release and which Rails version your project runs on.
+- **Use case: single tenant vs. multi-tenant**
+  - Single-tenant stores usually need straightforward workforce SSO. Multi-tenant or SaaS-style deployments may require isolated tenant directories and more complex provisioning.
+- **Identity governance requirements** (role-based access, just-in-time provisioning)
+- **User lifecycle management** (provisioning/de-provisioning)
+- **Security posture** (MFA enforcement, conditional access, passwordless policies)
+- **Compliance certifications required** (ISO, SOC2, HIPAA, PCI DSS)
+- **Traffic scale and performance** (concurrent users, global access, load balancing)
+- **Disaster recovery and redundancy** (failover strategies)
+- **Integration with third-party services** (analytics, CDPs, data warehouses)
+
+> **INFO:** Let's get in touch so we can scope your requirements and deliver this important integration for your project.
+
+
+  - [Book a Call](https://getvendo.com/book-a-demo/) — Schedule a call to explore the options and get your questions answered
+  - [Ask a Question](https://spreecommerce.org/get-started/) — Send us a message and share your thoughts

package/dist/integrations/sso-mfa-social-login/storefront.md

@@ -0,0 +1,56 @@
+---
+title: "SSO and Social Login for the Storefront"
+sidebarTitle: "Storefront SSO & Social Login"
+description: "Enable customer-facing SSO and social login on your Spree storefront, using Microsoft Entra External ID as an example."
+---
+
+Enterprise businesses benefit from offering **customer-facing SSO and social login** because it streamlines the shopping experience and improves conversions. Customers prefer using accounts they already trust instead of creating new ones.
+
+## SSO providers
+
+There are many popular SSO providers, such as **Microsoft Entra External ID**, **Auth0**, **Okta**, and **Ping Identity**. Each provider may offer several services with different target use cases.
+
+For example, Microsoft’s SSO ecosystem includes:
+
+- **Entra ID (previously Azure Active Directory)** → secures your **Spree Commerce admin panel** for workforce users.
+- **Entra External ID (previously Active Directory B2C)** → secures your **Spree storefront** for customer-facing apps, with support for social logins like Google and Facebook.
+
+> **NOTE:** For the purposes of this article, we are using **Microsoft** as the example provider.
+
+## Why integrate SSO and Social Login for the Storefront
+
+- **Used by shoppers**
+- Integration with **Entra External ID (B2C)** or other customer identity providers enables frictionless sign-ups and sign-ins
+- Benefits include:
+  - Reduced cart abandonment
+  - Faster checkout
+  - Higher conversion rates
+- Supports **social login options**: Google, Facebook, Amazon, Apple ID, Microsoft
+
+## Get Started with SSO and Social Login
+
+Each storefront integration must be scoped individually. Consider the following:
+
+- **Required SSO provider**
+  - Choose from Microsoft Entra External ID, Auth0, Okta, Ping Identity, or others. Your decision depends on features, ecosystem compatibility, and scalability needs.
+- **SSO provider settings, including identity providers**
+  - Each SSO platform has unique configuration settings (OAuth endpoints, certificates, client IDs). If you want to enable social logins, you’ll also need to configure providers like Google, Facebook, or Apple.
+- **Scope: social login only vs. SSO + social login**
+  - Decide whether you only want to add social login on top of Spree’s existing authentication or fully replace it with a unified SSO + social login solution.
+- **Existing or planned Spree customizations**
+  - Customized signup flows, checkout flows, or customer segmentation logic may impact integration design. These need to be factored in during scoping.
+- **Spree and Ruby on Rails versions**
+  - Ensure compatibility with your Spree and Rails versions. Older projects may need adjustments to take advantage of newer identity management features.
+- **Identity governance requirements** (segmentation, customer role-based access)
+- **User lifecycle management** (account creation, deactivation, syncing)
+- **Security posture** (MFA for customers, adaptive login, fraud detection)
+- **Compliance certifications required** (GDPR, CCPA, PCI DSS)
+- **Traffic scale and performance** (millions of customer accounts, peak season load)
+- **Disaster recovery and redundancy** (failover, global availability zones)
+- **Integration with third-party services** (marketing automation, CDPs, analytics, loyalty programs)
+
+> **INFO:** Let's get in touch so we can scope your requirements and deliver this important integration for your project.
+
+
+  - [Book a Call](https://getvendo.com/book-a-demo/) — Schedule a call to explore the options and get your questions answered
+  - [Ask a Question](https://spreecommerce.org/get-started/) — Send us a message and share your thoughts

package/package.json

@@ -0,0 +1,27 @@
+{
+  "name": "@spree/docs",
+  "version": "0.1.0",
+  "description": "Spree Commerce developer documentation for AI agents and local reference",
+  "type": "module",
+  "license": "CC-BY-4.0",
+  "author": "Vendo Connect Inc.",
+  "homepage": "https://spreecommerce.org",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/spree/spree.git",
+    "directory": "packages/docs"
+  },
+  "bugs": {
+    "url": "https://github.com/spree/spree/issues"
+  },
+  "files": [
+    "dist/**/*.md"
+  ],
+  "scripts": {
+    "build": "node scripts/build.js",
+    "clean": "rm -rf dist"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  }
+}