docs: capitalize use of Framework across docs (#12207)
* docs: capitalize use of Framework across docs * generate llm
This commit is contained in:
1 parent
f6b20a943e
commit
42262d41a1
36 files changed
+14297
-14283
No files matched your search
@@ -31,7 +31,7 @@ export const metadata = {
|
||||
|
||||
In this guide, you'll learn how to notify customers when a variant is restocked in Medusa.
|
||||
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with a framework for customization. The Medusa application's commerce features are built around [commerce modules](../../../commerce-modules/page.mdx) which are available out-of-the-box. These features include managing the inventory of product variants in different stock locations and sales channels.
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with a Framework for customization. The Medusa application's commerce features are built around [commerce modules](../../../commerce-modules/page.mdx) which are available out-of-the-box. These features include managing the inventory of product variants in different stock locations and sales channels.
|
||||
|
||||
Customers browsing your store may be interested in a product that is currently out of stock. To keep the customer interested in your store and encourage them to purchase the product in the future, you can build customizations around Medusa's commerce features to subscribe customers to receive a notification when the product is restocked.
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ export const metadata = {
|
||||
|
||||
In this guide, you'll learn how to support digital products in Medusa.
|
||||
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with support for customizations. Medusa provides all features related to products and managing them, and its framework allows you to extend those features and implement your custom use case.
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with support for customizations. Medusa provides all features related to products and managing them, and the Medusa Framework allows you to extend those features and implement your custom use case.
|
||||
|
||||
You can extend Medusa's product features to support selling, storing, and fulfilling digital products. In this guide, you'll customize Medusa to add the following features:
|
||||
|
||||
@@ -21,7 +21,7 @@ You can extend Medusa's product features to support selling, storing, and fulfil
|
||||
|
||||
<Note>
|
||||
|
||||
This guide provides an example of an approach to implement digital products. You're free to choose a different approach using Medusa's framework.
|
||||
This guide provides an example of an approach to implement digital products. You're free to choose a different approach using the Medusa Framework.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ export const metadata = {
|
||||
|
||||
In this guide, you will learn how to implement the integration layer between Odoo and Medusa.
|
||||
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform that supports customizations. However, your business might already be using other systems such as an ERP to centralize data and processes. Medusa's framework facilitates integrating the ERP system and using its data to enrich your commerce platform.
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform that supports customizations. However, your business might already be using other systems such as an ERP to centralize data and processes. The Medusa Framework facilitates integrating the ERP system and using its data to enrich your commerce platform.
|
||||
|
||||
Odoo is a suite of open-source business apps that covers all your business needs, including an ERP system. You can use Odoo to store products and their prices, manage orders, and more.
|
||||
|
||||
@@ -572,7 +572,7 @@ You create a step using `createStep` from the Workflows SDK. It accepts two para
|
||||
1. The step's name, which is `get-products-from-erp`.
|
||||
2. An async function that executes the step's logic. The function receives two parameters:
|
||||
- The input data for the step, which are the pagination fields `offset` and `limit`.
|
||||
- An object holding the workflow's context, including the [Medusa Container](!docs!learn/fundamentals/medusa-container) that allows you to resolve framework and commerce tools.
|
||||
- An object holding the workflow's context, including the [Medusa Container](!docs!learn/fundamentals/medusa-container) that allows you to resolve Framework and commerce tools.
|
||||
|
||||
In this step, you resolve the Odoo Module's service from the container and use its `listProducts` method to fetch products from Odoo. You pass the pagination options from the input data to the method.
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ Businesses often rely on an ERP system to centralize their data and custom busin
|
||||
|
||||
When integrating the ERP system with other ecommerce platforms, you'll face complications maintaining data consistency across systems and customizing the platform's existing flows to accommodate the ERP system's data and operations. For example, the ecommerce platform may not support purchasing products with custom pricing or restricting certain products from purchase under certain conditions.
|
||||
|
||||
Medusa's framework for customization solves these challenges by giving you a durable execution engine to orchestrate operations through custom flows, and the flexibility to customize the platform's existing flows. You can wrap existing flows with custom logic, inject custom features into existing flows, and create new flows that interact with the ERP system and sync data between the two systems.
|
||||
The Medusa Framework solves these challenges by giving you a durable execution engine to orchestrate operations through custom flows, and the flexibility to customize the platform's existing flows. You can wrap existing flows with custom logic, inject custom features into existing flows, and create new flows that interact with the ERP system and sync data between the two systems.
|
||||
|
||||

|
||||
|
||||
@@ -203,7 +203,7 @@ export const syncFromErpWorkflow = createWorkflow(
|
||||
)
|
||||
```
|
||||
|
||||
In the above file, you first create a `getProductsFromErpStep` that resolves the ERP Module's service from the [Medusa container](!docs!/learn/fundamentals/medusa-container), which is a registry of framework and commerce tools, including your modules, that you can access in your customizations. You can then call the `getProducts` method in the ERP Module's service to fetch the products from the ERP and return them.
|
||||
In the above file, you first create a `getProductsFromErpStep` that resolves the ERP Module's service from the [Medusa container](!docs!/learn/fundamentals/medusa-container), which is a registry of Framework and commerce tools, including your modules, that you can access in your customizations. You can then call the `getProducts` method in the ERP Module's service to fetch the products from the ERP and return them.
|
||||
|
||||
Then, you create a `syncFromErpWorkflow` that executes the `getProductsFromErpStep` to get the products from the ERP, then prepare the products to be created in Medusa. For example, you can set the product's title, and specify its ID in the ERP using the `external_id` field. Also, assuming the ERP products have variants, you can map the variants to Medusa's format, setting the variant's title and its ERP ID in the metadata.
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ export const metadata = {
|
||||
|
||||
In this guide, you'll learn how to build a restaurant-delivery marketplace platform, similar to Uber Eats, with Medusa.
|
||||
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with support for customizations. While Medusa doesn't provide marketeplace functionalities natively, it provides features that you can extend and a framework to support all your customization needs to build a marketplace.
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with support for customizations. While Medusa doesn't provide marketeplace functionalities natively, it provides features that you can extend and a Framework to support all your customization needs to build a marketplace.
|
||||
|
||||
In this guide, you'll customize Medusa to build a restaurant-delivery platform with the following features:
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ export const metadata = {
|
||||
|
||||
In this guide, you'll learn how to build a marketplace with Medusa.
|
||||
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with support for customizations. While Medusa doesn't provide marketplace functionalities natively, it provides features that you can extend and a framework to support all your customization needs to build a marketplace.
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with support for customizations. While Medusa doesn't provide marketplace functionalities natively, it provides features that you can extend and a Framework to support all your customization needs to build a marketplace.
|
||||
|
||||
## Summary
|
||||
|
||||
@@ -23,7 +23,7 @@ You can follow this guide whether you're new to Medusa or an advanced Medusa dev
|
||||
|
||||
<Note>
|
||||
|
||||
This guide provides an example of an approach to implement marketplaces. You're free to choose a different approach using Medusa's framework.
|
||||
This guide provides an example of an approach to implement marketplaces. You're free to choose a different approach using the Medusa Framework.
|
||||
|
||||
</Note>
|
||||
|
||||
@@ -498,7 +498,7 @@ You create a step with `createStep` from the Workflows SDK. It accepts three par
|
||||
1. The step's unique name, which is `create-vendor`.
|
||||
2. An async function that receives two parameters:
|
||||
- An input object with the details of the vendor to create.
|
||||
- The [Medusa container](!docs!/learn/fundamentals/medusa-container), which is a registry of framework and commerce tools that you can access in the step.
|
||||
- The [Medusa container](!docs!/learn/fundamentals/medusa-container), which is a registry of Framework and commerce tools that you can access in the step.
|
||||
3. An async compensation function. This function is only executed when an error occurs in the workflow. It undoes the changes made by the step.
|
||||
|
||||
In the step function, you resolve the Marketplace Module's service from the container. Then, you use the service's generated `createVendors` method to create the vendor.
|
||||
|
||||
@@ -64,7 +64,7 @@ In more complex cases, you can create a custom module that stores and manages th
|
||||
|
||||
## Build a Custom Storefront
|
||||
|
||||
Medusa's modular architecture removes any restrictions on the framework you use to build the storefront, or design and experience you provide customers. The storefront connects to the Medusa application using the Store API Routes.
|
||||
Medusa's modular architecture removes any restrictions on the your storefront's tech stack, design, and the experience you provide customers. The storefront connects to the Medusa application using the Store API Routes.
|
||||
|
||||
You can build a unique experience around your products that focuses on the customer’s personalization capabilities.
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Medusa's modular architecture solves these challenges. Any frontend can utilize
|
||||
|
||||
## Freedom in Choosing Your POS Tech Stack
|
||||
|
||||
When you build a POS system, you must choose which programming framework, language, or tool you want to use.
|
||||
When you build a POS system, you must choose the programming language or tool you want to use.
|
||||
|
||||
Medusa's modular architecture removes any restrictions you may have while making this choice. Any client or front end can connect to the Medusa application using its headless REST APIs.
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ export const metadata = {
|
||||
|
||||
In this guide, you'll learn how to support subscription purchases with Medusa.
|
||||
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with support for customizations. While Medusa doesn't provide subscription-based purchases natively, it provides the framework to support you in implementing this feature.
|
||||
When you install a Medusa application, you get a fully-fledged commerce platform with support for customizations. While Medusa doesn't provide subscription-based purchases natively, it provides the Framework to support you in implementing this feature.
|
||||
|
||||
In this guide, you'll customize Medusa to implement subscription-based purchases with the following features:
|
||||
|
||||
@@ -23,7 +23,7 @@ This guide uses Stripe as an example to capture the subscription payments. You'r
|
||||
|
||||
<Note>
|
||||
|
||||
This guide provides an example of an approach to implement subscriptions. You're free to choose a different approach using Medusa's framework.
|
||||
This guide provides an example of an approach to implement subscriptions. You're free to choose a different approach using the Medusa Framework.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
Reference in new issue
Block a user