Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.
Ruby b2b-commercee-commerceecommerceecommerce-apiecommerce-frameworkecommerce-platformheadlessheadless-commerceheadless-ecommercemarketplacemulti-tenantmulti-vendormulti-vendor-ecommerceopen-sourcespree-commerce
Docs update
Damian Legawiecc0af19fffcde
diff --git a/.github/SECURITY.md b/.github/SECURITY.mdindex 5df4752197..865965a581 100644--- a/.github/SECURITY.md+++ b/.github/SECURITY.md@@ -6,8 +6,8 @@ The following versions are actively maintained and receive security patches.| Version | End of life || ------- | ------------ |-| 5.x | 26.03.2028 |-| 4.10 | 06.09.2027 |+| 5.x | 26.03.2027 |+| 4.10 | 06.09.2026 |Versions that are not listed above will not receive any security patches or fixes.diff --git a/.gitignore b/.gitignoreindex d37339d274..377e59af46 100644--- a/.gitignore+++ b/.gitignore@@ -58,3 +58,4 @@ server/packages/*/package-lock.json.turbopackages/*/dist+.claude/worktreesdiff --git a/docs/developer/admin/admin.mdx b/docs/developer/admin/admin.mdxindex bc089c24b6..21eba019d9 100644--- a/docs/developer/admin/admin.mdx+++ b/docs/developer/admin/admin.mdx@@ -4,7 +4,7 @@ sidebarTitle: Overviewdescription: Learn how to customize and extend the Spree Admin Dashboard----The Spree Admin Dashboard is a full-featured administration interface for managing your e-commerce store. It's built with Ruby on Rails and ships as the `spree_admin` gem.+The Spree Admin Dashboard is a full-featured administration interface for managing your e-commerce store.<Frame><img src="/images/spree_admin_dashboard.png" alt="Spree Admin Dashboard" />diff --git a/docs/developer/admin/custom-javascript.mdx b/docs/developer/admin/custom-javascript.mdxindex f6f9e1b203..f3062c914a 100644--- a/docs/developer/admin/custom-javascript.mdx+++ b/docs/developer/admin/custom-javascript.mdx@@ -6,7 +6,7 @@ description: Learn how to add custom JavaScript to your Spree Admin Dashboard## Extending Admin Dashboard with JavaScript-Spree Admin Dashboard can be easily extended with custom JavaScript. Most of the JavaScript in the Admin Dashboard is powered by a framework called [Stimulus.js](https://stimulus.hotwired.dev/) which is the Ruby on Rails default. It's a very simple and minimalistic framework only enhancing our server-side rendered HTML with a bit of interactivity.+Spree Admin Dashboard can be easily extended with custom JavaScript. Most of the JavaScript in the Admin Dashboard is powered by a framework called [Stimulus.js](https://stimulus.hotwired.dev/). It's a very simple and minimalistic framework only enhancing our server-side rendered HTML with a bit of interactivity.### 3rd party JavaScript libraries@@ -29,7 +29,7 @@ You're probably wondering why these libraries are in the `vendor` directory, andThat's because we're not using Node.js at all. So no Yarn or npm. We're using a different approach to manage dependencies.-We're using a tool called [Importmaps](https://github.com/rails/importmap-rails) to manage dependencies which is the Ruby on Rails default.+We're using a tool called [Importmaps](https://github.com/rails/importmap-rails) to manage dependencies.<Info>If you want to use a different JavaScript package manager you can do so by using [jsbundling-rails](https://github.com/rails/jsbundling-rails) gem.@@ -115,4 +115,4 @@ If you need to add a small piece of JavaScript code (eg. tracking, marketing, an<script>console.log("I'm a spy!");</script>- ```\ No newline at end of file+ ```diff --git a/docs/developer/security/security_policy.mdx b/docs/developer/security/security_policy.mdxindex 53addbf384..7c19885fed 100644--- a/docs/developer/security/security_policy.mdx+++ b/docs/developer/security/security_policy.mdx@@ -58,7 +58,7 @@ Published security advisories can be found at [GitHub Security Advisories](https## Security Best Practices-Spree is built on **Ruby on Rails** which provides strong security defaults including protection against SQL injection, CSRF, and XSS. For more details on how Spree handles security in production environments, see the [Enterprise Security Overview](/user/security).+Spree API is built on **Ruby on Rails** which provides strong security defaults including protection against SQL injection, CSRF, and XSS. For more details on how Spree handles security in production environments, see the [Enterprise Security Overview](/user/security).We recommend:diff --git a/docs/developer/storefront/rails/custom-javascript.mdx b/docs/developer/storefront/rails/custom-javascript.mdxindex f733d3efd2..0b8faff138 100644--- a/docs/developer/storefront/rails/custom-javascript.mdx+++ b/docs/developer/storefront/rails/custom-javascript.mdx@@ -6,7 +6,7 @@ description: "Learn how to add custom JavaScript to your Spree storefront"## Extending Storefront with JavaScript-Spree Storefront can be easily extended with custom JavaScript. Most of the JavaScript in the storefront is powered by a framework called [Stimulus.js](https://stimulus.hotwired.dev/) which is the Ruby on Rails default. It's a very simple and minimalistic framework only enhancing our server-side rendered HTML with a bit of interactivity.+Spree Storefront can be easily extended with custom JavaScript. Most of the JavaScript in the storefront is powered by a framework called [Stimulus.js](https://stimulus.hotwired.dev/). It's a very simple and minimalistic framework only enhancing our server-side rendered HTML with a bit of interactivity.### 3rd party JavaScript libraries@@ -29,7 +29,7 @@ You're probably wondering why these libraries are in the `vendor` directory, andThat's because we're not using Node.js at all. So no Yarn or npm. We're using a different approach to manage dependencies.-We're using a tool called [Importmaps](https://github.com/rails/importmap-rails) to manage dependencies which is the Ruby on Rails default.+We're using a tool called [Importmaps](https://github.com/rails/importmap-rails) to manage dependencies.<Info>If you want to use a different JavaScript package manager you can do so by using [jsbundling-rails](https://github.com/rails/jsbundling-rails) gem.@@ -168,4 +168,4 @@ document.addEventListener('turbo:frame-load', (event) => {- [Custom CSS](/developer/storefront/rails/custom-css) - Styling your storefront- [Sections](/developer/storefront/rails/sections) - Creating custom sections-- [Blocks](/developer/storefront/rails/blocks) - Creating custom blocks\ No newline at end of file+- [Blocks](/developer/storefront/rails/blocks) - Creating custom blocksdiff --git a/docs/integrations/sso-mfa-social-login/admin-dashboard.mdx b/docs/integrations/sso-mfa-social-login/admin-dashboard.mdxindex 2078359fe4..5fc6380875 100644--- a/docs/integrations/sso-mfa-social-login/admin-dashboard.mdx+++ b/docs/integrations/sso-mfa-social-login/admin-dashboard.mdx@@ -40,8 +40,8 @@ Each SSO integration needs to be scoped individually. The integration plan depen- 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.+- **Spree version**+ - Compatibility matters. Integration strategies can differ depending on whether you’re on the latest Spree release.- **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)@@ -63,4 +63,4 @@ Each SSO integration needs to be scoped individually. The integration plan depen<Card title="Ask a Question" icon="dollar-sign" href="https://spreecommerce.org/get-started/" cta="Click here">Send us a message and share your thoughts</Card>-</Columns>\ No newline at end of file+</Columns>diff --git a/docs/integrations/sso-mfa-social-login/storefront.mdx b/docs/integrations/sso-mfa-social-login/storefront.mdxindex 7a46a047a9..9cba8e86c5 100644--- a/docs/integrations/sso-mfa-social-login/storefront.mdx+++ b/docs/integrations/sso-mfa-social-login/storefront.mdx@@ -41,8 +41,8 @@ Each storefront integration must be scoped individually. Consider the following:- 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.+- **Spree version**+ - Ensure compatibility with your Spree version. 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)@@ -62,4 +62,4 @@ Each storefront integration must be scoped individually. Consider the following:<Card title="Ask a Question" icon="dollar-sign" href="https://spreecommerce.org/get-started/" cta="Click here">Send us a message and share your thoughts</Card>-</Columns>\ No newline at end of file+</Columns>diff --git a/docs/use-case/b2b/b2b-capabilities.mdx b/docs/use-case/b2b/b2b-capabilities.mdxindex b0aa777d40..78a33c948b 100644--- a/docs/use-case/b2b/b2b-capabilities.mdx+++ b/docs/use-case/b2b/b2b-capabilities.mdx@@ -47,7 +47,7 @@ While many marketplace features are available out-of-the-box in Spree EnterpriseSpree Enterprise offers flexibility across all layers of the platform, from code-level customization to no-code configuration.- **Customization (Custom Code)**- - **Backend (Ruby on Rails)** - extend business logic, workflows, and integrations via Spree's modular architecture. See: [<u>Spree Developer Quickstart</u>](https://spreecommerce.org/docs/developer/getting-started/quickstart)+ - **Backend** - extend business logic, workflows, and integrations via Spree's modular architecture. See: [<u>Spree Developer Quickstart</u>](https://spreecommerce.org/docs/developer/getting-started/quickstart)- **Frontend Themes (HTML, CSS, JS)** - customize storefront layouts, styling, and interactivity to match your brand and UX goals. See: [<u>Storefront Customization</u>](https://spreecommerce.org/docs/developer/storefront/storefront)- **Configuration (No-Code / Low-Code)**- **Store Settings** - configure store name, logo, contact details, and supported languages/currencies.@@ -92,4 +92,4 @@ With Spree Enterprise, you’re not locked into a black-box SaaS model. You reta## Further Reading- [<u>B2B Commerce Model</u>](https://spreecommerce.org/docs/use-case/b2b/b2b-commerce-model)- [<u>B2B Admin Capabilities</u>](https://spreecommerce.org/docs/use-case/b2b/b2b-admin-capabilities)-- [<u>B2B Buyer Experience</u>](https://spreecommerce.org/docs/use-case/b2b/b2b-buyer-experience)\ No newline at end of file+- [<u>B2B Buyer Experience</u>](https://spreecommerce.org/docs/use-case/b2b/b2b-buyer-experience)diff --git a/docs/use-case/digital-products/capabilities.mdx b/docs/use-case/digital-products/capabilities.mdxindex 62c4c03e5d..88aba5c23f 100644--- a/docs/use-case/digital-products/capabilities.mdx+++ b/docs/use-case/digital-products/capabilities.mdx@@ -78,4 +78,4 @@ With Spree, you’re not locked into a black-box SaaS model. You retain complete## Further Reading- [Digital Products Model](https://spreecommerce.org/docs/use-case/digital-products/model)-- [Digital Products Admin Capabilities](https://spreecommerce.org/docs/use-case/digital-products/admin-capabilities)\ No newline at end of file+- [Digital Products Admin Capabilities](https://spreecommerce.org/docs/use-case/digital-products/admin-capabilities)diff --git a/docs/user/security.mdx b/docs/user/security.mdxindex 8e9c07718a..8809389a8b 100644--- a/docs/user/security.mdx+++ b/docs/user/security.mdx@@ -38,7 +38,7 @@ Our Secure Software Development Lifecycle (SDLC) ensures that every Spree Commer## 2. Security-by-Design (Ruby on Rails Foundation)-Spree is built on **Ruby on Rails**, a framework known for its strong “security-by-default” architecture. Rails powers global companies like Shopify, GitHub, Airbnb, Kickstarter, and Square—proving its enterprise readiness.+Spree API is built on **Ruby on Rails**, a framework known for its strong “security-by-default” architecture. Rails powers global companies like Shopify, GitHub, Airbnb, Kickstarter, and Square—proving its enterprise readiness.### Core Security Features@@ -150,5 +150,3 @@ This ensures enterprise customers remain **secure, compliant, and high-performinSee Enterprise pricing for your use case</Card></Columns>--