@spree/docs 0.1.107 → 0.1.109

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

@@ -579,38 +579,6 @@ Here's a list of all places you can inject your custom code:
 </details>
 
 
-### Custom Domains
-
-<details>
-<summary>Custom Domains Actions</summary>
-
-`custom_domains_actions`
-
-    Injects code into the page actions area for the custom domains list page.
-
-    ```erb
-    <%= link_to "Verify All Domains", verify_all_domains_path, class: "btn btn-secondary" %>
-    ```
-
-</details>
-
-
-  <details>
-<summary>Custom Domains Header</summary>
-
-`custom_domains_header`
-
-    Injects code between the page header and the main content area for the custom domains list page.
-
-    ```erb
-    <div class="alert alert-info">
-      <strong>SSL:</strong> SSL certificates are automatically managed.
-    </div>
-    ```
-
-</details>
-
-
 ### Customer Returns
 
 <details>

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

@@ -1,6 +1,6 @@
 ---
 title: Architecture
-description: How Spree's core models, APIs, and packages work together
+description: Explore how Spree's core models, APIs, and gems fit together — catalog, shopping, checkout, fulfillment, and pricing — for headless or embedded commerce.
 ---
 
 ## Overview

package/dist/developer/core-concepts/staff-roles.md

@@ -1,6 +1,6 @@
 ---
 title: Staff & Roles
-description: Admin users, roles, invitations, and permissions
+description: Manage Spree admin users, roles, invitations, and permissions — create admins via the CLI, scope access per store, and customize role-based permissions.
 ---
 
 ## Overview

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

@@ -1,13 +1,11 @@
 ---
 title: Stores
-description: The Store is Spree's top-level multi-tenant boundary — learn how products, orders, channels, and markets are scoped to a store.
+description: Understand Spree Stores — the top-level tenant boundary that scopes products, orders, channels, markets, and branding, with the Admin API for store config.
 ---
 
 ## Overview
 
-The Store is the top-level tenant in Spree. Every resource — products, orders, channels, markets, taxonomies — belongs to exactly one store. A store owns its branding (logo, custom domain, mail-from address), its [channels](channels.md) (online, POS, wholesale, …), its [markets](markets.md) (region/currency/locale), and its catalog.
-
-## Store Attributes
+The StThe Store is the top-level tenant in Spree. Every resource — products, orders, channels, markets, taxonomies — belongs to exactly one store. A store owns its [channels](channels.md) (online, POS, wholesale, …), its [markets](markets.md) (region/currency/locale), and its [product catalog](products.md).tore Attributes
 
 | Attribute | Description |
 |-----------|-------------|

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

@@ -5,16 +5,6 @@ sidebarTitle: Configuration
 
 Multi-tenant applications include additional configuration options. All configuration should be placed in `config/initializers/spree_multi_tenant.rb` file.
 
-### Root domain
-
-To make multi-tenant, you need a root/wildcard domain, eg. `*.example.com`. Tenant stores are usually accessed via subdomains, eg. `store1.example.com`, `store2.example.com`, etc.
-
-```bash
-Spree.root_domain = 'example.com'
-```
-
-Still your tenants will be able to add custom domains, eg. `myflowerstore.com` via the Spree admin panel. Tenant subdomains are used only for admin panel access.
-
 ### App subdomain
 
 Application subdomains is used to access the application, eg. `app.example.com`. By default for existing tenants it will redirect them to their tenant subdomain, eg. `store1.example.com`. If you want, you can also use this as a tenant signup/store setup page, this is available under `app.example.com/tenants/new`.

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

@@ -1,80 +1,36 @@
 ---
-title: Spree Multi Tenant Installation
-sidebarTitle: Installation
-description: Install and configure Spree Multi-Tenant to run a SaaS ecommerce platform, including prerequisites, gem setup, license keys, and tenant provisioning.
+title: Create a multi-tenant / SaaS platform on top of Spree
+sidebarTitle: Quickstart
+description: Configure Spree to run a SaaS ecommerce platform, including prerequisites, gem setup, license keys, and tenant provisioning.
 ---
 
