docs: capitalize use of Framework across docs (#12207)

* docs: capitalize use of Framework across docs

* generate llm
This commit is contained in:
Shahed Nasser
2025-04-17 10:40:26 +03:00
committed by GitHub
parent f6b20a943e
commit 42262d41a1
36 changed files with 14297 additions and 14283 deletions
@@ -31,7 +31,7 @@ export const metadata = {
In this tutorial, you'll learn how to integrate Medusa with Algolia.
When you install a Medusa application, you get a fully-fledged commerce platform with a framework for customization. Medusa's architecture supports integrating third-party services, such as a search engine, allowing you to build your unique requirements around core commerce flows.
When you install a Medusa application, you get a fully-fledged commerce platform with a Framework for customization. Medusa's architecture supports integrating third-party services, such as a search engine, allowing you to build your unique requirements around core commerce flows.
[Algolia](https://www.algolia.com/doc/) is a search engine that enables you to build and manage an intuitive search experience for your customers. By integrating Algolia with Medusa, you can index e-commerce data, such as products, and allow clients to search through them.
@@ -453,7 +453,7 @@ You create a step with `createStep` from the Workflows SDK. It accepts two param
1. The step's unique name, which is `sync-products`.
2. An async function that receives two parameters:
- The step's input, which is in this case an object holding an array of products to sync into Algolia.
- An object that has properties including the [Medusa container](!docs!/learn/fundamentals/medusa-container), which is a registry of framework and commerce tools that you can access in the step.
- An object that has properties including the [Medusa container](!docs!/learn/fundamentals/medusa-container), which is a registry of Framework and commerce tools that you can access in the step.
In the step function, you resolve the Algolia Module's service from the Medusa container using the name you exported in the module definition's file.