@mercurjs/docs 2.3.0-canary.1 → 2.3.0

package/content/home.mdx

@@ -1,13 +1,14 @@
 ---
 title: "Mercur Documentation"
 sidebarTitle: "Home"
-description: "The open-source enterprise marketplace platform built on Medusa."
+description: "The open-source enterprise marketplace platform. Composable, API-first, and AI-native, on infrastructure you own."
 ---
 
-Mercur is the open-source enterprise marketplace platform built on Medusa. It adds
-sellers, offers, commissions, order splitting, and payouts on top of Medusa's
-commerce engine, with role-based access and an auditable change pipeline, on
-infrastructure you own.
+Mercur is the open-source enterprise marketplace platform. It gives operators
+multi-vendor governance: sellers, offers, commissions, order splitting, and
+payouts, with role-based access and an auditable change pipeline, on
+infrastructure you own. Core commerce runs on the proven Medusa engine, so
+products, pricing, carts, orders, and payments are mature from day one.
 
 <video
   playsInline
@@ -26,7 +27,7 @@ infrastructure you own.
     Governance, ownership, and composability without a closed platform.
   </Card>
   <Card title="Architecture" icon="sitemap" href="/learn/architecture">
-    How Mercur layers the marketplace domain on Medusa.
+    How the marketplace platform is architected, module by module.
   </Card>
   <Card title="Build with AI" icon="robot" href="/resources/ai/overview">
     Version-matched docs, agent skills, and the MCP server.

package/content/learn/introduction.mdx

@@ -5,15 +5,16 @@ description: "Set up Mercur, tour the operator and seller panels, and see how a
 
 ## What is Mercur
 
-Mercur is the open-source enterprise marketplace platform built on Medusa. Medusa
-provides the commerce engine (products, pricing, carts, orders, fulfillment, and
-payments), and Mercur adds the marketplace layer on top: sellers and their teams,
-onboarding, the catalog change pipeline, commissions, order splitting, and vendor
-payouts.
+Mercur is the open-source enterprise marketplace platform. It gives a marketplace
+operator real governance over sellers and their teams, onboarding, the catalog
+change pipeline, commissions, order splitting, and vendor payouts. Role-based
+access control, an auditable change pipeline, and per-seller settlement back all of
+it, while it stays composable, API-first, and fully code-owned. You run it on your
+own infrastructure.
 
-It gives a marketplace operator real governance: role-based access control, an
-auditable change pipeline, and per-seller settlement, while staying composable,
-API-first, and fully code-owned. You run it on your own infrastructure.
+Core commerce runs on the proven Medusa engine, so products, pricing, carts,
+orders, fulfillment, and payments are mature and maintained from day one, and
+Mercur focuses on the marketplace domain on top.
 
 ## Requirements
 
@@ -165,7 +166,7 @@ step is governed by the same roles and recorded for audit.
 
 <CardGroup cols={2}>
   <Card title="Architecture" icon="sitemap" href="/learn/architecture">
-    How Mercur layers the marketplace domain on Medusa.
+    How the marketplace platform is architected, module by module.
   </Card>
   <Card title="Platform" icon="cubes" href="/platform/store/overview">
     Every marketplace capability, with its data models and workflows.

package/content/learn/why-mercur.mdx

@@ -47,11 +47,13 @@ by construction or it fails to compile. Agents work inside the same roles and
 review pipeline as people. They extend the platform, they do not bypass its
 governance.
 
-## Built on Medusa
+## A proven commerce core
 
-Mercur runs on the Medusa commerce engine, so products, pricing, carts, orders,
-and payments are proven, maintained infrastructure. You inherit Medusa's maturity
-and extension model, and Mercur adds only the marketplace layer on top.
+Mercur does not reinvent commerce. Products, pricing, carts, orders, and payments
+run on the proven Medusa engine, so that layer is mature, maintained infrastructure
+from day one. On top of it, Mercur delivers the full marketplace platform:
+governance, multi-vendor orders, commissions, and payouts that a single-store
+engine does not provide.
 
 ## Mercur vs closed marketplace platforms
 
@@ -80,7 +82,7 @@ closed platform.
     Set up Mercur and run a marketplace locally.
   </Card>
   <Card title="Architecture" icon="sitemap" href="/learn/architecture">
-    How Mercur layers the marketplace domain on Medusa.
+    How the marketplace platform is architected, module by module.
   </Card>
   <Card title="Platform" icon="cubes" href="/platform/store/overview">
     Every marketplace capability, with its data models and workflows.

package/llms.txt

@@ -242,7 +242,7 @@ package (`node_modules/@mercurjs/docs/`).
 ## Other
 
 - [Official Blocks](content/blocks.mdx) — Modular blocks from the official Mercur registry — install only what you need.
-- [Mercur Documentation](content/home.mdx) — The open-source enterprise marketplace platform built on Medusa.
+- [Mercur Documentation](content/home.mdx) — The open-source enterprise marketplace platform. Composable, API-first, and AI-native, on infrastructure you own.
 - [Attribute types](content/platform/attribute/concepts/attribute-types.mdx) — The five attribute types and the values they hold.
 - [Global vs inline & filtering](content/platform/attribute/concepts/global-vs-inline.mdx) — Catalog-wide attributes, product-scoped attributes, and storefront filtering.
 - [Variant axes](content/platform/attribute/concepts/variant-axes.mdx) — How is_variant_axis mirrors a native ProductOption and generates variants.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mercurjs/docs",
-  "version": "2.3.0-canary.1",
+  "version": "2.3.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/mercurjs/mercur",