-> **WARNING:** This installation instructions assume you have a clean Spree Starter installation and you've purchased the [Spree Enterprise Edition license](https://spreecommerce.org/pricing).
->   
->   For migrating existing application from single-tenant to multi-tenant, please contact us at [support@spreecommerce.org](mailto:support@spreecommerce.org).
+> **INFO:** Multi-tenancy requires [Spree Enterprise Edition license](https://spreecommerce.org/pricing).
 
-## Prerequisites
-
-* You need to be on Spree 5.1+, we recommend using [spree_starter](https://github.com/spree/spree_starter) as a base for your application
-* You need to have 2 environment variables set:
-  * `KEYGEN_ACCOUNT_ID`
-  * `KEYGEN_LICENSE_KEY`
-* We support both PostgreSQL and MySQL databases
-
-> **INFO:** Environment variables will be provided to you after purchasing the [Spree Enterprise Edition license](https://spreecommerce.org/pricing).
-
-> **WARNING:** You will need to add these environment variables to your CI/CD pipeline and production environments.
-
-## Customer User Class
+Spree can be configured to run a multi-tenant / SaaS platform. This guide will walk you through the steps to set up your Spree application to support multiple tenants (stores). 
+Each tenant (store) can have its own isolated data and configuration, including:
 
-Please follow [Authentication](../customization/authentication.md) documentation to create a new user class.
+* customer accounts
+* staff accounts (admin users), staff can manage multiple tenants (it's the standard invitation flow)
+* products, categories, and other catalog data
+* orders and order history
+* shipping and payment methods
+* tax rates and zones
+* store settings (name, logo, etc.)
+* etc.
 
-Now we will need to make slight adjustments to the generated user class so it can work in a multi-tenant environment.
+All data is fully isolated besided the staff users, which can manage multiple tenants. This allows you to create a SaaS platform where each tenant can have its own store with its own branding and configuration. Isolation works across admin dashboard and API.
 
-If you're using Devise, you will need to remove `:validatable` module. This module is responsible for validating the user's email uniqueness. We need to change it to validate it in the scope of the tenant.
+> **INFO:** If you need individual seller/supplier/vendor accounts but shared product listings under one site you should use [multi vendor recipe](../multi-vendor.md) instead.
 
-Spree Multi-Tenant gem injects `SpreeMultiTenant::CustomerUserConcern` that handles that instead.
-
-## Admin User Class
-
-For our multi-tenant setup we will need a separate Admin user class. Our standard User class will be only used for customer accounts which will be isolated by tenant. 
-Admin user classes will be shared across tenants allowing them to manage multiple tenants from a single admin panel.
-
-Let's create a new model with Devise (unless you already have one):
-
-
-```bash Spree CLI (Docker)
-spree rails g devise Spree::AdminUser
-```
-
-```bash Without Spree CLI
-bin/rails g devise Spree::AdminUser
-```
-
-
-Replace the generated Devise code with the following:
-
-```ruby
-class Spree::AdminUser < Spree::Base
-  # Include default devise modules. Others available are:
-  # :confirmable, :lockable, :timeoutable, :trackable and :omniauthable
-  devise :database_authenticatable, :registerable,
-        :recoverable, :rememberable, :validatable
-
-  # Spree modules
-  include Spree::UserMethods
-end
-```
-
-If you already have a custom Admin user class, you can add the following code to it:
-
-```ruby
-  # Spree modules
-  include Spree::UserMethods
-```
-
-This will make sure that the Admin user class works well with Spree ecosystem.
+## Prerequisites
 
-Register new model in `config/initializers/spree.rb`:
+* You need to be on Spree 5.1+, we recommend using [CLI](../getting-started.md) to setup your Spree application.
+* You need to set 2 environment variables in your `backend` directory:
+  * `KEYGEN_ACCOUNT_ID`
+  * `KEYGEN_LICENSE_KEY`
+* Both PostgreSQL and MySQL are supported
 
-```ruby
-Spree.admin_user_class = "Spree::AdminUser"
-```
+> **INFO:** You will need to add these environment variables to your CI/CD pipeline and staging/production environments.
 
 ## Installing gems
 
@@ -116,3 +72,37 @@ Spree.admin_user_class = "Spree::AdminUser"
     
 
     > **INFO:** This will copy and run migrations for `spree_enterprise` and `spree_multi_tenant` gems.
+
+
+## Setting root domain
+
+Usually multi-tenant applications are configured to use subdomains for each tenant. For example, if your root domain is `example.com`, you can have tenants like `tenant1.example.com`, `tenant2.example.com`, etc.
+To make it work you need to set the `Spree.root_domain` in your `config/initializers/spree.rb` file, eg.
+
+```ruby
+Spree.root_domain = 'example.com'
+```
+
+or use environment variable:
+
+```ruby
+Spree.root_domain = ENV.fetch('SPREE_ROOT_DOMAIN', 'localhost')
+```
+
+This way you can also test it locally using `localhost` as root domain, and use `tenant1.localhost`, `tenant2.localhost`, etc. for tenants.
+
+## Customer User Class adjustment
+
+We need to make slight adjustments to the user class so it can work in a multi-tenant environment.
+
+You need to remove `:validatable` module. This module is responsible for validating the user's email uniqueness. We need to change it to validate it in the scope of the tenant.
+
+```ruby backend/app/models/spree/user.rb
+class User < ApplicationRecord
+  devise :database_authenticatable, :registerable, :validatable # [!code --]
+  devise :database_authenticatable, :registerable, # [!code ++]
+         :recoverable, :rememberable, :trackable, :confirmable
+
+  include SpreeMultiTenant::CustomerUserConcern # [!code ++]
+end
+```

package/dist/developer/upgrades/4.2-to-4.3.md

@@ -1,9 +1,9 @@
 ---
-title: 4.2 to 4.3
+title: Upgrading to Spree 4.3
 section: upgrades
 order: 0
 hidden: true
-description: This guide covers upgrading a 4.2 Spree application to Spree 4.3.
+description: Upgrade a Spree 4.2 application to Spree 4.3 — split out spree_emails, spree_backend, and spree_frontend gems, remove merged extensions, and run migrations.
 ---
 
 > **NOTE:** If you're on an older version than 4.1 please follow previous upgrade guides and perform those upgrades incrementally, eg.

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

@@ -1,6 +1,6 @@
 ---
 title: Upgrading to Spree 5.4
-description: This guide covers upgrading a Spree 5.3 application to Spree 5.4.
+description: Upgrade a Spree 5.3 application to Spree 5.4 — remove spree_sample, update gems, run migrations, switch to AdminUserMethods, and backfill image thumbnail IDs.
 ---
 
 > **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.3](5.2-to-5.3.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spree/docs",
-  "version": "0.1.107",
+  "version": "0.1.109",
   "description": "Spree Commerce developer documentation for AI agents and local reference",
   "type": "module",
   "license": "CC-BY-4.0",