@spree/docs 0.1.5 → 0.1.6

package/dist/developer/admin/admin.md

@@ -4,7 +4,7 @@ sidebarTitle: Overview
 description: 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.
 
 <img src="/images/spree_admin_dashboard.png" alt="Spree Admin Dashboard" />
 

package/dist/developer/admin/custom-javascript.md

@@ -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, and
 
 That'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.
 

package/dist/developer/security/security_policy.md

@@ -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:
 

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

@@ -38,8 +38,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)

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

@@ -39,8 +39,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)

package/package.json

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